-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Labels
Description
I tried to deploy a scaffolded app (with 2.1.0) to Heroku, but I am getting boot timeout errors. The old release (2.0.13) doesn't have this issue, so I'd guess that some configuration change in the new release is causing it.
To reproduce this, I ran the following commands (and selected default options):
mkdir test-app && cd test-app
yo angular-fullstack
bower install && npm install
git init && git add -A && git commit -m 'Initialize repository'
yo angular-fullstack:heroku
cd dist && heroku config:set NODE_ENV=production && heroku addons:create mongolab && heroku ps:scale web=1
grunt --force && grunt buildcontrol:herokuThe Heroku logs are as follows, starting with the mongolab attachment:
heroku[api]: Attach MONGOLAB resource by <email>
heroku[api]: Release v5 created by <email>
heroku[web.1]: State changed from crashed to starting
heroku[web.1]: Starting process with command `node server/app.js`
app[web.1]: Recommending WEB_CONCURRENCY=1
app[web.1]: Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
app[web.1]: Express server listening on 46443, in production mode
heroku[api]: Scale to web=1 by <email>
heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
heroku[web.1]: Stopping process with SIGKILL
heroku[web.1]: Process exited with status 137
heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=secret-hamlet-5547.herokuapp.com request_id=c38e6147-8ec5-4774-8b5a-9e17b69a82ab fwd="69.70.177.123" dyno= connect= service= status=503 bytes=
heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=secret-hamlet-5547.herokuapp.com request_id=9fb59a80-b45a-4dbe-9857-0458ba04dc84 fwd="69.70.177.123" dyno= connect= service= status=503 bytes=
Grunt can serve the app locally with no problems.
Let me know if any other information would be useful (or if this is a user error)!