That's how Heroku works - http://docs.heroku.com/performance#request-timeout. A console command is treated identically to a HTTP request.
Oren On Sun, Aug 1, 2010 at 6:57 PM, Mike <[email protected]> wrote: > Okay, actually fixed this, sort of, by updating my heroku gem. > > Now it now longer crashes and just quits the console and tells me that > it's timed out and I should run it as a rake task instead of from the > console. > > Overall behavior seems to be the same still, with the request > continuing to run on the dyno until completed. > > On Aug 1, 9:44 pm, Mike <[email protected]> wrote: >> I'm updating some data in my database, and running them through the >> Heroku console since we have no direct database access. >> >> I'm calling this like so: ActiveRecord::Base.connection.execute "MY >> SQL COMMAND;" >> >> The command takes about 5-10 minutes to run. >> >> Every time I run it, it's causing the console to crash, with the >> following message: >> /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/client.rb:202:in >> `console': undefined method `code' for nil:NilClass (NoMethodError) >> from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/commands/app.rb: >> 158:in `console_session' >> from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/commands/app.rb: >> 147:in `console' >> from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/command.rb:48:in >> `send' >> from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/command.rb:48:in >> `run_internal' >> from /var/lib/gems/1.8/gems/heroku-1.9.9/lib/heroku/command.rb:20:in >> `run' >> from /var/lib/gems/1.8/gems/heroku-1.9.9/bin/heroku:13 >> from /var/lib/gems/1.8/bin/heroku:19:in `load' >> from /var/lib/gems/1.8/bin/heroku:19 >> >> After that, apparently the command is continuing to run even though I >> have no access to the console, as for about the runtime of my command, >> the dyno continues to be completely tied up and non-responsive. >> Afterwards, I can connect to the console again, and the data appears >> upon first inspection to have been changed. >> >> Has anyone else seen behavior like this? Did your data integrity turn >> out okay in the end? > > -- > 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. > > -- 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.
