[Backgroundrb-devel] Severe Bug with daylight saving time?
adam at thewilliams.ws
Mon Mar 30 09:47:38 EDT 2009
I have suffered the same way, and also believe it to be a time change
issue. We spent a good deal of time discovering, after the time change
a few weeks ago, that the schedule '0 0 0 * * * *' would no long work
at all. We are now running on '23 59 59 * * * *', and that seems to be
On Mar 30, 2009, at 5:59 AM, Till Vollmer wrote:
> we have encountered a severe bug in backgroundrb last weekend.
> On Sunday at 20:00 (EST) backgroundrb launched infinite workers of
> notification_worker and our server was killed because of memory
> :port: 11006
> :ip: 0.0.0.0
> :persistent_disabled: true # turn this off if your application
> doesn't use backgroundrb's persistent/enqueued tasks system
> :persistent_delay: 10 # the time (seconds) between each time
> backgroundrb checks the database for enqueued tasks
> :trigger_args: 0 30 */4 * * * *
> We think that it might be related to daylight saving time.
> Any hints appreciated.
> MindMeister - MeisterLabs GmbH
> Till Vollmer
> Managing Director
> Tel: +49 (0)89 1213 5359
> Mob: + 49 (0)160 718 7403
> Fax: +49 (0)89 1892 1347
> Yahoo ID: till_vollmer
> Skype: till_vollmer
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
More information about the Backgroundrb-devel