Thanks,
Menno
The current method of daemonizing really sucks. I'd like to rewrite the background process to use a unicorn style pre-forking worker, but haven't had time to tackle it yet.
Brandon
Thanks,
Allan
Allan
On Feb 3, 11:22 pm, Nathan Phelps <nat...@nathanwphelps.com> wrote:
> THANK YOU Woody! This was indeed the issue. When in production the buffered
> log is set to an auto_flushing value of 1000 which means that flush is not
> called until 1000 messages have been logged. Assuming you're using
> collectiveidea's fork of delayed_job, you can address this by setting
> auto_flushing to a more reasonable value in command.rb right after the
> logger is initialized on line 64. I.E.
>
> Delayed::Worker.logger = Rails.logger
> Delayed::Worker.logger.auto_flushing = 1 # or whatever
>
> I'm so happy this is resolved. Like you Allen, it was driving me nuts!
>
> Thanks,
>
> Nathan
>
I see that you bumped the gemspec to 1.8.5 back when you fixed this,
but that version isn't on gemcutter yet. Would you mind publishing
v1.8.5 to gemcutter?
Thanks,
Ryan
On Feb 4, 10:35 am, Brandon Keepers <bran...@opensoul.org> wrote:
> Thanks for figuring that out. I'll apply the patch and push a new version today.
>
> Brandon
>
> On Feb 4, 2010, at 2:22 AM, Nathan Phelps wrote:
>
> > THANK YOU Woody! This was indeed the issue. When in production the buffered log is set to an auto_flushing value of 1000 which means that flush is not called until 1000 messages have been logged. Assuming you're using collectiveidea's fork of delayed_job, you can address this by setting auto_flushing to a more reasonable value in command.rb right after the logger is initialized on line 64. I.E.
>
> > Delayed::Worker.logger = Rails.logger
> > Delayed::Worker.logger.auto_flushing = 1 # or whatever
>
> > I'm so happy this is resolved. Like you Allen, it was driving me nuts!
>
> > Thanks,
>
> > Nathan
>