Airbrake down / server issues?
Are folks having some server issues, we get this on our production server:
$ RAILS_ENV=production rake airbrake:test
Configuration:
api_key: "…snip…"
backtrace_filters: [#<Proc:0x000000031b16f8@/srv/my_application/shared/bundle/ruby/
development_environments: []
development_lookup: true
environment_name: "production"
host: "airbrake.io"
http_open_timeout: 2
http_read_timeout: 5
ignore: ["ActiveRecord::RecordNotFound", "ActionController::Rou
ignore_by_filters: []
ignore_user_agent: []
notifier_name: "Airbrake Notifier"
notifier_url: "http://airbrake.io"
notifier_version: "3.0.9"
params_filters: ["password", "password_confirmation"]
project_root: #<Pathname:/srv/my_application/releases/20120618113603>
port: 80
protocol: "http"
proxy_host: nil
proxy_pass: nil
proxy_port: nil
proxy_user: nil
secure: false
use_system_ssl_cert_chain: false
framework: "Rails: 3.2.6"
user_information: "Airbrake Error {{error_id}}"
rescue_rake_exceptions: nil
Setting up the Controller.
Processing request.
Started GET "/verify" for at 2012-06-18 16:25:57 +0300
Raising 'AirbrakeTestingException' to simulate application failure.
** [Airbrake] Failure: Net::HTTPServiceUnavailable
** [Airbrake] Environment Info: [Ruby: 1.9.3] [Rails: 3.2.6] [Env: production]
** [Airbrake] Response from Airbrake:
<html><body><h1>503 Service Unavailable</h1>
No server is available to handle this request.
</body></html>
AirbrakeTestingException (Testing airbrake via "rake airbrake:test". If you can see this, it works.):
app/middlewares/flash_session_cookie_middleware.rb:16:in `call'
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Morgan on 18 Jun, 2012 04:59 PM
Hello,
Thank you for raising this issue to our attention. I noticed in your
rake airbrake:testoutput you are using an outdated AirBrake Ruby Gem. Please upgrade to3.1.1, This may solve the issue for you! Please let me know once you have upgraded your gem if you still have this problem.From,
Morgan
3 Posted by Ryan on 18 Feb, 2013 06:28 PM
Hello, we are currently revisiting tickets that seem that have been resolved. If you have any further questions let us know. Send an Email to
[email blocked].
Thanks,
Ryan
Ryan closed this discussion on 18 Feb, 2013 06:28 PM.