[Backgroundrb-devel] cron scheduling problem
thomas.a.wood at uconn.edu
Thu Jan 31 11:48:25 EST 2008
I'm running a fresh checkout of release 1.0.1 ...
It's now 11:32 am local time on January 31.
I've configured a single worker for a test.
If I use the following schedule in my background.yaml file:
:trigger_args: 0 35 11 * * * *
Backgroundrb starts up without error.
If I make the following change:
:trigger_args: 0 30 11 * * * *
`local': argument out of range (ArgumentError)
from script/backgroundrb:60:in `new'
A puts added to cron_trigger.rb reveals why Time.local is failing. When
the worker is scheduled to run at 11:35, Time.local is called ala:
Calling Time.local 0, 35, 11, 31, 1, 2008, 4, 31, false, EST
When the worker is scheduled to run at 11:30, Time.local fails and is
Calling Time.local 0, 30, 11, 32, 1, 2008, 4, 31, false, EST
"32" is not a valid day of the month.
I think the error is dependent on the time that backgroundrb starts.
When I waited until 11:40, backgroundrb started to generate the same
exception for the 11:35 worker.
thomas.a.wood at uconn.edu <mailto:thomas.a.wood at uconn.edu>
ITS Applications Developer
University of Connecticut Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Backgroundrb-devel