getsentry/freight

Heroku template does not launch

akatz opened this issue · 9 comments

akatz commented

It fails every time with this output:

Detected 512 MB available memory, 512 MB limit per process (WEB_MEMORY)
Recommending WEB_CONCURRENCY=1
+ alembic upgrade head
dcramer commented

That's the only output? Seems like it's failing on upgrading the database.

akatz commented

Yes, it fails in the post deploy script with only that. The build step completes successfully. Interesting because the heroku postgres connector should take care of wiring up the db correctly.

akatz commented

If you need anything further from me I'd be happy to help.

akatz commented

As an aside I have been able to get it up and running manually on heroku, but I wasn't able to do it using the template, I had to configure it all myself.

rshk commented

@akatz was this related to #36? I remember getting a somehow-confusing error message in the log, along with an heroku message along the lines of «stop using the old dyno names, use the new one», which was the actual issue..

Draiken commented

Just launched the heroku template and can't seem to access the app.

http post http://appname.herokuapp.com/api/0/apps/ "Authorization: Key KEY" repository=git@github.com:owner/repo.git name=Lala provider=shell provider_config='{"command": "bin/deploy"}'

Throws out "no such app" errors.
Logs are useless, even tried to add the debug flag but nothing shows up.

2017-02-16T00:04:20.002399+00:00 heroku[web.1]: Starting process with command `bin/upgrade && PYTHONUNBUFFERED=1 bin/web --debug --addr=:${PORT}`
2017-02-16T00:04:22.705773+00:00 app[web.1]: + alembic upgrade head
2017-02-16T00:04:25.006213+00:00 app[web.1]: Raven is not configured (logging is disabled). Please see the documentation for more information.
2017-02-16T00:04:25.006236+00:00 app[web.1]: INFO  [raven.base.Client] Raven is not configured (logging is disabled). Please see the documentation for more information.
2017-02-16T00:04:26.339941+00:00 app[web.1]: Raven is not configured (logging is disabled). Please see the documentation for more information.
2017-02-16T00:04:26.422099+00:00 app[web.1]: Listening on http://0.0.0.0:57518
2017-02-16T00:04:27.043218+00:00 heroku[web.1]: State changed from starting to up
2017-02-16T00:04:27.611673+00:00 app[web.1]: Raven is not configured (logging is disabled). Please see the documentation for more information.
2017-02-16T00:04:27.695568+00:00 app[web.1]: Listening on http://0.0.0.0:57518
dcramer commented

Its throwing an API response that says no such app? otherwise i have no clue

Draiken commented

After about 30 minutes it suddenly started working.

I suspect it was heroku's fault. Sorry for the trouble.

akatz commented

I no longer maintain an active freight install so it might be best to close this out unless someone else reports it as well.