What's new

cronjob time is out by 1 hour

  • 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!

ilium007

Regular Contributor
Hi guys - I have a scheduled reboot that is supposed to happen at 5:00am but happens at 6:00 instead.

NTP time is correct. I am in Brisbane, Australia and we have no daylight saving but our southern states do. Whilst I have selected +10:00 Brisbane in the UTC offset window and the output of the 'date' command is correct , my scheuled reboot happens each day at 6:00am. Is it possible that there is a daylight saving setting somewhere ?

The "cru l" output is:

* 5 * * * reboot #scheduled_reboot#
 
Hi guys - I have a scheduled reboot that is supposed to happen at 5:00am but happens at 6:00 instead.

NTP time is correct. I am in Brisbane, Australia and we have no daylight saving but our southern states do. Whilst I have selected +10:00 Brisbane in the UTC offset window and the output of the 'date' command is correct , my scheuled reboot happens each day at 6:00am. Is it possible that there is a daylight saving setting somewhere ?

The "cru l" output is:

* 5 * * * reboot #scheduled_reboot#

I think I found it. The cru command should have been:

cru a scheduled_reboot "0 5 * * * reboot"

Without the 0 it would have been rebooting every 5 hours and given it was rebooting at 6am that means I would have last rebooted the router at 11pm which would be about right. I got confused when the reboot was happening at 6am thinking it was a daylight saving issue when in fact it was my cron mistake !
 

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!
Top