Re: Trace Application Error

2011-07-21 Thread batate 
We're considering moving away from Heroku for this reason. The logging
options are horrific, outside of advanced logging. We don't mind
paying for value, but logging should be a minimal base feature,
available to all. To add fuel to the fire, GetExceptional is now a fee-
only service. We love heroku, but it's rapidly moving out of our price
range with very basic add ons.

-bt

On Jul 20, 9:54 am, Daniele  wrote:
> Hi joshmckin,
> thank you very much for the support.
> I have tried to replicate the problem locally but I have found no
> error yet.
> I'm thinking a way to save the log realtime so I can parse it
> searching for the problem; the "advance" logging addon is out of my
> budget.
>
> On 20 Lug, 15:58, joshmckin  wrote:> I've had a similar 
> issue, since the application is crashing any system
> > built into the application for logging is crashing with it. New relic
> > can sometimes catch it but not always. Your best bet is build an
> > environment locally similar to Heroku (Nginx/Thin) and see if you can
> > replicate the error. For us it turned out Mysql2 gem was throwing
> > exceptions that would kill EventMachine and therefore kill Thin. Since
> > Thin was giving up its ghost, the logger would not record the
> > exception, once we were able to patch Mysql2 we were able to get to
> > the root exception.

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to heroku@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: Trace Application Error

2011-07-21 Thread Scott Watermasysk 
Heroku bills by the hour (even on add-ons). Why not turn it on, log your error, 
and then disable it? 

If the error is on Heroku's side you can then go back to them ask for a logging 
refund (not that they have to, but so far they have been very reasonable). 

-- 
Scott Watermasysk
Founder, KickoffLabs
Launch your dream in 60 seconds!
http://www.kickofflabs.com

On Wednesday, July 20, 2011 at 10:54 AM, Daniele wrote:

> Hi joshmckin,
> thank you very much for the support.
> I have tried to replicate the problem locally but I have found no
> error yet.
> I'm thinking a way to save the log realtime so I can parse it
> searching for the problem; the "advance" logging addon is out of my
> budget.
> 
> On 20 Lug, 15:58, joshmckin http://gmail.com)> wrote:
> > I've had a similar issue, since the application is crashing any system
> > built into the application for logging is crashing with it. New relic
> > can sometimes catch it but not always. Your best bet is build an
> > environment locally similar to Heroku (Nginx/Thin) and see if you can
> > replicate the error. For us it turned out Mysql2 gem was throwing
> > exceptions that would kill EventMachine and therefore kill Thin. Since
> > Thin was giving up its ghost, the logger would not record the
> > exception, once we were able to patch Mysql2 we were able to get to
> > the root exception.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Heroku" group.
> To post to this group, send email to heroku@googlegroups.com 
> (mailto:heroku@googlegroups.com).
> To unsubscribe from this group, send email to 
> heroku+unsubscr...@googlegroups.com 
> (mailto: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 heroku@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: Anyone having trouble using heroku console?

2011-07-21 Thread Terence Lee 
That's a good point. We'll take a look at adding something here.

-Terence

On Thu, Jul 14, 2011 at 4:48 PM, Francois  wrote:

> Terence
>  this error has been happening to a lot of people, it might be worth
> mentioning this in the docs somewhere? I searched for 'uninitialized
> constant Rake::DSL' in the docs and there was no mention.
>
> - F
>
> On Jul 14, 10:53 am, Terence Lee  wrote:
> > Hello Keenan,
> >
> > It's because rake is built into ruby 1.9.2 and the version is 0.8.7 and
> > that's the one being called here. We're looking into ways to fix this. In
> > the meantime, can you try hard coding your rake to 0.8.7 in your Gemfile?
> > Once you have that working locally, it should work fine on heroku.
> >
> > Best,
> > Terence
> >
> >
> >
> > On Wed, Jul 13, 2011 at 9:06 AM, Keenan Brock 
> wrote:
> > >  Hi,
> >
> > > Question: Are others able to run: heroku rake db:migrate OR heroku
> console
> > > "puts Model.count" ?
> >
> > > This is probably user error, but I can't figure it out. reminds me of
> not
> > > specifying RAILS_ENV when running rails console.
> >
> > > I had run rake db:seed which populated the Avatar model.
> > > I view a page on the website that relies upon the Avatar model.
> > > I ran heroku config:add RAILS_ENV=production (just in case)
> >
> > > But from heroku console:
> >
> > > *> puts Avatar.count*
> > > ActiveRecord::StatementInvalid: PGError: ERROR:  relation "avatars"
> does
> > > not exist
> > > : SELECT a.attname, format_type(a.atttypid, a.atttypmod),
> > > d.adsrc, a.attnotnull
> > >   FROM pg_attribute a LEFT JOIN pg_attrdef d
> > > ON a.attrelid = d.adrelid AND a.attnum = d.adnum
> > >  WHERE a.attrelid = '"avatars"'::regclass
> > >AND a.attnum > 0 AND NOT a.attisdropped
> > >  ORDER BY a.attnum
> >
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/activerecord-3.0.9/lib/active_record/conn
> ection_adapters/abstract_adapter.rb:207:in
> > > `rescue in log'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/activerecord-3.0.9/lib/active_record/conn
> ection_adapters/abstract_adapter.rb:199:in
> > > `log'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/activerecord-3.0.9/lib/active_record/conn
> ection_adapters/postgresql_adapter.rb:501:in
> > > `query'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/activerecord-3.0.9/lib/active_record/conn
> ection_adapters/postgresql_adapter.rb:1037:in
> > > `column_definitions'
> >
> > > *> heroku rake db:migrate*
> >
> > > (in /app)
> > > rake aborted!
> > > uninitialized constant Rake::DSL
> > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2482:in `const_missing'
> > > /app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:8:in
> > > `'
> > > /app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:6:in
> > > `'
> > > /app/.bundle/gems/ruby/1.9.1/gems/rake-0.9.2/lib/rake/tasklib.rb:3:in
> ` > > (required)>'
> > > /app/.bundle/gems/ruby/1.9.1/gems/rdoc-3.8/lib/rdoc/task.rb:37:in
> `require'
> > > /app/.bundle/gems/ruby/1.9.1/gems/rdoc-3.8/lib/rdoc/task.rb:37:in ` > > (required)>'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks/documentat
> ion.rake:2:in
> > > `require'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks/documentat
> ion.rake:2:in
> > > `'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb:15:in
> > > `load'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb:15:in
> > > `block in '
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb:6:in
> > > `each'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/tasks.rb:6:in
> > > `'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/application.rb:2
> 15:in
> > > `require'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/application.rb:2
> 15:in
> > > `initialize_tasks'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/application.rb:1
> 39:in
> > > `load_tasks'
> > >
> /app/.bundle/gems/ruby/1.9.1/gems/railties-3.0.9/lib/rails/application.rb:7
> 7:in
> > > `method_missing'
> > > /app/Rakefile:7:in `'
> > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `load'
> > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2373:in `raw_load_rakefile'
> > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2007:in `block in load_rakefile'
> > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2058:in
> `standard_exception_handling'
> > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:2006:in `load_rakefile'
> > > /usr/ruby1.9.2/lib/ruby/1.9.1/rake.rb:1991:in `run'
> > > /usr/ruby1.9.2/bin/rake:31:in `'
> >
> > > Thanks for any pointers on what I am doing wrong,
> > > Keenan
> >
> > > --Keenan
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Heroku" group.
> > > To post to this group, send email to heroku@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > heroku+unsubscr...@googlegroups.com.
> > > For more opt