Heroku deployment error H10 (App crashed)

Question

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_rpm-3.4.2/lib/new_relic/control/instance_methods.rb:95:in `start_agent'
    2012-11-21T15:26:48+00:00 heroku[web.1]: State changed from starting to crashed
    2012-11-21T15:26:48+00:00 heroku[web.1]: Process exited with status 1
    2012-11-21T15:26:59+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:27:00+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:30:08+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:30:08+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:30:59+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:31:19+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:31:19+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:32:08+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=
    2012-11-21T15:32:08+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=xxx.herokuapp.com fwd= dyno= queue= wait= connect= service= status=503 bytes=

Edit:

2012-11-22T10:00:58+00:00 app[web.1]: 
2012-11-22T10:00:59+00:00 heroku[router]: at=info method=GET path=/favicon.ico host=xxx.herokuapp.com fwd= dyno=web.1 queue=0 wait=0ms connect=1ms service=26ms status=200 bytes=0

Has anyone had this before, and know what might be causing the problem? I cannot find a solution.

Thanks.

Answer 1

I ran into the same error above, app was crashing on heroku (running fine in dev) but error logs on heroku were not revealing any clues. I read other answers on this page and broke out in a sweat after seeing "rebuilding the app." I figured maybe I could get in the heroku console and look around. I did and even the console crashed, but this time it told me why. It was some obscure variable I forgot to delete during a troubleshooting session hours earlier. I am not saying you will run into the same problem, but I found more info when I tried to go through the console.

$ heroku run rails console

Answer 2

I was having the same issue. Logs weren't giving me any clues either. So I scaled down and scaled back up the dynos. This solved the problem for me:

heroku ps:scale web=0

Waited a few seconds...

heroku ps:scale web=1

Answer 3

$heroku run rails console 

This is the best option since it will give you an error in your terminal which will be much more detailed than the 'app crashed' error in your Heroku logs.

Answer 4

$ heroku restart

helped me get my dyno running again. I'm new to Heroku but glad I know now.

Answer 5

this happened to me when I was listening on the wrong port

I changed my listen() to "process.env.PORT" so:

http.listen((process.env.PORT || 5000), function(){
  console.log('listening on *:5000');
});

instead of

http.listen(5000, function(){
  console.log('listening on *:5000');
});

Answer 6

Had same problem this evening. Not a very helpful error so I tried running in the console

heroku run rails c

it failed and gave me a much more helpful error. I had neglected to delete a method call in production. Once I fixed that, the app worked fine.

Answer 7

I solved this problem by pushing to Git:

git add .
git commit -am "some text"
git push

then push to Heroku:

git push heroku

then rake db:migrate on Heroku:

heroku run rake db:migrate

Answer 8

If you're using Node, you can try running the serve command directly in the console. In my case I'm running an angular application, so I tried with:

heroku run npm start

This showed me the exact error during the application startup.

Answer 9

I managed to not include my .gitignore file -> that breaks heroku. #doh

Here is a working .gitignore file

/.bundle
/vendor/bundle/
/vendor/ruby/


db/*.sqlite3
/db/*.sqlite3-journal
/log/*
/tmp/*


**.war
*.rbc
*.sassc
.redcar/
.sass-cache
/config/config.yml
/config/database.yml
/coverage.data
/coverage/
/db/*.javadb/
/db/*.sqlite3
/doc/api/
/doc/app/
/doc/features.html
/doc/specs.html
/public/cache
/public/stylesheets/compiled
/public/system/*
/spec/tmp/*
/cache
/capybara*
/capybara-*.html
/gems
/specifications
rerun.txt
pickle-email-*.html
.zeus.sock

**.orig

.DS_Store

/nbproject/

.idea

/*.tmproj

**.swp

.env
.powenv

To create a .gitignore file, in terminal navigate to your apps directory and use the following command

touch .gitignore

Then you can open it up in a your text editor and put the above code into it.

Answer 10

In my case i was using ENV variables in my app, but it was not set in heroku config.

heroku console gave proper error:

heroku console
`validate_options': Missing required arguments: aws_access_key_id, aws_secret_access_key (ArgumentError)

Then set the ENV config

heroku config:set AWS_ACCESS_KEY_ID='key'

Restart the Heroku

heroku restart

it works!!

Answer 11

