A web process took longer than 60 seconds to bind to its assigned $PORT. This error is often caused by a process being unable to reach an external resource, such as a database.
2011-05-03T17:31:38+00:00 heroku[web.1]: State changed from created to starting
2011-05-03T17:31:40+00:00 heroku[web.1]: Starting process with command: thin -p 22020 -e production -R /home/heroku_rack/heroku.ru start
2011-05-03T17:32:40+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2011-05-03T17:32:40+00:00 heroku[web.1]: Stopping process with SIGKILL
2011-05-03T17:32:40+00:00 heroku[web.1]: Process exited
2011-05-03T17:32:41+00:00 heroku[web.1]: State changed from starting to crashed
Filirom1
commented
11 years ago
R10 - Boot timeout
A web process took longer than 60 seconds to bind to its assigned $PORT. This error is often caused by a process being unable to reach an external resource, such as a database.
2011-05-03T17:31:38+00:00 heroku[web.1]: State changed from created to starting 2011-05-03T17:31:40+00:00 heroku[web.1]: Starting process with command:
thin -p 22020 -e production -R /home/heroku_rack/heroku.ru start2011-05-03T17:32:40+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 2011-05-03T17:32:40+00:00 heroku[web.1]: Stopping process with SIGKILL 2011-05-03T17:32:40+00:00 heroku[web.1]: Process exited 2011-05-03T17:32:41+00:00 heroku[web.1]: State changed from starting to crashedhttps://devcenter.heroku.com/articles/error-codes