At error code h10 desc app crashed method get path favicon ico - Исправление ошибок и поиск оптимальных решений проблем

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.

asked Nov 21, 2012 at 15:45

bskoolbskool

2,0582 gold badges19 silver badges24 bronze badges

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

user

4,8165 gold badges17 silver badges35 bronze badges

answered Jun 9, 2014 at 3:23

ntimba20ntimba20

3,6861 gold badge11 silver badges4 bronze badges

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

answered Jan 12, 2016 at 16:43

HunterHunter

1,66716 silver badges24 bronze badges

$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.

Igor

32.7k14 gold badges79 silver badges112 bronze badges

answered Jun 30, 2014 at 20:26

EricSchulzEricSchulz

2612 silver badges6 bronze badges

$ heroku restart

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

answered Feb 21, 2016 at 22:20

Kyle KwonKyle Kwon

3512 silver badges5 bronze badges

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');
});

answered Jul 6, 2015 at 21:49

newshortsnewshorts

1,04812 silver badges12 bronze badges

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.

answered Apr 14, 2016 at 3:04

GregoryGregory

1091 silver badge3 bronze badges

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

answered Mar 17, 2013 at 7:59

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.

answered Feb 20, 2019 at 15:49

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.

answered Sep 17, 2014 at 17:26

Joe MellinJoe Mellin

7218 silver badges15 bronze badges

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!!

answered Jun 20, 2017 at 19:24

devudilipdevudilip

1,27014 silver badges25 bronze badges

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

answered Feb 4, 2016 at 19:30

tombtomb

1,34613 silver badges23 bronze badges

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.

answered Nov 28, 2017 at 3:11

arielariel

15.1k11 gold badges60 silver badges72 bronze badges

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.

answered Jun 22, 2018 at 15:33

The Whiz of OzThe Whiz of Oz

6,6639 gold badges47 silver badges84 bronze badges

Solution Worked for me, Try running the command: :

Heroku restart

answered Sep 10, 2020 at 9:00

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.

answered Jun 10, 2015 at 8:41

Saqib R.Saqib R.

2,8492 gold badges26 silver badges21 bronze badges

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.

answered Dec 11, 2012 at 10:21

bskoolbskool

2,0582 gold badges19 silver badges24 bronze badges

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.

answered Sep 6, 2017 at 4:48

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.

answered Jan 4, 2018 at 20:31

PallavBakshiPallavBakshi

5242 gold badges12 silver badges21 bronze badges

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.

answered Oct 6, 2018 at 11:36

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" }

answered Dec 12, 2019 at 6:01

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.

answered Dec 11, 2012 at 5:20

Tu H.Tu H.

4966 silver badges12 bronze badges

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

answered Oct 2, 2014 at 2:07

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.

answered Jun 30, 2015 at 10:05

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

answered Jul 13, 2015 at 22:20

Aaron GrayAaron Gray

11k6 gold badges53 silver badges59 bronze badges

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

  ActiveRecord::Base.establish_connection
end

answered Dec 12, 2015 at 15:59

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!

smottt

3,27211 gold badges39 silver badges44 bronze badges

answered Nov 17, 2016 at 22:17

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

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

which i changed for Openshift hosting

answered Jun 12, 2017 at 16:06

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

answered Feb 11, 2019 at 20:39

Ahmed ElkoussyAhmed Elkoussy

7,7789 gold badges57 silver badges83 bronze badges

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.

answered Oct 24, 2019 at 16:22

GilbertSGilbertS

5638 silver badges11 bronze badges

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...");
    });

alyssaeliyah

2,0706 gold badges30 silver badges75 bronze badges

answered Apr 24, 2020 at 11:20

shrgrlshrgrl

873 silver badges13 bronze badges

Источник

Programming is bittersweet.
It is very tedious and many a time, it can leave developers very frustrated with little zeal for another keypress.

However, developers are always having a whale of a time while coding, and they are full of pride and joy, once all their codes run successfully without errors.

That being said no one wants to be frustrated while coding hence no one wants bugs in their codes.

Developers, often do not get it all right («code-wise«) at first try; consequently, the software development cycle involves debugging, refactoring, upgrading, and many other enhancement operations.
In addition, developers know that many a time we all have to deal with bugs in our code. Hence debugging is an invaluable skill in a developer’s repertoire. And to be successful at debugging, we need a good understanding of error messages.

Error codes or messages are the ways computers inform us that there are bugs in our codes, and sometimes it tells us where they are.

The paradox is that error codes; although are very helpful, they are not plain English and can be very confusing and cryptic

Below are error codes from a crashed app on Heroku.

2019-10-11T11:27:28.019054+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=realtylabapp.herokuapp.com request_id=74165d9f-db2a-46bd-ab9c-1a01403bd00f fwd="129.205.113.108" dyno= connect= service= status=503 bytes= protocol=https
2019-10-11T11:27:29.919409+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=realtylabapp.herokuapp.com request_id=fa48efa2-4ddf-41e6-a633-a62cb02314bd fwd="129.205.113.108" dyno= connect= service= status=503 bytes= protocol=https

Enter fullscreen mode

Exit fullscreen mode

Heroku uses a unique alphanumeric error code combo to communicate to the developer the kind of error that was found in their code.

This alphanumeric error code ranges from:

H10 to H99
R10 to R99
L10 to L15

Get a detailed list here: Complete Heroku Error Codes

This article is focused on the Heroku H10-App crashed error code which is thrown when an application crashes on Heroku. This is as much as it goes. It does not help us with the reason our app crashed and that’s where this article comes in. Below are some causes of this error and I guarantee you that some of them would surprise you greatly!

