Here's a bit more context on that log: 2012-07-13T01:08:43+00:00 heroku[router]: GET docs.webcubecms.com/ dyno=web.1 queue=0 wait=0ms service=17ms status=200 bytes=179302 2012-07-13T01:24:58+00:00 heroku[router]: GET docs.webcubecms.com/robots.txt dyno=web.1 queue=0 wait=0ms se rvice=5ms status=404 bytes=238 2012-07-13T01:24:58+00:00 app[web.1]: 10.5.22.206 - - [13/Jul/2012 01:24:58] "GET /robots.txt HTTP/1.1" 404 - 2012-07-13T02:29:35+00:00 heroku[web.1]: Idling 2012-07-13T02:29:37+00:00 heroku[web.1]: Stopping all processes with SIGTERM 2012-07-13T02:29:37+00:00 app[web.1]: Terminated 2012-07-13T02:29:38+00:00 heroku[web.1]: Process exited with status 143 2012-07-13T02:29:38+00:00 heroku[web.1]: State changed from up to down 2012-07-13T02:58:17+00:00 heroku[web.1]: Unidling 2012-07-13T02:58:17+00:00 heroku[web.1]: State changed from down to starting 2012-07-13T02:58:19+00:00 heroku[web.1]: Starting process with command `cd .heroku/app && python app.py` 2012-07-13T02:58:20+00:00 app[web.1]: Error: No such file or directory 2012-07-13T02:58:21+00:00 heroku[web.1]: Process exited with status 126 2012-07-13T02:58:21+00:00 heroku[web.1]: State changed from starting to crashed 2012-07-13T02:58:21+00:00 heroku[web.1]: State changed from crashed to starting 2012-07-13T02:58:23+00:00 heroku[web.1]: Starting process with command `cd .heroku/app && python app.py`
On Saturday, July 14, 2012 5:37:49 PM UTC-5, Kevin Mooney wrote: > > Hi Everyone, > > So I have this application that is running a custom buildpack that > creates a simple flask server and runs. Everything had been working > perfectly for months, until Friday, when the app idled, then when it came > back from idling, it died with the following error: > > 2012-07-13T02:58:19+00:00 heroku[web.1]: Starting process with command `cd > .heroku/app && python app.py` > 2012-07-13T02:58:20+00:00 app[web.1]: Error: No such file or directory > > I haven't touched the buildpack or even the source since I started running > the app, and no one had changed the code or the build pack around the time > that it broke. Are there any known platform changes (live in the last few > days) that would cause this to occur? > > Thanks, > Kevin > -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
