Fun with Airbrake customer support

Exceptions going unreported

Clay Shentrup's Avatar

Clay Shentrup

Oct 01, 2013 @ 10:49 AM
We're experiencing exceptions on production leading to 500 errors, but nothing new is making it to the exception list in Airbrake, nor are we getting email notifications. The only notifications I see are for repeats of exceptions that already existed prior to the new site rollout.
  1. SUPPORT STAFF2 Posted by Morgan on Oct 05, 2013 @ 01:31 PM
    Morgan's Avatar
    Hello Clay,
    Thank you for bringing this to our attention.
    Can you please provide your account's subdomain and the name of the project(s)
    effected [sic]?
    Please get back to us when we can, when I have that I will do some troubleshooting on the account and make a bug ticket for the developers to take action on.
  2. 3 Posted by Clay Shentrup on Oct 07, 2013 @ 10:30 AM
    Clay Shentrup's Avatar
    I just want to make absolutely sure you got this, seeing as how multiple of
    my replies failed permanently. 
    [I had replied to their automated email, which is supposed to post the message to this thread, an Sat, Oct 5, 2013 at 1:38 PM. But it failed permanently. I sent that permanently failure message back to them two more times, and only received one more failure reply, so I assumed that the second email had gone through. I finally checked back in on the 7th, via email, resulting in this post.]
  3. 4 Posted by Clay Shentrup on Oct 08, 2013 @ 11:33 AM
    Clay Shentrup's Avatar
    Could I get an update on this? We haven't had exception notifications for 7 days now. This is a pretty big deal for us. It seems to have perfectly coincided with the roll out of the new site, although that could indeed be a coincidence for all I know.
  4. SUPPORT STAFF5 Posted by Matt on Oct 09, 2013 @ 12:51 PM
    Matt's Avatar
    This issue has been resolved by our dev team. They have deployed the code to fix this issue. Unfortunately you will have to remove the addon from heroku, then re-add it again, but you will no longer run into this 401 issue.
    Let us know if you have any questions or run into any other issues.
  5. Matt closed this discussion on Oct 09, 2013 @ 12:51 PM.
  6. Clay Shentrup re-opened this discussion on Oct 09, 2013 @ 02:12 PM
  7. 6 Posted by Clay Shentrup on Oct 09, 2013 @ 02:12 PM
    Clay Shentrup's Avatar
    What does Heroku have to do with anything? We don't use Heroku.
  8. SUPPORT STAFF7 Posted by Ben Arent on Oct 09, 2013 @ 02:13 PM
    Ben Arent's Avatar
    Hi Clay, This looks like a bit of a mix up. I need to review this bug in more detail before I can tell you more.
  9. SUPPORT STAFF8 Posted by Ben Arent on Oct 09, 2013 @ 02:34 PM
    Ben Arent's Avatar
    Hi Clay,
    I looked at your app and it looks like it's reporting noticed just for NoMethodError: undefined methodto_sym' for nil:NilClas` Rake task, but may not be correctly setup for the rest of your app.
    Which version of the Gem are you using, and what's the output of config/initializers/airbrake.rb
  10. 9 Posted by Clay Shentrup on Oct 09, 2013 @ 03:34 PM
    Clay Shentrup's Avatar
    We're using version 3.1.14.
    I ran "rails runner config/initializers/airbrake.rb" but it doesn't output anything. Which makes sense to me, considering that file is just:
    Airbrake.configure do |config|
    config.api_key = 'our API key' end
    I did a puts on it and got:
    Note that the Airbrake testing rake task succeeds.
  11. 10 Posted by Clay Shentrup on Oct 10, 2013 @ 03:10 PM
    Clay Shentrup's Avatar
    Can I get an update? We're really suffering by not getting exception reporting.
  12. 11 Posted by Clay Shentrup on Oct 10, 2013 @ 03:31 PM
    Clay Shentrup's Avatar
    I just got a 422 that went unreported. The log says:
    Completed 422 Unprocessable Entity in 86ms
    ** [Airbrake] Failure: Net::HTTPRequestEntityTooLarge
  13. 12 Posted by Clay Shentrup on Oct 10, 2013 @ 05:24 PM
    Clay Shentrup's Avatar
    Now I'm getting a new exception, but it's not coming through in Pivotal Tracker.
    I refresh and it just never shows up. Yet repeats of OLD exceptions still show up in Tracker.
  14. 13 Posted by Clay Shentrup on Oct 11, 2013 @ 05:12 PM
    Clay Shentrup's Avatar
    Hi guys. Any updates. Haven't had fully functional exception tracking for about a week and a half now.
    [Update: as of today, October 14, it seems like the Pivotal Tracker integration is be working again.]

No comments: