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.

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.

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