Bug in Procfile
A very interesting discovery for me. A bug in your Procfile can crash your app. If your Procfile is pointing to the wrong server file. e.g If your server is in server.js and your Procfile points to app.js this would definitely crash your app and Heroku would greet you with the H10-App crashed error code message.
Secondly, a buggy Procfile can also come in the form of wrong spacing. e.g
Wrong: web : node index.js
Correct web: node index.js
Setting a PORT as a Heroku environment variable
This would surely crash your app. Heroku automatically sets a Port that can be accessed via process.env.PORT. Setting a port yourself would crash your app. Surprisingly, the command heroku config does not display the preset Heroku port so one might be tempted to set another port as an environment variable.
To see all the preset Heroku environment variables, use the command heroku run printenv.
Missing Required Environment Variable while setting a port would cause this error because Heroku already sets a port internally, failing to set any required environment variable (e.g your database), would prompt Heroku to greet you with this error.
Missing Required Scripts
This error is thrown in a Node.js environment if you forget to set a start script. Heroku uses this script to start your app so if it is missing, it would throw an H10-App crashed error code message.

This can be solved by setting a start script in the package.json. e.g

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

Enter fullscreen mode

Exit fullscreen mode

Final Thoughts
If none of the above solved your problem, you can make a last-ditch attempt by updating all your packages. If this doesn’t help and you are in a Node.js environment, your last resort would be setting a node version in the engine section of your package.json file.

{
 "name": "myapp",
 "description": "a really cool app",
 "version": "1.0.0",
 "engines": {
   "node": "12.11.1"
   }
}

Enter fullscreen mode

Exit fullscreen mode

The Unthinkable
Lastly, if your bug defiles all solution, and by this time you are grasping at straws; I leave you in the able hands of heroku restart.

Let me know if you have experienced any other cause of this error in the comment below.

Take a look at this:

Go to your customization settings to nudge your home feed to show content more relevant to your developer experience level. 🛠

H10 — App crashed

A crashed web dyno or a boot timeout on the web dyno will present this error.

2010-10-06T21:51:04-07:00 heroku[web.1]: State changed from down to starting
2010-10-06T21:51:07-07:00 app[web.1]: Starting process with command: `bundle exec rails server -p 22020`
2010-10-06T21:51:09-07:00 app[web.1]: >> Using rails adapter
2010-10-06T21:51:09-07:00 app[web.1]: Missing the Rails 2.3.5 gem. Please `gem install -v=2.3.5 rails`, update your RAILS_GEM_VERSION setting in config/environment.rb for the Rails version you do have installed, or comment out RAILS_GEM_VERSION to use the latest version installed.
2010-10-06T21:51:10-07:00 heroku[web.1]: Process exited
2010-10-06T21:51:12-07:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H11 — Backlog too deep

When HTTP requests arrive faster than your application can process them, they can form a large backlog on a number of routers. When the backlog on a particular router passes a threshold, the router determines that your application isn’t keeping up with its incoming request volume. You’ll see an H11 error for each incoming request as long as the backlog is over this size. The exact value of this threshold may change depending on various factors, such as the number of dynos in your app, response time for individual requests, and your app’s normal request volume.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H11 desc="Backlog too deep" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

The solution is to increase your app’s throughput by adding more dynos, tuning your database (for example, adding an index), or making the code itself faster. As always, increasing performance is highly application-specific and requires profiling.

H12 — Request timeout

For more information on request timeouts (including recommendations for resolving them), take a look at our article on the topic.

An HTTP request took longer than 30 seconds to complete. In the example below, a Rails app takes 37 seconds to render the page; the HTTP router returns a 503 prior to Rails completing its request cycle, but the Rails process continues and the completion message shows after the router message.

