Hi joshmckin, thank you very much for the support. I have tried to replicate the problem locally but I have found no error yet. I'm thinking a way to save the log realtime so I can parse it searching for the problem; the "advance" logging addon is out of my budget.
On 20 Lug, 15:58, joshmckin <joshmc...@gmail.com> wrote: > 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. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
