Heroku is supposed to restart a worker everytime it crashes. Whatever is in your jobs:work task will be executed as soon as it fails.
However, I run a very dependent on background jobs webapp in Heroku and this is not enough for me. What I did was create a rake task that finds the last record to be updated and issue a background job to update the next after that one and automate the task to find the rest of the records that need to be updated. The only thing you'll be able to do to interact with your app once it's deployed are Rake tasks. On Thu, Aug 12, 2010 at 5:54 PM, Chris Kalaboukis <[email protected]>wrote: > Possibly. Problem is I can't seem to catch it...do you know how I can, > other than running some monitor to restart. > > BTW, how do I restart a crashed job? Is there a way to do it from the > heroku command line? > > Thanks...Chris > > On Thu, 2010-08-12 at 17:47 +0200, Abel Tamayo wrote: > > Segmentation faults are the most mysterious of faults... could it be > > some incompatibility between Ruby 1.8.6 and the PostgreSQL adapter? > > > > On Thu, Aug 12, 2010 at 5:38 PM, Chris Kalaboukis > > <[email protected]> wrote: > > I think I found the culprit: > > > > ==> dj-1943630-crashlog.log <== > > (in /disk1/home/slugs/152245_4b6a640_e6b3/mnt) > > RPM Monitoring DJ worker host:railgun64.29102 pid:9157 > > ** [NewRelic] Connected to NewRelic Service at > > collector5.newrelic.com:80 > > ** [NewRelic] New Relic RPM Agent 2.12.3 Initialized: pid = > > 9157 > > ** [NewRelic] Agent Log found > > in > /disk1/home/slugs/152245_4b6a640_e6b3/mnt/log/newrelic_agent.log > > *** Starting job worker host:railgun64.29102 pid:9157 > > > /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/active_record/connection_adapters/postgresql_adapter.rb:1102: > [BUG] Segmentation fault > > ruby 1.8.6 (2008-08-11) [x86_64-linux] > > > > Any ideas on how to fix? > > > > > > > > On Thu, 2010-08-12 at 01:28 -0700, Chris Kalaboukis wrote: > > > Hi all: I've got workers crashing for no apparent reason. > > Have the > > > exception code in there but it just stops running and ps > > reports > > > "crashed". Neither heroku logs or New Relic have anything to > > add. > > > Where can I find out why a workers crashed like that? > > > > > > Thanks...Chris > > > > > > > > > -- > > You received this message because you are subscribed to the > > Google Groups "Heroku" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to heroku > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en. > > > > > > > > > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Heroku" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to heroku > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/heroku?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<heroku%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
