rake aborted! Don't know how to build task 'jobs:work'
hi guys: just installed the delayed_jobs gem and am now getting this error. rake aborted! Don't know how to build task 'jobs:work' Has anyone had this error? 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.
Re: workers crashing....
Thats what I'm saying. They aren't restarting at all. I guess I need to file a ticket? On Thu, 2010-08-12 at 18:46 +0200, Abel Tamayo wrote: > It's done automatically. You don't have to select or configure > anything. > > On Thu, Aug 12, 2010 at 6:33 PM, Chris Kalaboukis > wrote: > Hi Abel: > > For some reason, its not restarting the job. Is there a way to > change > that setting - its not re-starting the job its just hanging > there. i > need it to restart when it fails, can you tell me what I need > to edit in > order to make it do that? > > Thanks...Chris > > > On Thu, 2010-08-12 at 18:15 +0200, Abel Tamayo wrote: > > 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 > > 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 > > > 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&q
Re: workers crashing....
Hi Abel: For some reason, its not restarting the job. Is there a way to change that setting - its not re-starting the job its just hanging there. i need it to restart when it fails, can you tell me what I need to edit in order to make it do that? Thanks...Chris On Thu, 2010-08-12 at 18:15 +0200, Abel Tamayo wrote: > 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 > 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 > > 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 > 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. > > > > > > > > > > > > > -- > > 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. > > > > -- > > You received this m
Re: workers crashing....
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 > 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 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. > > > > > > -- > 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. -- 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.
Re: workers crashing....
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.
workers crashing....
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.
Re: Running Memcached
Heroku told me to add that to my manifest... On Wed, 2010-08-11 at 23:38 +0200, Abel Tamayo wrote: > Why are you installing memcached-northscale instead of just memcached? > > On Wed, Aug 11, 2010 at 12:34 AM, Chris Kalaboukis > wrote: > Hi guys: I've just installed Memcached and my development > environment > is hosed - responds with > > > ch...@chris-laptop:~/strong-fog-31$ ruby script/server > => Booting WEBrick > => Rails 2.3.8 application starting on http://0.0.0.0:3000 > Missing these required gems: > memcached-northscale > > You're running: > ruby 1.8.7.249 at /usr/bin/ruby1.8 > rubygems 1.3.5 > at /home/chris/.gem/ruby/1.8, /var/lib/gems/1.8 > > Run `rake gems:install` to install the missing gems. > ch...@chris-laptop:~/strong-fog-31$ rake gems:install > (in /home/chris/strong-fog-31) > DEPRECATION WARNING: Rake tasks in > vendor/plugins/delayed_job/tasks > and vendor/plugins/jrails/tasks are deprecated. Use lib/tasks > instead. > (called > from /home/chris/.gem/ruby/1.8/gems/rails-2.3.8/lib/tasks/ > rails.rb:10) > rake aborted! > no such file to load -- memcached > > (See full trace by running task with --trace) > ch...@chris-laptop:~/strong-fog-31$ ruby script/generate > migration > archivecapture > Missing these required gems: > memcached-northscale > > You're running: > ruby 1.8.7.249 at /usr/bin/ruby1.8 > rubygems 1.3.5 > at /home/chris/.gem/ruby/1.8, /var/lib/gems/1.8 > > Run `rake gems:install` to install the missing gems. > > So when i try to run rake, it craps out. Does anyone know how > I can > edit my config so I can get this working again? > > 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. > > > > > -- > 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. -- 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.
Running Memcached
Hi guys: I've just installed Memcached and my development environment is hosed - responds with ch...@chris-laptop:~/strong-fog-31$ ruby script/server => Booting WEBrick => Rails 2.3.8 application starting on http://0.0.0.0:3000 Missing these required gems: memcached-northscale You're running: ruby 1.8.7.249 at /usr/bin/ruby1.8 rubygems 1.3.5 at /home/chris/.gem/ruby/1.8, /var/lib/gems/1.8 Run `rake gems:install` to install the missing gems. ch...@chris-laptop:~/strong-fog-31$ rake gems:install (in /home/chris/strong-fog-31) DEPRECATION WARNING: Rake tasks in vendor/plugins/delayed_job/tasks and vendor/plugins/jrails/tasks are deprecated. Use lib/tasks instead. (called from /home/chris/.gem/ruby/1.8/gems/rails-2.3.8/lib/tasks/ rails.rb:10) rake aborted! no such file to load -- memcached (See full trace by running task with --trace) ch...@chris-laptop:~/strong-fog-31$ ruby script/generate migration archivecapture Missing these required gems: memcached-northscale You're running: ruby 1.8.7.249 at /usr/bin/ruby1.8 rubygems 1.3.5 at /home/chris/.gem/ruby/1.8, /var/lib/gems/1.8 Run `rake gems:install` to install the missing gems. So when i try to run rake, it craps out. Does anyone know how I can edit my config so I can get this working again? 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.
Programmatically Spinning Workers Up and Down
Hi guys: I saw an old thread on this but there seemed to be no answer. Is there a way within my app to shut down and restart all the workers programmatically? I have a twitter harvesting app which requires it and I need to do it manually. Is there a doc somewhere which describes how to do it? 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.
