Jump to content
Sign in to follow this  

crond broke after upgrading to 6.4.1

3 posts in this topic Last Reply

Recommended Posts

I use the go script to populate my crontab.   All my jobs stopped after the upgrade however the crontab looked normal when running crontab -l


I had to add a killall crond and add /usr/sbin/crond to my go script to fix the issue. 


Seems odd why I would have to do this.  I see crond in the process table with a -l command switch.  Restarting crond fires off all my jobs no problem.


I run 3 unraid VM's and the behavior was confirmed on all 3.

Share this post

Link to post

I would like to second this.


I've spent the past couple of days trying to figure out why my scripts weren't running then stumbled across this post.


Killing crond and then starting it again fixes the issue.

Share this post

Link to post

It is recommended to use CA User Scripts instead of the 'go' file.


Share this post

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this