2010-10-06T21:51:07-07:00 app[web.2]: Processing PostController#list (for 75.36.147.245 at 2010-10-06 21:51:07) [GET]
2010-10-06T21:51:08-07:00 app[web.2]: Rendering template within layouts/application
2010-10-06T21:51:19-07:00 app[web.2]: Rendering post/list
2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=6ms service=30001ms status=503 bytes=0
2010-10-06T21:51:42-07:00 app[web.2]: Completed in 37000ms (View: 27, DB: 21) | 200 OK [http://myapp.heroku.com/]

This 30-second limit is measured by the router, and includes all time spent in the dyno, including the kernel’s incoming connection queue and the app itself.

See Request Timeout for more, as well as a language-specific article on this error:

H12 — Request Timeout in Ruby (MRI)

H13 — Connection closed without response

This error is thrown when a process in your web dyno accepts a connection but then closes the socket without writing anything to it.

2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H13 desc="Connection closed without response" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=3030ms service=9767ms status=503 bytes=0

One example where this might happen is when a Unicorn web server is configured with a timeout shorter than 30s and a request has not been processed by a worker before the timeout happens. In this case, Unicorn closes the connection before any data is written, resulting in an H13.

An example of an H13 can be found here.

H14 — No web dynos running

This is most likely the result of scaling your web dynos down to 0 dynos. To fix it, scale your web dynos to 1 or more dynos:

$ heroku ps:scale web=1

Use the heroku ps command to determine the state of your web dynos.

2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H15 — Idle connection

The dyno did not send a full response and was terminated due to 55 seconds of inactivity. For example, the response indicated a Content-Length of 50 bytes which were not sent in time.

2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H15 desc="Idle connection" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=55449ms status=503 bytes=18

H16 — (No Longer in Use)

Heroku no longer emits H16 errors

H17 — Poorly formatted HTTP response

Our HTTP routing stack has no longer accepts responses that are missing a reason phrase in the status line. ‘HTTP/1.1 200 OK’ will work with the new router, but ‘HTTP/1.1 200’ will not.

This error message is logged when a router detects a malformed HTTP response coming from a dyno.

2010-10-06T21:51:37-07:00 heroku[router]: at=error code=H17 desc="Poorly formatted HTTP response" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=1ms status=503 bytes=0

H18 — Server Request Interrupted

An H18 signifies that the socket connected, and some data was sent; The error occurs in cases where the socket was destroyed before sending a complete response, or if the server responds with data before reading the entire body of the incoming request.

2010-10-06T21:51:37-07:00 heroku[router]: sock=backend at=error code=H18 desc="Server Request Interrupted" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=1ms status=503 bytes=0

An example of an H18 can be found here.

H19 — Backend connection timeout

A router received a connection timeout error after 5 seconds of attempting to open a socket to a web dyno. This is usually a symptom of your app being overwhelmed and failing to accept new connections in a timely manner. For Common Runtime apps, if you have multiple dynos, the router will retry multiple dynos before logging H19 and serving a standard error page. Private Space routers can’t reroute requests to another web dyno.

If your app has a single web dyno, it is possible to see H19 errors if the runtime instance running your web dyno fails and is replaced. Once the failure is detected and the instance is terminated your web dyno will be restarted somewhere else, but in the meantime, H19s may be served as the router fails to establish a connection to your dyno. This can be mitigated by running more than one web dyno.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H19 desc="Backend connection timeout" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=5001ms service= status=503 bytes=

H20 — App boot timeout

The router will enqueue requests for 75 seconds while waiting for starting processes to reach an “up” state. If after 75 seconds, no web dynos have reached an “up” state, the router logs H20 and serves a standard error page.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

The Ruby on Rails asset pipeline can sometimes fail to run during git push, and will instead attempt to run when your app’s dynos boot. Since the Rails asset pipeline is a slow process, this can cause H20 boot timeout errors.

This error differs from R10 in that the H20 75-second timeout includes platform tasks such as internal state propagation, requests between internal components, slug download, unpacking, container preparation, etc… The R10 60-second timeout applies solely to application startup tasks.

If your application requires more time to boot, you may use the boot timeout tool to increase the limit. However, in general, slow boot times will make it harder to deploy your application and will make recovery from dyno failures slower, so this should be considered a temporary solution.

H21 — Backend connection refused

A router received a connection refused error when attempting to open a socket to your web process. This is usually a symptom of your app being overwhelmed and failing to accept new connections.

For Common Runtime apps, the router will retry multiple dynos before logging H21 and serving a standard error page. Private Spaces apps are not capable of sending the requests to multiple dynos.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H21 desc="Backend connection refused" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service= status=503 bytes=

H22 — Connection limit reached

A routing node has detected an elevated number of HTTP client connections attempting to reach your app. Reaching this threshold most likely means your app is under heavy load and is not responding quickly enough to keep up. The exact value of this threshold may change depending on various factors, such as the number of dynos in your app, response time for individual requests, and your app’s normal request volume.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H22 desc="Connection limit reached" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H23 — Endpoint misconfigured

A routing node has detected a websocket handshake, specifically the ‘Sec-Websocket-Version’ header in the request, that came from an endpoint (upstream proxy) that does not support websockets.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H23 desc="Endpoint misconfigured" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H24 — Forced close

The routing node serving this request was either shutdown for maintenance or terminated before the request completed.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H24 desc="Forced close" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=80000ms status= bytes=18

H25 — HTTP Restriction

This error is logged when a routing node detects and blocks a valid HTTP response that is judged risky or too large to be safely parsed. The error comes in four types.

Currently, this functionality is experimental, and is only made available to a subset of applications on the platform.

Invalid content length

The response has multiple content lengths declared within the same response, with varying lengths.

2014-03-20T14:22:00.203382+00:00 heroku[router]: at=error code=H25 desc="HTTP restriction: invalid content length" method=GET path="/" host=myapp.herokuapp.com request_id=3f336f1a-9be3-4791-afe3-596a1f2a481f fwd="17.17.17.17" dyno=web.1 connect=0 service=1 status=502 bytes=537

Oversized cookies

The cookie in the response will be too large to be used again in a request to the Heroku router or SSL endpoints.

2014-03-20T14:18:57.403882+00:00 heroku[router]: at=error code=H25 desc="HTTP restriction: oversized cookie" method=GET path="/" host=myapp.herokuapp.com request_id=90cfbbd2-0397-4bab-828f-193050a076c4 fwd="17.17.17.17" dyno=web.1 connect=0 service=2 status=502 bytes=537

A single header line is deemed too long (over 512kb) and the response is discarded on purpose.

2014-03-20T14:12:28.555073+00:00 heroku[router]: at=error code=H25 desc="HTTP restriction: oversized header" method=GET path="/" host=myapp.herokuapp.com request_id=ab66646e-84eb-47b8-b3bb-2031ecc1bc2c fwd="17.17.17.17" dyno=web.1 connect=0 service=397 status=502 bytes=542

Oversized status line

The status line is judged too long (8kb) and the response is discarded on purpose.

2014-03-20T13:54:44.423083+00:00 heroku[router]: at=error code=H25 desc="HTTP restriction: oversized status line" method=GET path="/" host=myapp.herokuapp.com request_id=208588ac-1a66-44c1-b665-fe60c596241b fwd="17.17.17.17" dyno=web.1 connect=0 service=3 status=502 bytes=537

H26 — Request Error

This error is logged when a request has been identified as belonging to a specific Heroku application, but cannot be delivered entirely to a dyno due to HTTP protocol errors in the request. Multiple possible causes can be identified in the log message.

The request has an expect header, and its value is not 100-Continue, the only expect value handled by the router. A request with an unsupported expect value is terminated with the status code 417 Expectation Failed.

2014-05-14T17:17:37.456997+00:00 heroku[router]: at=error code=H26 desc="Request Error" cause="unsupported expect header value" method=GET path="/" host=myapp.herokuapp.com request_id=3f336f1a-9be3-4791-afe3-596a1f2a481f fwd="17.17.17.17" dyno= connect= service= status=417 bytes=

The request has an HTTP header with a value that is either impossible to parse, or not handled by the router, such as connection: ,.

2014-05-14T17:17:37.456997+00:00 heroku[router]: at=error code=H26 desc="Request Error" cause="bad header" method=GET path="/" host=myapp.herokuapp.com request_id=3f336f1a-9be3-4791-afe3-596a1f2a481f fwd="17.17.17.17" dyno= connect= service= status=400 bytes=

Bad chunk

The request has a chunked transfer-encoding, but with a chunk that was invalid or couldn’t be parsed correctly. A request with this status code will be interrupted during transfer to the dyno.

2014-05-14T17:17:37.456997+00:00 heroku[router]: at=error code=H26 desc="Request Error" cause="bad chunk" method=GET path="/" host=myapp.herokuapp.com request_id=3f336f1a-9be3-4791-afe3-596a1f2a481f fwd="17.17.17.17" dyno=web.1 connect=1 service=0 status=400 bytes=537

H27 — Client Request Interrupted

The client socket was closed either in the middle of the request or before a response could be returned. For example, the client closed their browser session before the request was able to complete.

2010-10-06T21:51:37-07:00 heroku[router]: sock=client at=warning code=H27 desc="Client Request Interrupted" method=POST path="/submit/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=0ms status=499 bytes=0

H28 — Client Connection Idle

The client did not send a full request and was terminated due to 55 seconds of inactivity. For example, the client indicated a Content-Length of 50 bytes which were not sent in time.

2010-10-06T21:51:37-07:00 heroku[router]: at=warning code=H28 desc="Client Connection Idle" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno=web.1 connect=1ms service=55449ms status=499 bytes=18

H31 — Misdirected Request

The client sent a request to the wrong endpoint. This could be because the client used stale DNS information or is accessing the app through a CDN that has stale DNS information. Verify that DNS is correctly configured for your app. If a CDN is configured for the app, consider contacting your CDN provider.

If you and your app users can successfully access the app in a browser (or however the app is used), this may not be cause for concern. The errors may be caused by clients (typically web-crawlers) with cached DNS entries trying to access a now-invalid endpoint or IP address for your app.

You can verify the validity of user agent through the app log error message as shown in the example below:

error code=H31 desc="Misdirected Request" method=GET path="/" host=[host.com] request_id=[guid] fwd="[IP]" dyno= connect= service= status=421 bytes= protocol=http agent="<agent>"

H80 — Maintenance mode

This is not an error, but we give it a code for the sake of completeness. Note the log formatting is the same but without the word “Error”.

2010-10-06T21:51:07-07:00 heroku[router]: at=info code=H80 desc="Maintenance mode" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H81 — Blank app

No code has been pushed to this application. To get rid of this message you need to do one deploy. This is not an error, but we give it a code for the sake of completeness.

2010-10-06T21:51:07-07:00 heroku[router]: at=info code=H81 desc="Blank app" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H82 — You’ve used up your dyno hour pool

This error indicates that an account has exhausted its monthly dyno hour quota for Free or Eco dynos and its apps running these dynos are sleeping. You can view your app’s Free or Eco dyno usage in the Heroku dashboard.

2015-10-06T21:51:07-07:00 heroku[router]: at=info code=H82 desc="You've used up your dyno hour pool" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H83 — Planned Service Degradation

This indicates that your app is temporarily unavailable as Heroku makes necessary changes to support the retirement of a feature that has reached end of life. You will likely encounter an error screen when attempting to access your application and see the error below in your logs. Please reference the Heroku Changelog and the Heroku Status page for more details and the timeline of the planned service outage.

2021-10-10T21:51:07-07:00 heroku[router]: at=info code=H83 desc="Service Degradation" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

H99 — Platform error

H99 and R99 are the only error codes that represent errors in the Heroku platform.

This indicates an internal error in the Heroku platform. Unlike all of the other errors which will require action from you to correct, this one does not require action from you. Try again in a minute, or check the status site.

2010-10-06T21:51:07-07:00 heroku[router]: at=error code=H99 desc="Platform error" method=GET path="/" host=myapp.herokuapp.com fwd=17.17.17.17 dyno= connect= service= status=503 bytes=

R10 — Boot timeout

A web process took longer than 60 seconds to bind to its assigned $PORT. When this happens, the dyno’s process is killed and the dyno is considered crashed. Crashed dynos are restarted according to the dyno manager’s restart policy.

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: `bundle exec rails server -p 22020 -e production`
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

This error is often caused by a process being unable to reach an external resource, such as a database, or the application doing too much work, such as parsing and evaluating numerous, large code dependencies, during startup.

Common solutions are to access external resources asynchronously, so they don’t block startup, and to reduce the amount of application code or its dependencies.

One exception is for apps using the Java buildpack, Gradle buildpack, heroku-deploy toolbelt plugin, or Heroku Maven plugin, which will be allowed 90 seconds to bind to their assigned port.

R12 — Exit timeout

A process failed to exit within 30 seconds of being sent a SIGTERM indicating that it should stop. The process is sent SIGKILL to force an exit.

2011-05-03T17:40:10+00:00 app[worker.1]: Working
2011-05-03T17:40:11+00:00 heroku[worker.1]: Stopping process with SIGTERM
2011-05-03T17:40:11+00:00 app[worker.1]: Ignoring SIGTERM
2011-05-03T17:40:14+00:00 app[worker.1]: Working
2011-05-03T17:40:18+00:00 app[worker.1]: Working
2011-05-03T17:40:21+00:00 heroku[worker.1]: Error R12 (Exit timeout) -> Process failed to exit within 30 seconds of SIGTERM
2011-05-03T17:40:21+00:00 heroku[worker.1]: Stopping process with SIGKILL
2011-05-03T17:40:21+00:00 heroku[worker.1]: Process exited

R13 — Attach error

A dyno started with heroku run failed to attach to the invoking client.

2011-06-29T02:13:29+00:00 app[run.3]: Awaiting client
2011-06-29T02:13:30+00:00 heroku[run.3]: State changed from starting to up
2011-06-29T02:13:59+00:00 app[run.3]: Error R13 (Attach error) -> Failed to attach to process
2011-06-29T02:13:59+00:00 heroku[run.3]: Process exited

R14 — Memory quota exceeded

A dyno requires memory in excess of its quota. If this error occurs, the dyno will page to swap space to continue running, which may cause degraded process performance. The R14 error is calculated by total memory swap, rss and cache.

2011-05-03T17:40:10+00:00 app[worker.1]: Working
2011-05-03T17:40:10+00:00 heroku[worker.1]: Process running mem=1028MB(103.3%)
2011-05-03T17:40:11+00:00 heroku[worker.1]: Error R14 (Memory quota exceeded)
2011-05-03T17:41:52+00:00 app[worker.1]: Working

If you are getting a large number of R14 errors, your application performance is likely severely degraded. Resolving R14 memory errors are language specific:

R14 — Memory Quota Exceeded in Ruby (MRI)
Troubleshooting Memory Issues in Java Applications
Troubleshooting Node.js Memory Use

R15 — Memory quota vastly exceeded

A dyno requires vastly more memory than its quota and is consuming excessive swap space. If this error occurs, the dyno will be forcibly killed with SIGKILL (which cannot be caught or handled) by the platform. The R15 error is calculated by total memory swap and rss; cache is not included.

2011-05-03T17:40:10+00:00 app[worker.1]: Working
2011-05-03T17:40:10+00:00 heroku[worker.1]: Process running mem=1029MB(201.0%)
2011-05-03T17:40:11+00:00 heroku[worker.1]: Error R15 (Memory quota vastly exceeded)
2011-05-03T17:40:11+00:00 heroku[worker.1]: Stopping process with SIGKILL
2011-05-03T17:40:12+00:00 heroku[worker.1]: Process exited

In Private Spaces, dynos exceeding their memory quota do not use swap space and thus do not emit R14 errors.

Private Space dynos vastly exceeding their memory quota generally will emit R15 errors but occasionally the platform may shut down the dyno before the R15 is sent, causing the error to be dropped. If an R15 is emitted it will only be visible in the app log stream but not in the dashboard Application Metrics interface. Other non-R15 types of errors from Private Space dynos are correctly surfaced in the Application Metrics interface.

For Private Space dynos vastly exceeding their memory quota the platform kills dyno processes consuming large amounts of memory, but may not kill the dyno itself.

R16 — Detached

An attached dyno is continuing to run after being sent SIGHUP when its external connection was closed. This is usually a mistake, though some apps might want to do this intentionally.

2011-05-03T17:32:03+00:00 heroku[run.1]: Awaiting client
2011-05-03T17:32:03+00:00 heroku[run.1]: Starting process with command `bash`
2011-05-03T17:40:11+00:00 heroku[run.1]: Client connection closed. Sending SIGHUP to all processes
2011-05-03T17:40:16+00:00 heroku[run.1]: Client connection closed. Sending SIGHUP to all processes
2011-05-03T17:40:21+00:00 heroku[run.1]: Client connection closed. Sending SIGHUP to all processes
2011-05-03T17:40:26+00:00 heroku[run.1]: Error R16 (Detached) -> An attached process is not responding to SIGHUP after its external connection was closed.

R17 — Checksum error

This indicates an error with runtime slug checksum verification. If the checksum does not match or there is another problem with the checksum when launch a dyno, an R17 error will occur and the dyno will fail to launch. Check the log stream for details about the error.

2016-08-16T12:39:56.439438+00:00 heroku[web.1]: State changed from provisioning to starting
2016-08-16T12:39:57.110759+00:00 heroku[web.1]: Error R17 (Checksum error) -> Checksum does match expected value. Expected: SHA256:ed5718e83475c780145609cbb2e4f77ec8076f6f59ebc8a916fb790fbdb1ae64 Actual: SHA256:9ca15af16e06625dfd123ebc3472afb0c5091645512b31ac3dd355f0d8cc42c1
2016-08-16T12:39:57.212053+00:00 heroku[web.1]: State changed from starting to crashed

If this error occurs, try deploying a new release with a correct checksum or rolling back to an older release. Ensure the checksum is formatted and calculated correctly with the SHA256 algorithm. The checksum must start with SHA256: followed by the calculated SHA256 value for the compressed slug. If you did not manually calculate the checksum and error continues to occur, please contact Heroku support.

R99 — Platform error

R99 and H99 are the only error codes that represent errors in the Heroku platform.

L10 — Drain buffer overflow

2013-04-17T19:04:46+00:00 d.1234-drain-identifier-567 heroku logplex - - Error L10 (output buffer overflow): 500 messages dropped since 2013-04-17T19:04:46+00:00.

The number of log messages being generated has temporarily exceeded the rate at which they can be received by a drain consumer (such as a log management add-on) and Logplex, Heroku’s logging system, has discarded some messages in order to handle the rate difference.

A common cause of L10 error messages is the exhaustion of capacity in a log consumer. If a log management add-on or similar system can only accept so many messages per time period, your application may experience L10s after crossing that threshold.

Another common cause of L10 error messages is a sudden burst of log messages from a dyno. As each line of dyno output (e.g. a line of a stack trace) is a single log message, and Logplex limits the total number of un-transmitted log messages it will keep in memory to 1024 messages, a burst of lines from a dyno can overflow buffers in Logplex. In order to allow the log stream to catch up, Logplex will discard messages where necessary, keeping newer messages in favor of older ones.

You may need to investigate reducing the volume of log lines output by your application (e.g. condense multiple log lines into a smaller, single-line entry). You can also use the heroku logs -t command to get a live feed of logs and find out where your problem might be. A single dyno stuck in a loop that generates log messages can force an L10 error, as can a problematic code path that causes all dynos to generate a multi-line stack trace for some code paths.

L11 — Tail buffer overflow

A heroku logs –tail session cannot keep up with the volume of logs generated by the application or log channel, and Logplex has discarded some log lines necessary to catch up. To avoid this error you will need run the command on a faster internet connection (increase the rate at which you can receive logs) or you will need to modify your application to reduce the logging volume (decrease the rate at which logs are generated).

2011-05-03T17:40:10+00:00 heroku[logplex]: L11 (Tail buffer overflow) -> This tail session dropped 1101 messages since 2011-05-03T17:35:00+00:00

L12 — Local buffer overflow

The application is producing logs faster than the local delivery process (log-shuttle) can deliver them to logplex and has discarded some log lines in order to keep up. If this error is sustained you will need to reduce the logging volume of your application.

2013-11-04T21:31:32.125756+00:00 app[log-shuttle]: Error L12: 222 messages dropped since 2013-11-04T21:31:32.125756+00:00.

L13 — Local delivery error

The local log delivery process (log-shuttle) was unable to deliver some logs to Logplex and has discarded them. This can happen during transient network errors or during logplex service degradation. If this error is sustained please contact support.

2013-11-04T21:31:32.125756+00:00 app[log-shuttle]: Error L13: 111 messages lost since 2013-11-04T21:31:32.125756+00:00.

L14 — Certificate validation error

The application is configured with a TLS syslog drain that doesn’t have a valid TLS certificate.

You should check that:

You’re not using a self-signed certificate.
The certificate is up to date.
The certificate is signed by a known and trusted CA.
The CN hostname embedded in the certificate matches the hostname being connected to.

2015-09-04T23:28:48+00:00 heroku[logplex]: Error L14 (certificate validation): error="bad certificate" uri="syslog+tls://logs.example.com:6514/"

L15 — Tail buffer temporarily unavailable

The tail buffer that stores the last 1500 lines of your logs is temporarily unavailable. Run heroku logs again. If you still encounter the error, run heroku logs -t to stream your logs (which does not use the tail buffer).

Источник

у меня есть приложение RoR, работающее на моем локальном компьютере, но когда я отправляю его в heroku, он падает. Журнал ошибок выдает ошибку H10 и говорит:

    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

кто-нибудь это раньше, и знаю, что может быть причиной проблемы? Я не могу найти решение.

спасибо.

2959

24

24 ответов:

я столкнулся с той же ошибкой выше, приложение рушилось на heroku (работает нормально в dev), но журналы ошибок на heroku не показывали никаких подсказок. Я прочитал другие ответы на этой странице и вспотел, увидев «восстановление приложения.- Я подумал, что, может быть, мне удастся залезть в консоль heroku и осмотреться. Я сделал это, и даже консоль разбилась, но на этот раз она сказала мне, почему. Это была какая-то неясная переменная, которую я забыл удалить во время сеанса устранения неполадок несколькими часами ранее. Я не говорю, что ты столкнется с той же проблемой, но я нашел больше информации, когда попытался пройти через консоль. Надеюсь, это поможет.
    $heroku run rails console

у меня была такая же проблема. Журналы тоже не давали мне никаких подсказок.
Поэтому я уменьшил и снова увеличил Динос. Это решило проблему для меня:
heroku ps:scale web=0
подождал несколько секунд…
heroku ps:scale web=1

$heroku run rails console 
Это лучший вариант, так как он даст вам ошибку в вашем терминале, которая будет гораздо более подробной, чем ошибка «приложение разбилось» в ваших журналах Heroku.

$ heroku restart
помог мне снова запустить мой Дино. Я новичок в Heroku, но рад, что теперь знаю.

это случилось со мной, когда я слушал на неправильный порт

Я изменил свой listen () на » process.ОКР.Порт » Итак:
http.listen((process.env.PORT || 5000), function(){
  console.log('listening on *:5000');
});
вместо
http.listen(5000, function(){
  console.log('listening on *:5000');
});

была такая же проблема сегодня вечером. Не очень полезная ошибка, поэтому я попытался запустить в консоли
heroku run rails c
это не удалось и дал мне гораздо более полезную ошибку. Я забыл удалить вызов метода в производство. Как только я это исправил, приложение работало нормально.

я решил эту проблему, нажав на Git:
git add .
git commit -am "some text"
git push
затем нажмите на Heroku:
git push heroku
затем rake db: migrate on Heroku:
heroku run rake db:migrate

мне удалось не включить мой .gitignore file — > что ломает heroku. #ДЗ

вот такой рабочий .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
для создания a .gitignore file, в терминале перейдите в каталог приложений и используйте следующую команду
touch .gitignore
затем вы можете открыть его в текстовом редакторе и вставьте код в него.

Я получал этот же H10 приложение разбился ошибку в Heroku. Я нажал «перезагрузить все dynos» в интерфейсе heroku, и проблема решена.

в моем случае я использовал переменные ENV в своем приложении, но он не был установлен в конфигурации heroku.

консоль heroku дала правильную ошибку:
heroku console
`validate_options': Missing required arguments: aws_access_key_id, aws_secret_access_key (ArgumentError)
затем установите env config
heroku config:set AWS_ACCESS_KEY_ID='key'
перезапустить Heroku
heroku restart
это работает!!

смотрите, если вы получите
bash: bin/rails: No such file or directory
в журналах во время работы (heroku logs-t) команда, если да, то пожалуйста, запустите
bundle exec rake rails:update
не перезаписывайте свои файлы, в конце концов эта команда создаст
  create  bin
  create  bin/bundle
  create  bin/rails
  create  bin/rake
нажмите эти файлы на heroku, и вы сделали.

корень проблемы, с которой я столкнулся, был связан с отсутствием базы данных. Чтобы решить эту проблему, я сначала экспортировал свою локальную базу данных:
$ 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 
затем импортировал его в Heroku:
$ heroku pgbackups:restore DATABASE 'http://site.tld/mydb.dump'
переменные для замены в этих примерах являются:mypassword,myuser,mydb & http://site.tld/mydb.dump. Обратите внимание, что мне пришлось загрузить дамп на временный сервер.

решение всех моих проблем я написал краткое руководство о том, как развернуть Enki в Heroku,что может быть нашли здесь.

Я получил ту же ошибку выше, что и «приложение разбилось», и журналы приложений heroku не показывают много информации, связанной с причинами ошибки msg. Затем я перезапустил dynos в heroku, а затем он показал ошибку, сказав дополнительную фигурную скобку в одном из индексов.файлы js в моей настройке. Проблема была исправлена после того, как он был удален и перераспределен приложение на heroku.

надеюсь, что это будет полезно для тех, кто сталкивается с той же проблемой.

пройдя весь список ответов я наткнулся на этот сайт:https://status.heroku.com/ который детализирует текущий статус / инциденты с Heroku. Его всегда безопасно проверить на наличие инцидентов, прежде чем ударить головой о стену. Для меня это был прикрепленный отчет об инциденте, опубликованный по вышеупомянутой ссылке, которая вызвала ошибку.

У меня была такая же проблема, я сделал следующее
heroku run rails c
Он определил синтаксическую ошибку и отсутствующую запятую в контроллере разрешенных параметров. Как упоминалось выше, журналы Heroku не предоставили достаточной информации для решения проблемы.

Я не видел приложение разбилось сообщение на Heroku ранее.

Я сегодня столкнулся с той же проблемой. Я сделал heroku run rake db:migrate хотя я перенес модель раньше, и приложение не падает.

будьте очень осторожны с копированием и вставкой кода. Иногда, когда вы добавляете блок в файл, он форматируется неправильно и приведет к ошибке.

У меня была эта проблема раньше, и я получил эту ошибку: неожиданный tIDENTIFIER, ожидая keyword_end

была такая же проблема. для меня это была ошибка в фильтрах before_action (потому что пустая БД)
Проверьте свои фильтры before_action, может быть, они бросают необработанные exeptions.

у меня была эта проблема при попытке запустить Rails в подкаталоге, а не в /. Например, у меня было приложение Angular/Node/Gulp, работающее в /client и приложение Rails работает в /server, но оба они были в одном и том же репозитории git, поэтому я мог отслеживать изменения на переднем и заднем концах. Я получил эту ошибку при попытке развернуть их в Heroku. Для тех, кто еще имеет эту проблему, вот пользовательский buildpack, который позволит запускать Rails в a подкаталог.

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

у меня была та же проблема (та же ошибка на heroku, работающая на локальной машине), и я попробовал все решения, перечисленные здесь, включая
heroku run rails console
который работал без сообщений об ошибках. Я пытался heroku run rake db:migrate и heroku run rake db:migrate:reset несколько раз. Ничего из этого не решило проблему. При просмотре некоторых файлов, которые используются в производстве, но не в среде разработки, я нашел некоторые пробелы в puma.rb файл, чтобы быть виновником. Надеюсь, это поможет кому-то, у кого есть такая же проблема.
Изменение это работа
  ActiveRecord::Base.establish_connection
  End
до
  ActiveRecord::Base.establish_connection
end

Я столкнулся с той же проблемой при развертывании в Heroku (сбой приложения). Журналы не указали, в чем может быть проблема. В Heroku консоли отображается ошибка синтаксиса в коде дополнительный кронштейн. Удивительно, но у меня не было проблемы с локальными рельсами при запуске приложения и, следовательно, пропустил его. После коррекции и git push to Heroku, приложение начало работать на Heroku!

я обновил свои настройки с
приложение.set (‘ip_address’, process.ОКР.IP|/ ‘127.0.0.1’);

до

приложение.set (‘ip_address’, process.ОКР.IP|/ ‘0.0.0.0’);

который я изменил для хостинга Openshift

Я H10 С Heroku и узлом из-за неправильного имени основного файла кода. Редактировать package.json:
{

  ...

  "main": "correct_file_name.js",

  ...

  "scripts": {
    "start": "node correct_file_name.js"
  }
}
или переименовать файл.

В моем случае Procfile раньше я все ломал. Героку ищет Procfile и применяет свои настройки при запуске приложения-очевидно, что настройки dev, которые я использовал, не имели никакого смысла для сервера prod. Мне пришлось переименовать его в Procfile.dev и все начало работать нормально.

Источник

i have searched around for this error on SO but it seems there are so many reasons why this error can appear and none seem to be similar with mine.

I am new to heroku, this is actually my first deployment on the platform.I have created a Spring boot app with thymeleaf and a mysql database.I am using herokus own ClearDB cloud db wich i successfully connected to my local rdbms.The app was synchronised on the platform with a git repository.

The app works fine on localhost and it was also successfully deployed on heroku as stated by the platform.Each time i try to start the application from heroku i get an application error.The logs say the following

2020-07-14T14:13:38.972105+00:00 app[web.1]: Error: Could not create the Java Virtual Machine. 2020-07-14T14:13:38.972108+00:00 app[web.1]: Error: A fatal exception has occurred. Program will exit. 2020-07-14T14:13:39.017969+00:00 heroku[web.1]: Process exited with status 1 2020-07-14T14:13:39.062501+00:00 heroku[web.1]: State changed from starting to crashed 2020-07-14T14:15:20.313138+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=roommanager1.herokuapp.com request_id=35122073-efb5-4244-852d-cdf1778cf919 fwd="86.124.21.129" dyno= connect= service= status=503 bytes= protocol=https 2020-07-14T14:15:20.848774+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=roommanager1.herokuapp.com request_id=b9e45355-eb87-4a0f-8528-b47b5eaffdab fwd="86.124.21.129" dyno= connect= service= status=503 bytes= protocol=https 2020-07-14T14:15:59.976811+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=roommanager1.herokuapp.com request_id=939747d9-8e28-40b2-81aa-bcfebbfa3241 fwd="86.124.21.129" dyno= connect= service= status=503 bytes= protocol=https 2020-07-14T14:16:00.206366+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=roommanager1.herokuapp.com request_id=43ee5528-26ee-4668-a226-504f8f7636d1 fwd="86.124.21.129" dyno= connect= service= status=503 bytes= protocol=https 2020-07-14T14:33:14.438079+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=roommanager1.herokuapp.com request_id=7d9e0f13-badd-4579-aab8-5b48bd5f0cb5 fwd="86.124.21.129" dyno= connect= service= status=503 bytes= protocol=https 2020-07-14T14:33:14.947903+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=roommanager1.herokuapp.com request_id=0030f545-f148-4dc8-a256-cca5a0abbbc0 fwd="86.124.21.129" dyno= connect= service= status=503 bytes= protocol=https 2020-07-14T14:38:51.155083+00:00 heroku[web.1]: State changed from crashed to starting 2020-07-14T14:38:54.791871+00:00 heroku[web.1]: Starting process with command `java $JAVA_OPTS - jar target/roomManager-0.0.1-SNAPSHOT.jar -Dserver.port=#PORT $JAR_OPTS` 2020-07-14T14:38:56.104659+00:00 heroku[web.1]: Process exited with status 1 2020-07-14T14:38:56.126096+00:00 heroku[web.1]: State changed from starting to crashed 2020-07-14T14:38:56.065158+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them. 2020-07-14T14:38:56.068366+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8 2020-07-14T14:38:56.068437+00:00 app[web.1]: Unrecognized option: - 2020-07-14T14:38:56.068438+00:00 app[web.1]: Error: Could not create the Java Virtual Machine. 2020-07-14T14:38:56.068440+00:00 app[web.1]: Error: A fatal exception has occurred. Program will exit. 2020-07-14T15:19:49.301124+00:00 heroku[web.1]: State changed from crashed to starting 2020-07-14T15:19:53.370758+00:00 heroku[web.1]: Starting process with command `java $JAVA_OPTS - jar target/roomManager-0.0.1-SNAPSHOT.jar -Dserver.port=#PORT $JAR_OPTS` 2020-07-14T15:19:55.205516+00:00 heroku[web.1]: Process exited with status 1 2020-07-14T15:19:55.244509+00:00 heroku[web.1]: State changed from starting to crashed 2020-07-14T15:19:55.162382+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them. 2020-07-14T15:19:55.166086+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8 2020-07-14T15:19:55.166162+00:00 app[web.1]: Unrecognized option: - 2020-07-14T15:19:55.166163+00:00 app[web.1]: Error: Could not create the Java Virtual Machine. 2020-07-14T15:19:55.166163+00:00 app[web.1]: Error: A fatal exception has occurred. Program will exit. Disconnected from log stream. There may be events happening that you do not see here! Attempting to reconnect... Connection to log stream failed. Please try again later.

this is my app propreties

spring.datasource.url=* spring.datasource.username=* spring.datasource.password=* #Conflicts with heroku so have to comment out #spring.jpa.database-platform=org.hibernate.dialect.MySQL8Dialect spring.jpa.hibernate.ddl-auto=update #Change from never to always in order to add data from .sql to db spring.datasource.initialization-mode=never spring.data=data.sql spring.datasource.max-active=3; server.port=${PORT:8080}

and this is my procfile wich is in the app root folder

web: java $JAVA_OPTS - jar target/roomManager-0.0.1-SNAPSHOT.jar -Dserver.port=#PORT $JAR_OPTS

Can you please help me find the issue and make my app functional? Thank you!

Источник

I am trying to run my simple node app on Heroku.

Here is the directory structure

├── app.js
├── assets
├── blog.html
├── index.html
├── node_modules
└── package.json

Here is my app.js

let express = require('express'),
    path = require('path');
var app = express();
let server = require('http').Server(app);

app.use(express.static(path.join(__dirname)));

app.get('/', function(req, res, next){
    res.sendStatus(200);
});

app.get('/blog.html', function(req, res,next){
    res.sendFile(path.join(__dirname+"/blog.html"));
});

app.post('/contact', function(req, res, next){

});
server.listen('8000', function() {
    console.log("App is running on port 8000");
});

Here is the package.json

{
  "name": "website",
  "version": "1.0.0",
  "engines" : {
    "node" : "6.3.1",
    "npm" : "3.10.3"
  },
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo "Error: no test specified" && exit 1",
    "start" : "node app.js"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "express": "^4.14.0"
  }
}

