On Mon, Mar 30, 2009 at 3:29 PM, Till Vollmer <[email protected]> wrote: > Hi, > 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 consumption. > :backgroundrb: > :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 > :schedules: > :notification_worker: > :do_it: > :trigger_args: 0 30 */4 * * * * > We think that it might be related to daylight saving time. > Any hints appreciated.
Were you using reload_on_schedule ?? But yes, the bug do seem like triggered by DST, I will be pushing out an update that will contain the fix. BTW, were you able to recover the worker? _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
