So I noticed the README on rack-timeout was telling you to install the system_timer and not SystemTimer. (lovely difference, ain't it?)
I updated the README. You should ensure your app is using the correct, newer SystemTimer gem. https://github.com/kch/rack-timeout/commit/cabe05b5e42fbbe8e319abc20fb450ff597d0289 On Dec 1, 1:37 am, mattsly <matt...@gmail.com> wrote: > Yeah unfortunately I missed the log entries where the crash first > occurred, and I didn't have a tail -f going (dumb) so I don't know the > request that caused it. And nothing was logged to exceptional so I > don't have a stacktrace - maybe the Heroku guys can dig one up? (I > also have a thread open w/ support about the issue) > > In terms of being unrecoverable, once the original crash happened, > every subsequent resulted in an "App Crashed" response from the dyno - > here's a sample from the logs (just after the first crash event - > really just missed by seconds, sadly...) > > 2010-11-29T20:14:15-08:00 heroku[nginx]: GET /letters/recently_written? > offset=48 HTTP/1.1 | [ip address] | 3310 | http | 500 > 2010-11-29T20:14:20-08:00 heroku[router]: Error H10 (App crashed) -> > GETwww.futureme.org/letters/recently_writtendyno=none queue=0 > wait=0ms service=0ms bytes=0 > 2010-11-29T20:14:20-08:00 heroku[nginx]: GET /letters/recently_written? > offset=48 HTTP/1.1 | [ip address] | 3310 | http | 500 > 2010-11-29T20:14:25-08:00 heroku[router]: Error H10 (App crashed) -> > GETwww.futureme.org/letter/218665-no-subjectdyno=none queue=0 > wait=0ms service=0ms bytes=0 > 2010-11-29T20:14:31-08:00 heroku[router]: Error H10 (App crashed) -> > GETwww.futureme.org/letter/218665-no-subjectdyno=none queue=0 > wait=0ms service=0ms bytes=0 > 2010-11-29T20:14:31-08:00 heroku[router]: Error H10 (App crashed) -> > GETwww.futureme.org/dyno=none queue=0 wait=0ms service=0ms bytes=0 > 2010-11-29T20:14:31-08:00 heroku[nginx]: GET / HTTP/1.1 | [ip address] > | 3310 | http | 500 > 2010-11-29T20:14:36-08:00 heroku[router]: Error H10 (App crashed) -> > GET futureme.org/ dyno=none queue=0 wait=0ms service=0ms bytes=0 > 2010-11-29T20:14:36-08:00 heroku[nginx]: GET / HTTP/1.1 | [ip address] > | 3310 | http | 500 > 2010-11-29T20:14:37-08:00 heroku[nginx]: GET /letters/our_favs? > offset=483 HTTP/1.1 | [ip address] | 6194 | http | 200 > 2010-11-29T20:14:37-08:00 heroku[router]: Error H10 (App crashed) -> > GETwww.futureme.org/dyno=none queue=0 wait=0ms service=0ms bytes=0 > > I got back on track by commenting out the two gems (system-timer and > rack-timeout) and then redeploying. But until I did that, every > request was hitting the "Application crashed" page. > > Feel free to ping me offline to discuss more. I tried to repro in my > staging environment for a while last night but couldn't but can keep > giving it a shot. > > Matt > > On Nov 30, 1:07 pm, Caio Chassot <caio.chas...@gmail.com> wrote: > > > > > > > > > On Nov 30, 2:55 am, mattsly <matt...@gmail.com> wrote: > > > > So I've been trying to get rack-timeout installed, but it's causing > > > consistent, though non-deterministic, application crashes from which > > > my app won't recover. I've had to rollback. > > > Can you tell me more about the nature of these crashes? > > > What do you see, what do you mean by won't recover? > > > How were you getting your app back on track? By restarting it? > > > Mostly, I'd love to see a stack trace if that's possible. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@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.
