all exceptions are marked as "Action: Internal"

bumi's Avatar

bumi

14 Jun, 2012 09:48 AM

Hi,

we use:
Rails: 3.2.6
Rack: 1.4.1
Airbrake: 3.1.1
Ruby: 1.9.3

in one of our projects all exceptions are marked as "Action: Internal" thus no request/session information is provided (I assume).
When debugging that issue I found out that currently Airbrake::UserInformer and Airbrake::Rack are latest in the middleware stack - while in other projects (with airbrake 3.0.9) the Airbrake::Rack is inserted right after Foo::Application.routes.
I could not confirm that this fixes the error and I could not find anything related in the airbrake gem or in our application.
Do you have an idea what cases this?

Thanks!

P.S.
also RoutingErrors are sent to Airbrake even though they should be ignored by default, shouldn't they? - not sure if this relates to the same issue. Unfortunately I'm not too familiar with rails exception handling.

  1. Support Staff 2 Posted by Morgan on 14 Jun, 2012 04:59 PM

    Morgan's Avatar

    Hello Bumi,

    Thank you for raising this issue with us. An internal error does not actually happen on a web page, you assumed correctly this is why there is no request/session data. Please upgrade your AirBrake gem to 3.1.1 and let me know if this causes other errors to be reported beside those that are internal. Also if you want to ignore the internal errors just let me know and I will help you get them filtered out. Thank you for your patience with this issue, please let me know if upgrading to 3.1.1 does not allow for more reporting.

    From,
    Morgan

  2. 3 Posted by bumi on 14 Jun, 2012 05:33 PM

    bumi's Avatar

    Hi Morgan,

    thanks for your reply.
    We are already using the latest airbrake version 3.1.1.
    The described behavior occurs on an app with the following setup:
    Airbrake: 3.1.1
    Rails: 3.2.6
    Rack: 1.4.1
    Ruby: 1.9.3

  3. 4 Posted by bumi on 19 Jun, 2012 01:17 PM

    bumi's Avatar

    do you have any update for me on this? any idea? ;)
    I'm sure it's some issue on my side...
    thanks for your help.

  4. Support Staff 5 Posted by Morgan on 19 Jun, 2012 07:20 PM

    Morgan's Avatar

    Hello Bumi,

    I have escalated this issue to the development team in the form of an Issue Ticket, they will be able to solve this problem, I have also added your email to the ticket so that I can give you and update on the issue.
    It may also be useful to check that your configuration is correct!

    What is the output of the following:

    #run from the rails console
    Airbrake.configuration
    #locate and paste the contents of [Rails Root]/config/initializers/airbrake.rb
    
    #feel free to substitue your api_key from the output.
    #you can paste output in this ticket or link gists
    

    Thank you for your patience on this issue!

    From,
    Morgan

  5. 6 Posted by Rob Holland on 20 Jun, 2012 07:53 PM

    Rob Holland's Avatar

    We're also seeing the same issue, same stack as bumi.

  6. 7 Posted by delorum on 22 Jun, 2012 05:09 PM

    delorum's Avatar

    We're also seeing the same issue, we have an identical stack to bumi and Rob Holland.

    Here's a gist with the results of Airbrake.configuration and the contents of config/initializers/airbrake.rb: https://gist.github.com/a8ee0ad87cf721460145

  7. 8 Posted by Dean Holdren on 22 Jun, 2012 06:51 PM

    Dean Holdren's Avatar

    I had the same issue, I found the bug and was going to post a fix, but this commit (yesterday) has the side effect of solving the problem (see my comment for an alternative fix):

    https://github.com/airbrake/airbrake/commit/cc97d5b50899848bd0aeb60...

  8. Support Staff 9 Posted by Morgan on 22 Jun, 2012 07:20 PM

    Morgan's Avatar

    Hello Everyone,

    I apologize for the trouble you have had with this issue! Herb form our development team has recently posted the above fix mentioned by Dean, Please point your Airbrake Gem to the github version for now in your gemfile:

    gem 'airbrake', :git => 'git@github.com:airbrake/airbrake.git'
    

    Until 3.1.2 has been released. Dean, great job making an alternate fix! Please let me know if your issues persist after updating your gem to the Github version. Alternately you could mimic the same adjustments in your own gem just like the commit Herb made.

    From,
    Morgan

  9. Morgan closed this discussion on 22 Jun, 2012 07:20 PM.

Comments are currently closed for this discussion. You can start a new one.