1.9.2 and daemonization

58 views
Skip to first unread message

Jeff McFadden

unread,
Oct 29, 2010, 10:30:17 PM10/29/10
to delayed_job
I'm on 1.9.2 and rails 2.3.10

When I run

$ rake:jobs work

everything is great. So the delayed handling is working just fine.


But when I run the

$ RAILS_ENV=development ./script/delayed_job start

I get

delayed_job: process with pid 7406 started.

But the process must be immediately dying, because it doesn't exist
when you look for it with 'ps', etc (and no progress is made on the
jobs in the db, of course).

Have anyone dealt with this? And solutions?

David Genord II

unread,
Nov 3, 2010, 9:20:56 AM11/3/10
to delay...@googlegroups.com
What version of delayed_job are you using?

David Genord II

Scott Johnson

unread,
Nov 5, 2010, 2:18:34 PM11/5/10
to delayed_job
I get the same behavior with the following versions:

ruby 1.9.2p0
rails 2.3.8
daemons-1.1.0
delayed_job-2.0.3

When I run `script/delayed_job run` I get the following:

/home/scottj/.gem/ruby/1.9.1/gems/activesupport-2.3.8/lib/
active_support/buffered_logger.rb:99:in `write': not opened for
writing (IOError)
from /home/scottj/.gem/ruby/1.9.1/gems/activesupport-2.3.8/lib/
active_support/buffered_logger.rb:99:in `block in flush'
from <internal:prelude>:10:in `synchronize'
from /home/scottj/.gem/ruby/1.9.1/gems/activesupport-2.3.8/lib/
active_support/buffered_logger.rb:96:in `flush'
from /home/scottj/.gem/ruby/1.9.1/gems/activesupport-2.3.8/lib/
active_support/buffered_logger.rb:116:in `auto_flush'
from /home/scottj/.gem/ruby/1.9.1/gems/activesupport-2.3.8/lib/
active_support/buffered_logger.rb:65:in `add'
from /home/scottj/.gem/ruby/1.9.1/gems/activesupport-2.3.8/lib/
active_support/buffered_logger.rb:72:in `fatal'
from /home/scottj/.gem/ruby/1.9.1/gems/delayed_job-2.0.3/lib/delayed/
command.rb:95:in `rescue in run'
from /home/scottj/.gem/ruby/1.9.1/gems/delayed_job-2.0.3/lib/delayed/
command.rb:77:in `run'
from /home/scottj/.gem/ruby/1.9.1/gems/delayed_job-2.0.3/lib/delayed/
command.rb:72:in `block in run_process'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
application.rb:250:in `call'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
application.rb:250:in `block in start_proc'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
application.rb:261:in `call'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
application.rb:261:in `start_proc'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
application.rb:294:in `start'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
controller.rb:73:in `run'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons.rb:
193:in `block in run_proc'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
cmdline.rb:112:in `call'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons/
cmdline.rb:112:in `catch_exceptions'
from /home/scottj/.gem/ruby/1.9.1/gems/daemons-1.1.0/lib/daemons.rb:
192:in `run_proc'
from /home/scottj/.gem/ruby/1.9.1/gems/delayed_job-2.0.3/lib/delayed/
command.rb:71:in `run_process'
from /home/scottj/.gem/ruby/1.9.1/gems/delayed_job-2.0.3/lib/delayed/
command.rb:65:in `block in daemonize'
from /home/scottj/.gem/ruby/1.9.1/gems/delayed_job-2.0.3/lib/delayed/
command.rb:63:in `times'
from /home/scottj/.gem/ruby/1.9.1/gems/delayed_job-2.0.3/lib/delayed/
command.rb:63:in `daemonize'
from script/delayed_job:5:in `<main>'

Scott Johnson

unread,
Nov 11, 2010, 8:15:24 PM11/11/10
to delayed_job
Downgrading to daemons-1.0.10 seems to fix this problem for some
people. (Not for me).

https://github.com/collectiveidea/delayed_job/issues/#issue/81
Reply all
Reply to author
Forward
0 new messages