chaperone
chaperone copied to clipboard
garywiz
Chaperone with cron job got crazy on DST change
If cron job is configured and DST change occurs Chaperone starts executing job in loop regardless cron configuration.
Log:
Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: Switching all chaperone logging to /dev/log Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: chaperone version 0.3.9, ready. start Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: cron service periodic_long_running.service scheduled using interval spec '* * * * *' Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: cron service periodic_long_running.service running CMD ( echo 'EXECUTION' ) Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: service periodic_long_running.service enabled, queueing start request Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: periodic_long_running.service attempting start '/bin/echo EXECUTION'... Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: cron service periodic_long_running.service running CMD ( echo 'EXECUTION' ) Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: service periodic_long_running.service enabled, queueing start request Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: REAP pid=8,status=0 Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: no child processes present Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: cron service periodic_long_running.service running CMD ( echo 'EXECUTION' ) Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: service periodic_long_running.service enabled, queueing start request Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: cron service periodic_long_running.service running CMD ( echo 'EXECUTION' ) Oct 29 02:58:50 d3a4d1f36a3a chaperone[1]: service periodic_long_running.service enabled, queueing start request
Test case: chaperone-dst-bug.tar.gz
To run test case. Execute attached archive and run ./run_test.sh. Script is using sudo command to change system datetime.
Disabling time sync may be required. (Note that Virtual Box Guest additions synchronizes your time with host clock)
Env: Ubuntu 14.04
Serious problem you've found there. I have been off this project for some time, but I don't want a bug like hanging around, so sometime over the next couple days I'll patch it, test it, and make another release. Thanks for bringing this to my attention.
I found and fixed the problem.
It was inside aiocron. Here is reported issue: https://github.com/gawel/aiocron/issues/7.