What's new

CRON jobs keep deleting?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

davidwford

Occasional Visitor
I noticed the other day that the LED scheduler on my router stopped working. I found this was due to all CRON jobs being deleted apart from 5 Diversion related ones. I did a forced update to all my addons (scMerlin, ntpMerlin, conmon, Diversion, etc.) and they all seemed to be restored. I’ve just checked scMerlin again and they have all been deleted apart from 5 Diversion related jobs. Any idea whats going on or how to fix it?
 
I'm pretty sure this problem has been discussed before. Use The Better Search function to try and find those posts.
 
I’ve searched through previous posts, but not sure if anything fits the bill exactly, might just be my lack of knowledge.

Still having the problem, but found out that if i reboot the router, then all the cron jobs are listed. When it goes wrong, just the 5 Diversion jobs are listed. Had the issue again today at the same time as lost all wifi connection to router for a couple of mins, not sure if related or not.

System log from around the time is below, not sure what it means though…

Nov 24 13:42:49 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Nov 24 13:42:56 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
Nov 24 13:43:00 wsdd2[18379]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:43:08 wsdd2[18379]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:43:15 wsdd2[18379]: Terminated received.
Nov 24 13:43:17 wsdd2[31480]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:44:47 wsdd2[31480]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:44:47 wsdd2[31480]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:44:47 wsdd2[31480]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:44:55 wsdd2[31480]: Terminated received.
Nov 24 13:46:31 pixelserv-tls[8091]: 105647 uts, 1 log, 0 kcc, 5 kmx, 0.14 kvg, 2 krq, 4278 req, 15 avg, 602 rmx, 2 tav, 411 tmx, 8 slh, 3 slm, 0 sle, 58 slc, 4203 slu, 23 v13, 43 v12, 0 v10, 0 zrt, 8 uca, 0 ucb, 2060 uce, 1990 ush, 500 sct, 4244 sch, 16 scm, 16 scp, 5 ssh, 1 ssm, 0 ssp, 1 nfe, 0 gif, 0 ico, 0 txt, 0 jpg, 0 png, 0 swf, 0 ufe, 0 opt, 13 pst, 0 hed, 0 rdr, 0 nou, 0 pth, 0 204, 0 bad, 58 cls, 0 cly, 0 clt, 0 err
Nov 24 13:46:49 wsdd2[27833]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:46:49 wsdd2[27833]: Terminated received.
Nov 24 13:46:50 kernel: *** ERROR: [udb_shell_mod_exit:661] Udb static = 0, dynamic = 48
Nov 24 13:46:50 Mastiff: Got SIGTERM
Nov 24 13:46:54 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
May 5 06:05:02 kernel: brcmboard registered
May 5 06:05:02 kernel: genirq: Flags mismatch irq 36. 00000000 (brcm_36) vs. 00000000 (brcm_36)
May 5 06:05:02 kernel: pci 0000:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 06:05:02 kernel: pci 0000:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 06:05:02 kernel: pci 0001:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 06:05:02 kernel: pci 0001:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 06:05:02 kernel: broadcomThermalDrv brcm-therm: init (CPU count 4 4 4 4)
May 5 06:05:02 kernel: FPM Pool 0: invalid token 0x00808000 freed
May 5 06:05:02 kernel: FPM Pool 1: invalid token 0x206b8000 freed
May 5 06:05:03 kernel: eth5 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link UP at 1000 mbps full duplex
May 5 06:05:03 kernel: FPM Pool 1: invalid token 0x206d8000 freed
May 5 06:05:07 Mastiff: init
May 5 06:05:08 wsdd2[1178]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
May 5 06:05:11 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
May 5 06:05:14 wsdd2[1178]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Nov 24 13:47:41 wsdd2[1178]: Terminated received.
Nov 24 13:47:43 wsdd2[3688]: Terminated received.
Nov 24 13:47:47 wsdd2[3929]: Terminated received.
Nov 24 13:48:21 crond[1098]: time disparity of 1871083 minutes detected
 
Your log file looks odd. The May 5 entries suggest that the router as rebooted, but it's missing all the other usual boot-up messages. At 13:47 there appear to be 3 copies wsdd2 being shut down which doesn't seem normal.

But probably the main issue is at the being where the router's connection to modem is lost. You've probably go some custom scripts that can't handle that situation. I'd investigate the modem logs first to see if there's a problem there.
 
I’ve searched through previous posts, but not sure if anything fits the bill exactly, might just be my lack of knowledge.

Still having the problem, but found out that if i reboot the router, then all the cron jobs are listed. When it goes wrong, just the 5 Diversion jobs are listed. Had the issue again today at the same time as lost all wifi connection to router for a couple of mins, not sure if related or not.
I have found that the cron jobs can be lost depending on what event triggers a restart of certain systems.

In this case, open the various event scripts in jffs, find the one that only has the diversion items, and either add the other cron entries to that script or call another script that contains them. Having the same cron entries in different scripts won't hurt, because it'll just overwrite the existing cron job (well, you need to remember to update and keep them all harmonized or you could end up with dupes, I suppose).

When trying to track down what erased my cron jobs a year or so ago, I added a line to the start of each script logger -s -p user.info NOTE WAN-EVENT (change the name of the event to whatever the script is, obvs) to log the event so I would know when a particular event got triggered, so I could add or call the missing cron jobs.
 
I’ve disabled Diversion via the GUI, and no issues what so ever for a week now. I’ll try re-enabling Diversion and see what happens…
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Top