Resque command works from terminal but not via bluepill. Please help!

34 views
Skip to first unread message

rmossuk

unread,
Jul 12, 2011, 6:09:46 PM7/12/11
to Bluepill
Hi all


I am trying to get bluepill to monitor my resque workers.

If i run this command from my rails root as root user it starts up
resque worker ok.

cd /var/www/domain.com/current; RAILS_ENV=production QUEUE=* bundle
exec rake resque:work

but when i try to run it using bluepill it just keeps trying to start
it and doesnt give me an error.

Here is my bluepill log showing it trying....!

W, [2011-07-12T22:58:21.640467 #19267] WARN -- : [domain.com:resque]
Executing start command: cd /var/www/domain.com/current;
RAILS_ENV=production QUEUE=* bundle exec rake resque:work
I, [2011-07-12T22:58:21.754392 #19267] INFO -- : [domain.com:resque]
Going from down => starting

I, [2011-07-12T22:59:21.334300 #19267] INFO -- : [domain.com:resque]
Going from starting => down
W, [2011-07-12T22:59:22.339873 #19267] WARN -- : [domain.com:resque]
Executing start command: cd /var/www/domain.com/current;
RAILS_ENV=production QUEUE=* bundle exec rake resque:work
I, [2011-07-12T22:59:22.479740 #19267] INFO -- : [domain.com:resque]
Going from down => starting

it keeps doing this over and over.


here is my .pill file process

app.process("resque") do |process|
process.start_command = "cd #{RAILS_ROOT}; RAILS_ENV=#{RAILS_ENV}
QUEUE=* bundle exec rake resque:work"
process.daemonize = true

process.start_grace_time = 10.seconds
process.stop_grace_time = 10.seconds
process.restart_grace_time = 10.seconds

end


I have tried to extend the start grace time for if its not loading in
the required time but not making a difference.


Please can anyone help with this ?


thanks in advance
Rick
Reply all
Reply to author
Forward
0 new messages