When I go to the console it rightly prints app is starting at xxxx port.
But then the app crashes with the following message

2016-08-10T13:12:49.839138+00:00 app[web.1]: App is running on port xxxx
2016-08-10T13:13:34.944963+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/" host=saras-website.herokuapp.com request_id=28d8705a-d5a4-4aaa-bd8d-4c4c6101fbd4 fwd="106.51.20.181" dyno= connect= service= status=503 bytes=
2016-08-10T13:13:48.295315+00:00 heroku[web.1]: State changed from starting to crashed
2016-08-10T13:13:48.552740+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=saras-website.herokuapp.com request_id=b77e151f-7017-482d-b4ba-15d980534fd7 fwd="106.51.20.181" dyno= connect= service= status=503 bytes=
2016-08-10T13:13:50.163466+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=saras-website.herokuapp.com request_id=1e7b57e5-1056-4cb3-b41f-cd3f11794efe fwd="106.51.20.181" dyno= connect= service= status=503 bytes=

I don’t know what am I doing wrong here… Help is appreciated

Answer

Set port like this

ES5:

var port = process.env.PORT || 8000;

And

server.listen(port, function() {
    console.log("App is running on port " + port);
});

ES6:

const port = process.env.PORT || 8000;

And

server.listen(port, () => {
    console.log("App is running on port " + port);
});

