Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not reporting Mysql2::Error (Can't connect....) #138

Open
twigbranch opened this issue Apr 1, 2013 · 4 comments
Open

Not reporting Mysql2::Error (Can't connect....) #138

twigbranch opened this issue Apr 1, 2013 · 4 comments
Labels
bug existing issue

Comments

@twigbranch
Copy link

Exception Notification does not seem to be catching the following error when the database is down:
Mysql2::Error (Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)):

Is this possible to configure?

@twigbranch
Copy link
Author

NOTE: this is with version 2.6.1 on Rails 3. Installation code is in config/initializers/.

@jweslley
Copy link
Collaborator

if the error occurs during the application boot, exception_notification can not be able to send notifications because it relies on rack middleware to catch errors.

@san650
Copy link

san650 commented Dec 14, 2015

Hi!

I'm doing some bug triage and I would like to know if this bug is still happening on master.

The idea is to close those errors that can't be reproduced or that don't have enough information to reproduce it. I'll revisit this bug in a week and I'll close it if there's no more information. It can be opened again later if necessary.

Thanks!

@twigbranch
Copy link
Author

It can be reproduced. Just turn off the db.

@san650 san650 added the bug existing issue label Dec 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug existing issue
Projects
None yet
Development

No branches or pull requests

3 participants