Closed graemian closed 10 years ago
Re-deploying doesn't fix it either - I now permanently get "Error R10 (Boot timeout)".
However, if I create a new app, it works. I'm waiting for that app to fall asleep now, that will probably kill it too
Hi there i've got the same problem, @graemian did you found a fix yet?
No, I gave up. I ended up using Meteor bundle and hosting my own NodeJS and Mongo on Digital Ocean.
On 19 November 2013 16:00, Auke van Scheltinga notifications@github.comwrote:
Hi there i've got the same problem, @graemianhttps://github.com/graemiandid you found a fix yet?
— Reply to this email directly or view it on GitHubhttps://github.com/oortcloud/heroku-buildpack-meteorite/issues/24#issuecomment-28791632 .
Graeme Pyle
+27 (83) 415-1642 +1 (650) 427-9429 facebook http://www.facebook.com/graemeapyle . linked-inhttp://www.linkedin.com/in/graemepyle
Boot timeout happens when an app fails to bind to PORT
within 60 seconds.
I don't think this is an issue with the buildpack
Hi,
My app works after deploy, but won't wake up again after it idles then goes to sleep.
Any ideas? See "heroku log" below.
Thanks, G
2013-10-10T08:49:17.079953+00:00 heroku[router]: at=info method=POST path=/sockjs/462/z802ar88/xhr host=tp.taskputty.com fwd="192.168.1.147, 105.236.179.33" dyno=web.1 connect=1ms service=2 5003ms status=200 bytes=12 2013-10-10T09:51:59.133633+00:00 heroku[web.1]: Idling 2013-10-10T09:52:02.223979+00:00 heroku[web.1]: Stopping all processes with SIGTERM 2013-10-10T09:52:04.443785+00:00 heroku[web.1]: State changed from up to down 2013-10-10T09:52:04.431350+00:00 heroku[web.1]: Process exited with status 1 2013-10-10T17:43:23.964142+00:00 heroku[web.1]: Unidling 2013-10-10T17:43:23.964452+00:00 heroku[web.1]: State changed from down to starting 2013-10-10T17:43:29.773801+00:00 heroku[web.1]: Starting process with command
.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js
2013-10-10T17:44:30.740905+00:00 heroku[web.1]: Stopping process with SIGKILL 2013-10-10T17:44:30.740703+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 2013-10-10T17:44:31.879252+00:00 heroku[web.1]: Process exited with status 137 2013-10-10T17:44:36.934189+00:00 heroku[web.1]: Starting process with command.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js
2013-10-10T17:44:39.269253+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path=/ host=tp.taskputty.com fwd="41.150.166.98" dyno= connect= service= status=503 bytes= 2013-10-10T17:45:38.648018+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 2013-10-10T17:45:38.648147+00:00 heroku[web.1]: Stopping process with SIGKILL 2013-10-10T17:45:39.716529+00:00 heroku[web.1]: Process exited with status 137 2013-10-10T17:45:40.446201+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=tp.taskputty.com fwd="41.150.166.98" dyno= connect= service= status=503 bytes= 2013-