My delayed jobs are not running

907 views
Skip to first unread message

krish

unread,
Oct 14, 2010, 8:38:23 AM10/14/10
to delayed_job
We have amazon ec2 hosted debian server running ruby on rails site.

There was a contractor running the site and he has used the delayed
job to collect the feed from many other site. But now we have taken
over the maintenance but we could not get the delayed job working
correctly.

We could start the delayed job with -n 5 with production environment
but there was no sign of progress.

Does delayed job log the process stdout into log file? May I know
where the log files are stored?

Regards,

Krish,
http://stacked.in

David Genord II

unread,
Oct 15, 2010, 11:21:21 AM10/15/10
to delay...@googlegroups.com
All log and stdout output is sent to RAILS_ROOT/log/delayed_job.log This logging has been notoriously unstable though. Do you know what version of rails and delayed_job you are running?

David Genord II

James Cook

unread,
Oct 19, 2010, 5:10:13 AM10/19/10
to delayed_job
I have the same problem. My delayed_job is working when I'm running
the rake task but not when
I'm running the daemon, same for production and development. I can
start the daemon and the log file
is showing "[Worker(delayed_job host:eric-smith-macbook.local pid:
14809)] Starting job worker" but
it doesn't work off any jobs.

I'm running following gems:

rails-3.0.0
delayed_job-2.1.0.pre2
daemons-1.1.0

And I'm using the default config.
ActiveRecord as backend.

Regards

On Oct 15, 5:21 pm, David Genord II <albus...@gmail.com> wrote:
> All log and stdout output is sent to RAILS_ROOT/log/delayed_job.log This
> logging has been notoriously unstable though. Do you know what version of
> rails and delayed_job you are running?
>
> David Genord II
>

James Cook

unread,
Oct 19, 2010, 8:30:31 AM10/19/10
to delayed_job
Using the following gemfile works fine:

gem 'daemons', '1.0.10'
gem 'delayed_job', :git => 'git://github.com/collectiveidea/
delayed_job.git'

Sundus Yousuf

unread,
Dec 23, 2013, 12:21:04 PM12/23/13
to delay...@googlegroups.com
I had the same issue when using 'daemons' '1.1.9' as you recommended I moved to older version '1.0.10' and it works fine.
Do you have any idea why this is happening and should I be worried about having to use older version of 'daemons' ?
Reply all
Reply to author
Forward
0 new messages