This allows Heroku to set the port at run time.

Attribution
Source : Link , Question Author : Saras Arya , Answer Author : Hemadri Dasari

Источник

Take a look at this:

Read next

51 AI tools you should be using for life, programming, content creation and everything else

How to implement a .NET Core DbConnectionFactory?

React useRef() 🪝

Regular expressions are no longer a problem thanks to OpenAI!

Table of Contents

H10 — App crashed

H11 — Backlog too deep

H12 — Request timeout

H13 — Connection closed without response

H14 — No web dynos running

H15 — Idle connection

H16 — (No Longer in Use)

H17 — Poorly formatted HTTP response

H18 — Server Request Interrupted

H19 — Backend connection timeout

H20 — App boot timeout

H21 — Backend connection refused

H22 — Connection limit reached

H23 — Endpoint misconfigured

H24 — Forced close

H25 — HTTP Restriction

Invalid content length

Oversized cookies

Oversized status line

H26 — Request Error

Bad chunk

H27 — Client Request Interrupted

H28 — Client Connection Idle

H31 — Misdirected Request

H80 — Maintenance mode

H81 — Blank app

H82 — You’ve used up your dyno hour pool

H83 — Planned Service Degradation

H99 — Platform error

R10 — Boot timeout

R12 — Exit timeout

R13 — Attach error

R14 — Memory quota exceeded

R15 — Memory quota vastly exceeded

R16 — Detached

R17 — Checksum error

R99 — Platform error

L10 — Drain buffer overflow

L11 — Tail buffer overflow

L12 — Local buffer overflow

L13 — Local delivery error

L14 — Certificate validation error

L15 — Tail buffer temporarily unavailable

24 ответов:

Answer