I was getting this same H10 app crashed error in Heroku. I clicked 'restart all dynos' in the heroku interface, and problem solved.

Answer 12

I had H10 with Heroku and Node due to wrong name of the main code file. Edit package.json:

{

  ...

  "main": "correct_file_name.js",

  ...

  "scripts": {
    "start": "node correct_file_name.js"
  }
}

Or rename the file.

Answer 13

In my case the Procfile I used was breaking everything. Heroku looks for Procfile and applies its settings when launching the app - clearly the dev settings I used didn't make any sense for the prod server. I had to rename it to Procfile.dev and everything started working normally.

Answer 14

Solution Worked for me, Try running the command: :

Heroku restart

Answer 15

The root of the problem I was facing was due to not having a database. To resolve the problem I first exported my local database:

$ heroku addons:add heroku-postgresql:dev 
$ heroku addons:add pgbackups
$ PGPASSWORD=mypassword pg_dump -Fc --no-acl --no-owner -h localhost -U myuser mydb > mydb.dump 

Then imported it into Heroku:

$ heroku pgbackups:restore DATABASE 'http://site.tld/mydb.dump'

The variables to replace in these examples are: mypassword, myuser, mydb & http://site.tld/mydb.dump. Note that I had to upload the dump to a temporary server.

Resolving all my problems I wrote up a quick guide on how to deploy Enki to Heroku, which can be found here.

Answer 16

See if you get

bash: bin/rails: No such file or directory

in logs while running (heroku logs -t) command if yes then please Run

bundle exec rake rails:update

Don't overwrite your files, in the end this command will create

  create  bin
  create  bin/bundle
  create  bin/rails
  create  bin/rake

push these files to heroku and you are done.

Answer 17

I got the same above error as "app crashed" and the heroku app logs is not showing much info related to the error msg reasons. Then I restarted the dynos in heroku and then it showed the error saying additional curly brace in one of the index.js files in my setup. The issue got fixed once it is removed and redeployed the app on heroku.

Hope this will be helpful to someone facing the same issue.

Answer 18

After going through the entire list of answers I stumbled upon this website: https://status.heroku.com/ which details the current status/incidents with Heroku. Its always safe to check out for incidents before banging your head against the wall. For me, it was the attached incident report published on the above mentioned link that was causing the error.

Answer 19

I had the same problem, I did the following

heroku run rails c

It identified a syntax error and missing comma within a controller permitted params. As mentioned above the Heroku logs did not provide sufficient information to problem solve the problem.

I have not seen the application crashed message on Heroku previously.

Answer 20

I traced my problem back to the Puma server as did @Ahmed Elkoussy, but I solved just by commenting the following line on the puma.rb file:

# pidfile ENV.fetch("PIDFILE") { "tmp/pids/server.pid" }

Answer 21

I encountered the same problem today. I did heroku run rake db:migrate though I migrated the model before, and the app doesn't crash.

Answer 22

Be very cautious of copy and pasting code. Sometimes when you add a block into a file, it is formatted incorrectly and will yield an error.

I've had this problem before and got this error: unexpected tIDENTIFIER, expecting keyword_end

Answer 23

Had same problem. for me it was error in before_action filters(because empty DB) Check your before_action filters, maybe they throw unhendled exeptions.

Answer 24

I had this problem when trying to run Rails in a subdirectory, and not in /. For example, I had Angular/Node/Gulp app running in /client and a Rails app running in /server, but both of them were in the same git repo, so I could track changes across the front end and back end. I got this error when trying to deploy them to Heroku. For anyone else having this issue, here is a custom buildpack that will allow running Rails in a subdirectory.

https://github.com/aarongray/heroku-buildpack-ruby

Answer 25

I had the same issue (same error on heroku, working on local machine) and I tried all the solutions listed here including heroku run rails console which ran without error messages. I tried heroku run rake db:migrate and heroku run rake db:migrate:reset a few times. None of this solved the problem. On going through some files that are used in production but not in dev environment, I found some whitespace in the puma.rb file to be the culprit. Hope this helps someone who has the same issue. Changing this made it work

  ActiveRecord::Base.establish_connection
  End

to

  ActiveRecord::Base.establish_connection
end

Answer 26

