Update: I upgraded my stack to Ruby 1.9.1 and the crashes seem to have
stopped. (Knock wood!)
heroku stack:migrate bamboo-mri-1.9.1
On Jul 30, 10:28 am, Alex Chaffee ale...@gmail.com wrote:
What a useful command! Thanks.
Still, I don't know what I could be doing to cause DJ to crash.
What a useful command! Thanks.
Still, I don't know what I could be doing to cause DJ to crash.
Doesn't it catch all exceptions raised by jobs? My jobs are just doing
plain vanilla Ruby stuff...
- A
On Jul 29, 8:22 am, Dan Croak dcr...@thoughtbot.com wrote:
Only time I've had issues with
I wrote a simple Heroku app to do service monitoring. It uses
DelayedJob to queue up repeating tasks like doing an HTTP ping of a
server once a minute or once an hour.
Twice now the worker has died overnight. heroku workers still says
I'm running 1 worker, but there's no message in heroku logs --
Only time I've had issues with workers is when I messed up something
on my side so that I was causing DJ to crash. I debugged it by doing:
heroku ps
On Thu, Jul 29, 2010 at 11:10 AM, Alex Chaffee a...@cohuman.com wrote:
I wrote a simple Heroku app to do service monitoring. It uses
DelayedJob
That's a scary subject line!!
;)
-- Pito
On Thu, Jul 29, 2010 at 11:10 AM, Alex Chaffee a...@cohuman.com wrote:
I wrote a simple Heroku app to do service monitoring. It uses
DelayedJob to queue up repeating tasks like doing an HTTP ping of a
server once a minute or once an hour.
Twice now
