help with constant log rc_service messages

[andresmorago]

Hello all
I’m having constant “spam” messages on my log. im on a rescued ac88u running latest 384.13. i have resetted it several times
Does this need to be a concern? Router seems to work ok but this message is spamming my log every minute non stop.

i have all the basic installed: amtm, diversion, skynet, qos, logrotate.

thanks

Here is part of my log

Aug 12 06:24:27 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:24:27 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:24:56 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:24:56 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:25:26 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:25:26 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:25:56 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:25:56 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:26:27 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:26:27 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:26:56 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:26:56 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:27:26 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:27:26 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:27:56 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:27:56 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:28:27 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:28:27 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:28:56 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:28:56 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:29:26 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:29:26 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Aug 12 06:29:56 RT-AC88U-A740 rc_service: watchdog 285:notify_rc start_cfgsync
Aug 12 06:29:56 RT-AC88U-A740 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)

here is /jffs/scripts/service-event

/jffs/scripts/connmon generate "$1" "$2" & # connmon
/jffs/scripts/ntpmerlin generate "$1" "$2" & # ntpMerlin
/jffs/scripts/uiDivStats generate "$1" "$2" & # uiDivStats
/jffs/scripts/scribe kill-logger nologo "$1" "$2" & # added by scribe

after uninstalling ntpmerlin, logrotate and rebooting, messages still appear

Aug 12 07:05:52 rc_service: watchdog 305:notify_rc start_cfgsync
Aug 12 07:05:52 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)

just for curiosity. Uninstalled conmon and diversion stats. Messages remain

Aug 12 07:15:12 rc_service: watchdog 305:notify_rc start_cfgsync
Aug 12 07:15:12 custom_script: Running /jffs/scripts/service-event (args: start cfgsync)

 

[dave14305]

It seems to be unhappy detecting whether the AiMesh cfgsync daemon is running. It wouldn’t be related to the scripts. That’s just a side effect of the service-event script triggering for every event logged.

Does anything else run on your router on port 7788 that could cause a conflict with cfg_server?

 

[andresmorago]

thanks dave
nothing is going on on port 7788. in fact, im not using aimesh at all.

i believe this might be related with the "illness" on this particular router. both radios are very unstable as they "take turns" to work. yesterday, after dozens of hard resets and having a 2G radio dead, i was able to bring both radios up. today, only 2G worked and 5G was dead and tons of this message appear.

its being fun to try to revive this unit