Understanding Heroku server status 143

heroku deployment server-side
Tien Nguyen picture Tien Nguyen · Apr 2, 2013 · Viewed 51.5k times · Source

I'm wondering about Heroku server status and can't find any documentation about this topic.

Example: 

Process exited with status 143

Can anyone explain this example? And where would I find resources for future reference?

Answer

Eric Fode picture Eric Fode · Apr 2, 2013

Exit code 143 means that your process was terminated by a SIGTERM. This is generally sent when you do any commands that require your dynos to restart (config:set, restart, scale down...).

Related questions

Permission denied (publickey) when deploying heroku code. fatal: The remote end hung up unexpectedly

I'm attempting to deploy my code to heroku with the following command line: git push heroku master but get the following error: Permission denied (publickey). fatal: The remote end hung up unexpectedly I have already uploaded my public SSH key, …

Read More
Heroku deployment error H10 (App crashed)

I have a RoR app working on my local computer, but when I send it to heroku, it crashes. The error log gives an error H10 & says: 2012-11-21T15:26:47+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/newrelic_…

Read More
Collectstatic error while deploying Django app to Heroku

I'm trying to deploy a Django app to Heroku, it starts to build, download and installs everything, but that's what I get when it comes to collecting static files $ python manage.py collectstatic --noinput remote: Traceback (most recent call last): …

Read More