Closed jonpaul closed 13 years ago
It's failing to deserialize the YAML in a job handler. I've seen this happen when the YAML gets clipped by the database. Generally the root cause is a giant object structure in some instance variable that gets serialized along with the job.
Please take this to the mailing list if you have further problems.
This is basically a copy of my question here: http://stackoverflow.com/questions/5383625/delayed-job-returns-syntax-error-for-process-daemon-and-rake-task
However, it seemed appropriate to re-post the question in effort to generate some form of backlog for delayed_job.
Started to have an issue this afternoon with the delayed_job process, found that the daemons were dead and restarted them...
Roughly 40 minutes later the process died again @ 86 jobs. Tried to start the daemons again and found they quietly died immediately after I start them. Checking the log I found:
I went ahead and did some digging, a lot of people used to find the daemon gem for delayed_jobs was bugged, and the rake task still worked; this was not the case for me however:
Now I'm simply not sure what could possibly be the problem, any advice on how to get more information(or a more verbose exception) would be awesome. If anyone can help me to solve it, that'd be unbelievable. Thanks in advance--
Job.rb File: http://pastie.org/1697465