I ran into the same issue while deploying to Heroku (app crash). Logs did not indicate what the problem could be. Heroku console displayed syntax error in the code of an extra bracket. Surprisingly, I did not have an issue on local rails while running the app and hence missed it. After correction and git push to Heroku, the app started working on Heroku!

Answer 27

I updated my settings from app.set('ip_address', process.env.IP || '127.0.0.1');

to

app.set('ip_address', process.env.IP || '0.0.0.0');

which i changed for Openshift hosting

Answer 28

I had the same issue when I started using Puma in heroku as per their guide page, this issue was solved when I commented the port line shown below

# port        ENV['PORT']     || 3000

So, disabling the above line in the puma.rb in the config directory solved the issue

workers Integer(ENV['WEB_CONCURRENCY'] || 2)
threads_count = Integer(ENV['RAILS_MAX_THREADS'] || 5)
threads threads_count, threads_count

preload_app!

rackup      DefaultRackup
# port        ENV['PORT']     || 3000
environment ENV['RACK_ENV'] || 'production'

on_worker_boot do
  # Worker specific setup for Rails 4.1+
  # See: https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#on-worker-boot
  ActiveRecord::Base.establish_connection
end

Answer 29

In my case I was performing git push heroku master when I am not on the master branch. I had to go to master branch first, merge the code with my other branch and then git pushed.

Answer 30

I also encountered the same error. Adding a .gitignore file to my project resolved my issue.

My .gitignore file is here:

# Node build artifacts
node_modules
npm-debug.log

# Local development
*.env
*.dev
.DS_Store

# Docker
Dockerfile
docker-compose.yml

And I changed listen() function;

app.listen(5000, function() {
console.log("Server running on port 5000...");
});

I changed it to;

    const PORT = process.env.PORT || 5000

...

    app.listen(PORT, function() {
    console.log("Server running on port 5000...");
    });

Answer 31

The solution I posted on Dev and worked for most people using React:

https://medium.com/@uros.randelovic/causes-of-heroku-h10-app-crashed-error-and-how-to-solve-them-70495914d2a3?sk=1c51cf95e904f754a43a4b63a06b5503

npm install serve --s
"scripts": {
"dev": "react-scripts start",
"start": "serve -s build",
"build": "react-scripts build",
"test": "react-scripts test --env=jsdom",
"eject": "react-scripts eject",
"heroku-postbuild": "npm run build"
}

Answer 32

I had same issue in my server-side application. by default browser requests server for favicon.ico. So I used serve-favicon package. this is the set up:

import favicon from "serve-favicon";
server.use(favicon(path.join(__dirname, "../assets/images/favicon.ico")));

Answer 33

My 50 cents, I had this problem too and solved by:

• inspect logs via UI from very begining of building process (eg. after commit, restart dynos) to see what happens before crash

• when link modules do not include root directory of project (my problem..)

this:

const router = require('./logic/router.js') 

instead of:

const router = require('../DMS/logic/router.js') 

Answer 34

I know this question is very old. I add new answer just in case there is someone who has the same issue on Rails 3.

In my case, app started to crash on Heroku once "thin" gem was commented by accident on Gemfile.

It worked again I added back that gem.

Answer 35

In node.js a have the same problem

fix: remove PORT from .env file on project

// app.ts or app.js

const PORT = process.env.PORT || '5000';

// .env

PORT=5000 <--- comment or remove this line

Answer 36

I experienced this issue after upgrading from rails 6 to rails 7. It was because rails 7 uses the default image processor :vips, but I had not prepared my app to use vips, so there were problems.

Since I wanted to continue to use :mini_magick like I was in rails 6, I simply had to add this line to config/application.rb and all was well:

config.active_storage.variant_processor = :mini_magick

I got that information here

---

Now, how did I figure this out? Thankfully I could see the last heroku logs to figure out what a user had just done on the production application, I ran the app locally, and did the same thing locally and the server crashed, and I saw a problem involving vips in the server logs.

Answer 37

In my case, my app crashed because I was hard setting the PORT, instead of using the port that Heroku dynamically sets, which can be accessed with process.env.PORT

I was using this code

app.listen(PORT, () => {
  console.log("App started at port " + PORT);
});

so then I try this

app.listen(process.env.PORT || 3000, function(){
   console.log("Express server listening on port %d in %s mode", 
 this.address().port, app.settings.env);
});