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

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

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

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

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 t

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,

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, >

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 b

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 express

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

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_4b6a6

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 = 9

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

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

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.