Skip to content

Removal of Cron Jobs with Timeout - #589

Merged
ExtremeFiretop merged 1 commit into
ExtremeFiretop:devfrom
Martinski4GitHub:dev
Jul 31, 2026
Merged

Removal of Cron Jobs with Timeout#589
ExtremeFiretop merged 1 commit into
ExtremeFiretop:devfrom
Martinski4GitHub:dev

Conversation

@Martinski4GitHub

Copy link
Copy Markdown
Collaborator

Modified code that removes cron jobs from 3rd-party add-ons so that the cru command call has a timeout to prevent stuck commands.

Modified code that removes cron jobs from 3rd-party add-ons so that the cru command call has a timeout to prevent a stuck commands.
@Martinski4GitHub

Copy link
Copy Markdown
Collaborator Author

@ExtremeFiretop,

I saw the problem report on the SNB Forums about the cru command getting "stuck" while removing a cron job, so I decided to add a simple routine to prevent such a "stuck" command.

I don't know the reason for the cru command getting stuck, and instead of going into a "rabbit hole" or getting lost in the weeds investigating, for now I prefer to avoid the problem altogether, so at least the router is not left in a "hung" state.

Please take a look at the PR changes.

@ExtremeFiretop
ExtremeFiretop merged commit 72473f8 into ExtremeFiretop:dev Jul 31, 2026
1 check passed
@ExtremeFiretop

Copy link
Copy Markdown
Owner

I don't know the reason for the cru command getting stuck, and instead of going into a "rabbit hole" or getting lost in the weeds investigating
.

I feel this is targeted at me 😁 I was going to spend some time trying to get some theories tested. But I agree in the meantime just a simple escape is the best solution

@Martinski4GitHub

Copy link
Copy Markdown
Collaborator Author

I don't know the reason for the cru command getting stuck, and instead of going into a "rabbit hole" or getting lost in the weeds investigating
.

I feel this is targeted at me 😁 I was going to spend some time trying to get some theories tested. But I agree in the meantime just a simple escape is the best solution

At least for the next production release, the first priority (IMO) is to prevent the "hung" state. For the long run, we could spend some time investigating further what the issue is with the cru command, but as I mentioned, that might be a deep "rabbit hole" for which I don't have time at the moment.

I do recall in the past there were some issues with cron jobs going missing during reboots, and I believe that was fixed with an exclusive FLock. Perhaps there is some race condition somewhere that causes a deadlock??

Anyway, I'm being summoned for dinner, so talk to you later, bud.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants