I've had a similar issue, since the application is crashing any system built into the application for logging is crashing with it. New relic can sometimes catch it but not always. Your best bet is build an environment locally similar to Heroku (Nginx/Thin) and see if you can replicate the error. For us it turned out Mysql2 gem was throwing exceptions that would kill EventMachine and therefore kill Thin. Since Thin was giving up its ghost, the logger would not record the exception, once we were able to patch Mysql2 we were able to get to the root exception.
On Jul 20, 8:07 am, Daniele <[email protected]> wrote: > Hi, > some users are informing me that my application sometimes pop up an > Application Error: > > ------ > Application Error > An error occurred in the application and your page could not be > served. Please try again in a few moments. > If you are the application owner, check your logs for details. > ------ > > I'm using Exception Notifier to log rails errors but it cannot log > these errors because they are at heroku level. > I'm unable to check the log because time has passed and it is not > longer available. > > What can I do to log, be notified *instantly* and debug these errors? > > Thanks! -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
