Re: pg_dump version mismatch
Thats why I added the -i flag to the pg_dump call as it specifically
addresses this minor issue. From pg_dump docs:
-i
--ignore-version
Ignore version mismatch between pg_dump and the database server.
pg_dump can handle databases from previous releases of PostgreSQL,
but very old versions are not supported anymore (currently prior to
7.0). Use this option if you need to override the version check (and
if pg_dump then fails, don't say you weren't warned).
A minor version mismatch (which it appears you are running into)
shouldn't cause any problems.
Jason
On Aug 6, 9:11 pm, sthapit wrote:
> I'm auto backing up my database to S3 using code
> fromhttp://github.com/jpearl/heroku_backupsbut it's giving me this error:
>
> pg_dump: server version: 8.3.11; pg_dump version: 8.3.7
> pg_dump: proceeding despite version mismatch
>
> Can someone help? I've pasted the pg_dump code below.
>
> def get_db_settings
> database_url = ENV['DATABASE_URL']
> matches = database_url.match(/postgres:\/\/([^:]+):([...@]+)@([^\/]+)\/
> (.+)/)
> {:username => matches[1], :password => matches[2], :host =>
> matches[3], :db_name => matches[4]}
> end
>
> def pg_dump(filename)
> settings = get_db_settings
> ENV['PGPASSWORD'] = settings[:password]
> `pg_dump -i -h #{settings[:host]} -U #{settings[:username]} -F c
> #{settings[:db_name]} > "tmp/#{filename}.pgdump"`
> filename
> end
--
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: push succeeds but app fails to start, what am i doing wrong?
It's a known problem with Bundler and git paths. Have a look here http://docs.heroku.com/bundler100rc2-git and http://groups.google.com/group/heroku/browse_thread/thread/f33a79310c0fef4d Steve -- http://cloudmailin.com @cloudmailin Incoming email for your web app On Aug 12, 6:05 pm, problemblog wrote: > I have the following two lines in my Gemfile > > gem 'gdata4ruby', '0.1.3', :git => 'git://github.com/mjreich/ > GData4Ruby.git' > gem 'gcal4ruby', '0.5.5', :git => 'git://github.com/mjreich/ > GCal4Ruby.git' > > however, when I push this to Heroku (push ends successfully) I get > the > following app error. > > App failed to start > Check out the troubleshooting section on our Documentation site. > > Original Error > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc.2/lib/ > bundler/ > source.rb:552:in `rescue in load_spec_files': > git://github.com/mjreich/GData4Ruby.git > (at master) is not checked out. Please run `bundle install` > (Bundler::PathError) > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/source.rb:549:in `load_spec_files' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/source.rb:371:in `local_specs' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/source.rb:534:in `specs' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/lazy_specification.rb:48:in `__materialize__' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/spec_set.rb:83:in `block in materialize' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/spec_set.rb:81:in `map!' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/spec_set.rb:81:in `materialize' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/definition.rb:93:in `specs' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/definition.rb:125:in `specs_for' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/definition.rb:114:in `requested_specs' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/environment.rb:23:in `requested_specs' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler/runtime.rb:11:in `setup' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. > 2/lib/ > bundler.rb:102:in `setup' > from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/boot.rb: > 8:in `' > from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ > application.rb: > 1:in `require' > from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ > application.rb: > 1:in `' > from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ > environment.rb: > 2:in `require' > from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ > environment.rb: > 2:in `' > from config.ru:3:in `require' > from config.ru:3:in `block (3 levels) in ' > from /home/heroku_rack/heroku.ru:26:in `eval' > from /home/heroku_rack/heroku.ru:26:in `block (3 levels) in ' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:46:in `instance_eval' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:46:in `initialize' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:63:in `new' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:63:in `map' > from /home/heroku_rack/heroku.ru:21:in `block (2 levels) in ' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:46:in `instance_eval' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:46:in `initialize' > from /home/heroku_rack/heroku.ru:14:in `new' > from /home/heroku_rack/heroku.ru:14:in `block in ' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:46:in `instance_eval' > from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ > 1.9.1/gems/ > rack-1.1.0/lib/rack/builder.rb:46:in `initialize' > from /home/heroku_rack/heroku.ru:1:in `new' > from /home/heroku_rack/heroku.ru:1:in `' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ > rack/ > adapter/loader.rb:36:in `eval' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ > rack/ > adapter/loader.rb:36:in `load' > from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ > thin/ > controllers/controller.rb:175:in `
push succeeds but app fails to start, what am i doing wrong?
I have the following two lines in my Gemfile gem 'gdata4ruby', '0.1.3', :git => 'git://github.com/mjreich/ GData4Ruby.git' gem 'gcal4ruby', '0.5.5', :git => 'git://github.com/mjreich/ GCal4Ruby.git' however, when I push this to Heroku (push ends successfully) I get the following app error. App failed to start Check out the troubleshooting section on our Documentation site. Original Error /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc.2/lib/ bundler/ source.rb:552:in `rescue in load_spec_files': git://github.com/mjreich/GData4Ruby.git (at master) is not checked out. Please run `bundle install` (Bundler::PathError) from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/source.rb:549:in `load_spec_files' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/source.rb:371:in `local_specs' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/source.rb:534:in `specs' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/lazy_specification.rb:48:in `__materialize__' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/spec_set.rb:83:in `block in materialize' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/spec_set.rb:81:in `map!' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/spec_set.rb:81:in `materialize' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/definition.rb:93:in `specs' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/definition.rb:125:in `specs_for' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/definition.rb:114:in `requested_specs' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/environment.rb:23:in `requested_specs' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler/runtime.rb:11:in `setup' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/bundler-1.0.0.rc. 2/lib/ bundler.rb:102:in `setup' from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/boot.rb: 8:in `' from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ application.rb: 1:in `require' from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ application.rb: 1:in `' from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ environment.rb: 2:in `require' from /disk1/home/slugs/223747_57f5765_4c81/mnt/config/ environment.rb: 2:in `' from config.ru:3:in `require' from config.ru:3:in `block (3 levels) in ' from /home/heroku_rack/heroku.ru:26:in `eval' from /home/heroku_rack/heroku.ru:26:in `block (3 levels) in ' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:46:in `instance_eval' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:46:in `initialize' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:63:in `new' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:63:in `map' from /home/heroku_rack/heroku.ru:21:in `block (2 levels) in ' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:46:in `instance_eval' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:46:in `initialize' from /home/heroku_rack/heroku.ru:14:in `new' from /home/heroku_rack/heroku.ru:14:in `block in ' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:46:in `instance_eval' from /home/slugs/223747_57f5765_4c81/mnt/.bundle/gems/ruby/ 1.9.1/gems/ rack-1.1.0/lib/rack/builder.rb:46:in `initialize' from /home/heroku_rack/heroku.ru:1:in `new' from /home/heroku_rack/heroku.ru:1:in `' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ rack/ adapter/loader.rb:36:in `eval' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ rack/ adapter/loader.rb:36:in `load' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ thin/ controllers/controller.rb:175:in `load_rackup_config' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ thin/ controllers/controller.rb:65:in `start' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ thin/ runner.rb:177:in `run_command' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/lib/ thin/ runner.rb:143:in `run!' from /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/thin-1.2.6/bin/ thin:6:in `' from /usr/ruby1.9.1/bin/thin:19:in `load' from /usr/ruby1.9.1/bin/thin:19:in `' -- You receive
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". 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...@googleg
Re: workers crashing....
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". 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 >
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 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,
Re: Use Heroku gem from within application?
Hey, look at this cool blog post, it's for an other problem, but I think it's that what you need. http://blog.darkhax.com/2010/07/30/auto-scale-your-resque-workers-on-heroku Mit freundlichen Grüßen Daniel Spangenberg daniel.spangenb...@gmail.com Am 12.08.2010 um 18:13 schrieb Brett: > Hi all, > > I want to let users purchase custom domain names to access my app on > Heroku. When the purchase transaction takes place, I'd like to add > the custom domain to my app in real time. I thought of using the > Heroku gem/command line tool from within the app, analagous to the > command-line expression: > heroku domains:add www.example.com > > Is this possible? If so, what is the syntax? > > Thanks! > > Brett > > > -- > 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....
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 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.
Use Heroku gem from within application?
Hi all, I want to let users purchase custom domain names to access my app on Heroku. When the purchase transaction takes place, I'd like to add the custom domain to my app in real time. I thought of using the Heroku gem/command line tool from within the app, analagous to the command-line expression: heroku domains:add www.example.com Is this possible? If so, what is the syntax? Thanks! Brett -- 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....
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....
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.
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.
Re: Workflow to allow heroku to install a 'private' (local) gem on deploy
On Aug 12, 2010, at 3:34 AM, Bradley wrote: >> Right, so I added in: >> >> Host heroku.com >> ForwardAgent yes >> >> to my Tomcat user's ~/.ssh/config. This is the user that checks out >> from Github then pushes to heroku. I still get the same error, >> Permission denied (publickey). Hi, Brad -- I've just done an experiment here, pushing to Heroku (with and without ForwardAgent turned on) a small Rack app having a Gemfile specifying a dependency on a privately-accessible-over-ssh git repository. It didn't work. I see the same error you do. As I Google, I'm suspecting this is because of the way Heroku's ssh authorized_keys file is configured. It turns out there's a setting called "no-agent-forwarding" that keeps turning up in [people's][1] [examples][2] for how to configure git access over ssh. (See [sshd(8)][3] for more.) Heroku guys, would any of you be able to confirm that these "no-agent-forwarding" clauses are present in (the equivalent of) the ~/.ssh/authorized_keys file for g...@heroku.com? Do I understand correctly that removing them would enable Brad's use case here? On Aug 12, 2010, at 3:39 AM, David Balatero wrote: > If Bundler is running on Heroku, the Heroku UNIX user account needs to have > its public key in your Github repo as an authorized key. > > Each Heroku machine will have a different SSH key generated, and you > non-deterministically deploy to machine in the Heroku cloud each time > you deploy. > > Even if you had a consistent SSH key, it would be insecure for you to add > that key to your public repo, as anyone else deploying to the same machine as > you would be able to download your code repo. Hi, David -- Yes, exactly -- this multiple-host inconsistency / insecurity is what I suspect we'd be able to overcome with ssh's agent forwarding. It would transitively allow (bundler running on) Heroku to connect to Brad's private repository using his local ssh keys. All the best, -- Matthew [1]: http://stackoverflow.com/questions/3224340/git-push-returns-fatal-protocol-error-bad-line-length-character [2]: http://eagain.net/blog/2007/03/22/howto-host-git.html [3]: http://www.manpagez.com/man/8/sshd/ Oy, that's an ugly page! -- 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: Rails 3 doesn't officially support Ruby 1.9.1
Hi, 1.9.2 is almost here and as @heroku team mentioned : "We will add support for 1.9.2 when the community releases the official release" http://blog.heroku.com/archives/2010/6/15/rails_3_beta_4_on_heroku/ 1.9.2 is for mid-aug, it is really a question of days now :) Until that, we stick to Ruby 1.8.7 and Rails3 RC, which is perfectly fine. Regards, On Thu, Aug 12, 2010 at 8:52 AM, Stefan Wintermeyer < stefan.winterme...@amooma.de> wrote: > Am 11.08.2010 um 23:43 schrieb Abel Tamayo: > > The best you can do is either find a deployment stack with the > specifications you're using or adapt your environment to what is offered by > Heroku. I'm checking the documents and it seems that Bamboo MRI supports > Ruby 1.9.1. > > What I don't get is that it is fine for Heroku to offer Rails 3.0 beta but > they don't offer Ruby 1.9.2 beta. Even as the Rails-Team says itself that > Ruby 1.9.1 crashes all the time. > > I know that time will solve this issue. I was just searching for a solution > for my current problem. Now I have to host everything myself which I hate. > It is just the kind of work for which I happily pay a hosting provider for. > > Stefan > > -- > AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied --> http://www.amooma.de > Geschäftsführer: Stefan Wintermeyer, Handelsregister Montabaur B14998 > > Asterisk 1.6: http://das-asterisk-buch.de > Ruby on Rails 3: http://ruby-auf-schienen.de > Videos and slides of AMOOCON: http://amoocon.de > > -- > 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.
