Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have been using delayed_job successfully for a while. I upgraded my Rails installation and now when I run:
./script/delayed_job -n 4 start
to run 4 processes, all 4 processes are created. But they are silently killed immediately, leaving their pid files in RAILS_ROOT/tmp/pids.
This is for delayed_job version 1.8.4 and Rails 2.3.8.
Well I am a ridiculous person. I did NOT know about the “run” option, where I could run delayed_job in the foreground and see exactly what was happening. My database setup is unconventional for rails, and my delayed_job table is not in the same schema as is listed in my config/database.yml table.
The reason this worked before is that I had monkey-patched a vendored delayed_job gem to hardcode the schema where my delayed_jobs table lived. When I upgraded Rails, I upgraded and re-vendored several gems, thus overwriting my previous hard-coding.
Which is why I shouldn’t be doing that, I know. Lesson learned.