Exceptional test is not working for me

Messay's Avatar

Messay

02 Aug, 2011 04:31 AM

When I try to send a test exception with : exceptional test
I get the following message: Problem sending exception to Exceptional. Check your API key.

I followed some of the suggestions mentioned in the following post http://support.getexceptional.com/discussions/problems/199-no-worx-... but it is not working for me.
I am running:
exceptional (2.0.32)
Rails 2.3.8
ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]

Exceptional::Config.api_key returns
28b979f4d869daddbdf761fec579a41bc6d6f9a2

Exceptional::Config.should_send_to_api?
=> true

Exceptional.handle Exception.new('an error with a title I made up')
=> nil

  1. Support Staff 1 Posted by Ben on 03 Aug, 2011 01:40 PM

    Ben's Avatar

    It seems we actually had a problem in the API processing that affected some users but it is working again now. The root cause seemed to be a Amazon RDS connectivity issue that we did not handle well.

    I'm sorry this affected you. We are working on major architectural changes that will remove this as a future contention. The Exceptional team is expanding and our first commitment is to getting the service to work reliably, and better report issues on our status page. http://status.getexceptional.com/

    Apologies and many thanks for using Exceptional.

    Ben

  2. Ben closed this discussion on 03 Aug, 2011 01:40 PM.

  3. Messay re-opened this discussion on 03 Aug, 2011 02:22 PM

  4. 2 Posted by Messay on 03 Aug, 2011 02:22 PM

    Messay's Avatar

    I am still facing the same issue.

    Do I need to generate a new API key to get it to work?

  5. Support Staff 3 Posted by Ben on 03 Aug, 2011 02:25 PM

    Ben's Avatar

    Hi Messay. I will get one of our developers to review your account.

  6. 4 Posted by Messay on 03 Aug, 2011 06:14 PM

    Messay's Avatar

    I am not sure if this is helpful but in exceptional.log I see the following error when i run "exceptional test"

    [ERROR] (remote.rb:45:in call_remote') Wed Aug 03 18:12:00 UTC 2011 - Problem notifying Exceptional about the error [ERROR] (remote.rb:46:incall_remote') Wed Aug 03 18:12:00 UTC 2011 - execution expired (Timeout::Error): /usr/lib/ruby/1.8/timeout.rb:60:in open' | /usr/lib/ruby/1.8/net/http.rb:560:inconnect' | /usr/lib/ruby/1.8/net/http.rb:560:in connect' | /usr/lib/ruby/1.8/net/http.rb:553:indo_start' | /usr/lib/ruby/1.8/net/http.rb:542:in start' | /usr/lib/ruby/1.8/net/http.rb:1035:inrequest' | /usr/lib/ruby/1.8/net/http.rb:845:in post' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/lib/exceptional/remote.rb:36:incall_remote' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/lib/exceptional/remote.rb:21:in error' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/lib/exceptional/integration/tester.rb:10:intest' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/bin/exceptional:31 | /usr/bin/exceptional:19:in `load' | /usr/bin/exceptional:19

  7. 5 Posted by Messay on 04 Aug, 2011 12:50 PM

    Messay's Avatar

    When I run "exceptional test" I see the following in the exceptional.log file

    [ERROR] (remote.rb:45:in call_remote') Thu Aug 04 12:47:36 UTC 2011 - Problem notifying Exceptional about the error [ERROR] (remote.rb:46:incall_remote') Thu Aug 04 12:47:36 UTC 2011 - execution expired (Timeout::Error): /usr/lib/ruby/1.8/timeout.rb:60:in open' | /usr/lib/ruby/1.8/net/http.rb:560:inconnect' | /usr/lib/ruby/1.8/net/http.rb:560:in connect' | /usr/lib/ruby/1.8/net/http.rb:553:indo_start' | /usr/lib/ruby/1.8/net/http.rb:542:in start' | /usr/lib/ruby/1.8/net/http.rb:1035:inrequest' | /usr/lib/ruby/1.8/net/http.rb:845:in post' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/lib/exceptional/remote.rb:36:incall_remote' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/lib/exceptional/remote.rb:21:in error' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/lib/exceptional/integration/tester.rb:10:intest' | /usr/lib/ruby/gems/1.8/gems/exceptional-2.0.32/bin/exceptional:31 | /usr/bin/exceptional:19:in `load' | /usr/bin/exceptional:19

  8. Support Staff 6 Posted by stuartchaney22 on 09 Aug, 2011 06:47 AM

    stuartchaney22's Avatar

    Hi Messay, apologies for the delay in responding.

    We have tested your api key and successfully posted a test exception to your app. For a situation such as this we believe that it is an issue between your application and our servers. This could possibly be a firewall restricting access to our api. Could you possibly try to post a test exception from another machine or connection?

    Thanks, Stuart

  9. Support Staff 7 Posted by Ben on 10 Aug, 2011 11:34 AM

    Ben's Avatar

    HI Messay,

    I have another solution. Can you please try running this curl command from your application's server, and let us know the results? This is just a check to be sure that you can reach Exceptional's API from your network: "curl http://api.getexceptional.com/my_ip"

  10. 8 Posted by Robert on 15 Feb, 2013 10:10 PM

    Robert's Avatar

    Hi, this is Robert with support, I am clearing out old tickets. If you are still having issues with this, send an email to [email blocked].

    Thanks,
    Robert

  11. Robert closed this discussion on 15 Feb, 2013 10:10 PM.

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

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac