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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
