I have deployed app on Heroku but app is not working( I got this message on browser "We're sorry, but something went wrong. If you are the application owner check the logs for more information.") when I checked log I found below message.Can anyone tell me what is the meaning of it?
Stopping all processes with SIGTERM
2018-01-20T10:54:29.710117+00:00 app[web.1]: - Gracefully stopping, waiting for requests to finish
2018-01-20T10:54:29.710722+00:00 app[web.1]: === puma shutdown: 2018-01-20 10:54:29 +0000 ===
2018-01-20T10:54:29.710724+00:00 app[web.1]: - Goodbye!
2018-01-20T10:54:29.710881+00:00 app[web.1]: Exiting
2018-01-20T10:54:29.837650+00:00 heroku[web.1]: Process exited with status 143
2018-01-20T10:54:39.660402+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 38017 -e production`
2018-01-20T10:54:45.686497+00:00 app[web.1]: DEPRECATION WARNING: `config.serve_static_files` is deprecated and will be removed in Rails 5.1.
2018-01-20T10:54:45.686528+00:00 app[web.1]: Please use `config.public_file_server.enabled = true` instead.
2018-01-20T10:54:45.686586+00:00 app[web.1]: (called from block in <top (required)> at /app/config/environments/production.rb:6)
2018-01-20T10:54:47.277792+00:00 app[web.1]: => Booting Puma
2018-01-20T10:54:47.277810+00:00 app[web.1]: => Rails 5.0.6 application starting in production on http://0.0.0.0:38017
2018-01-20T10:54:47.277812+00:00 app[web.1]: => Run `rails server -h` for more startup options
2018-01-20T10:54:47.277818+00:00 app[web.1]: * Version 3.10.0 (ruby 2.3.4-p301), codename: Russell's Teapot
2018-01-20T10:54:47.277813+00:00 app[web.1]: Puma starting in single mode...
2018-01-20T10:54:47.277819+00:00 app[web.1]: * Min threads: 0, max threads: 16
2018-01-20T10:54:47.277908+00:00 app[web.1]: * Listening on tcp://0.0.0.0:38017
2018-01-20T10:54:47.277820+00:00 app[web.1]: * Environment: production
2018-01-20T10:54:47.278132+00:00 app[web.1]: Use Ctrl-C to stop
2018-01-20T10:54:47.817688+00:00 heroku[web.1]: State changed from starting to up
2018-01-20T10:56:14.896122+00:00 heroku[router]: at=info method=GET path="/" host=salty-peak-94323.herokuapp.com request_id=85b8c594-2d92-4e76-9060-01caf2307a44 fwd="45.115.104.19" dyno=web.1 connect=0ms service=268ms status=500 bytes=1735 protocol=https
2018-01-20T10:59:49.774607+00:00 heroku[router]: at=info method=GET path="/" host=salty-peak-94323.herokuapp.com request_id=d60e4280-6d74-42ff-93e4-5a47dcc3bc93 fwd="45.115.104.19" dyno=web.1 connect=0ms service=41ms status=500 bytes=1735 protocol=https
The logs says DEPRECATION WARNING: config.serve_static_files is deprecated and will be removed in Rails 5.1, Please use config.public_file_server.enabled = true instead, So try to change this to what it is saying, Although i believe it is just a warning and it should not break your app but i found a related question to this one, Here it is, Hope it helps
Related
I deployed my rails app on Heroku.
When I try to create a new profile, my app crashes. My logs display a Client Request Interrupted error. You can see my logs below.
I searched this error on heroku dev center: https://devcenter.heroku.com/changelog-items/662
On this page (https://devcenter.heroku.com/changelog-items/662):
It said : "This error will be logged if the client socket was closed either in the middle of the request or before a response could be returned."
Then
"This error condition caused an H18 to be logged and the sock field could be used to differentiate between what are now H18 and H27 errors. "
H18 - Server Request Interrupted
The backend socket, belonging to your app’s web process was closed before the backend returned an HTTP response.
2019-02-05T15:53:19.905345+00:00 app[web.1]: bundler: failed to load command: puma (/app/vendor/bundle/ruby/2.5.0/bin/puma)
2019-02-05T15:53:19.905399+00:00 app[web.1]: SignalException: SIGTERM
2019-02-05T15:53:19.905401+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/gems/puma-3.12.0/lib/puma/launcher.rb:398:in `block in setup_signals'
2019-02-05T15:53:19.905406+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/gems/puma-3.12.0/lib/puma/single.rb:115:in `join'
2019-02-05T15:53:19.905407+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/gems/puma-3.12.0/lib/puma/single.rb:115:in `run'
2019-02-05T15:53:19.905409+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/gems/puma-3.12.0/lib/puma/launcher.rb:184:in `run'
2019-02-05T15:53:19.905410+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/gems/puma-3.12.0/lib/puma/cli.rb:78:in `run'
2019-02-05T15:53:19.905412+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/gems/puma-3.12.0/bin/puma:10:in `<top (required)>'
2019-02-05T15:53:19.905414+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/bin/puma:23:in `load'
2019-02-05T15:53:19.905415+00:00 app[web.1]: /app/vendor/bundle/ruby/2.5.0/bin/puma:23:in `<top (required)>'
2019-02-05T21:33:39.526627+00:00 heroku[web.1]: Unidling
2019-02-05T21:33:53.579585+00:00 app[web.1]: Puma starting in single mode...
2019-02-05T21:33:53.579631+00:00 app[web.1]: * Version 3.12.0 (ruby 2.5.3-p105), codename: Llamas in Pajamas
2019-02-05T21:33:53.579632+00:00 app[web.1]: * Min threads: 5, max threads: 5
2019-02-05T21:33:53.579634+00:00 app[web.1]: * Environment: production
2019-02-05T21:34:00.063370+00:00 heroku[web.1]: State changed from starting to up
2019-02-05T21:33:59.640588+00:00 app[web.1]: * Listening on tcp://0.0.0.0:11397
2019-02-05T21:33:59.642173+00:00 app[web.1]: Use Ctrl-C to stop
2019-02-05T21:34:02.204235+00:00 heroku[router]: sock=client at=warning code=H27 desc="Client Request Interrupted" method=GET path="/" host=agora-challenge.herokuapp.com request_id=9d994b8b-eff4-4088-b2be-a42b14fec708 fwd="209.17.96.226" dyno=web.1 connect=1ms service=119ms status=499 bytes= protocol=https
The important part to notice is the sock=client which means that the request was interrupted at the request of the client:
2019-02-05T21:34:02.204235+00:00 heroku[router]: sock=client at=warning code=H27 desc="Client Request Interrupted" method=GET path="/" host=agora-challenge.herokuapp.com request_id=9d994b8b-eff4-4088-b2be-a42b14fec708 fwd="209.17.96.226" dyno=web.1 connect=1ms service=119ms status=499 bytes= protocol=https
I didn't understand either Heroku dev center explanations nor previous Stack Overflow questions.
Thanks a lot for your answers.
well i'm trying to deploy my application using Heroku and I'm getting some errors that my internet digging was not enough to solve. The deploy goes fine, showing it was successful:
remote: Verifying deploy... done.
To https://git.heroku.com/MYAPPHERE.git
7715c7c..c85251d master -> master
but when I go to the domain it shows this message:
"Application Error, An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details."
my logs show this:
018-05-18T19:14:24.000000+00:00 app[api]: Build succeeded
2018-05-18T19:14:28.864974+00:00 heroku[web.1]: Starting process with command `bundle exec puma -C config/puma.rb`
2018-05-18T19:14:31.064709+00:00 app[web.1]: [4] Puma starting in cluster mode...
2018-05-18T19:14:31.064729+00:00 app[web.1]: [4] * Version 3.11.4 (ruby 2.3.1-p112), codename: Love Song
2018-05-18T19:14:31.064730+00:00 app[web.1]: [4] * Min threads: 5, max threads: 5
2018-05-18T19:14:31.064732+00:00 app[web.1]: [4] * Environment: production
2018-05-18T19:14:31.064752+00:00 app[web.1]: [4] * Process workers: 2
2018-05-18T19:14:31.064776+00:00 app[web.1]: [4] * Preloading application
2018-05-18T19:14:33.736893+00:00 app[web.1]: [4] * Listening on tcp://0.0.0.0:36902
2018-05-18T19:14:33.737145+00:00 app[web.1]: [4] * Listening on tcp://0.0.0.0:36902
2018-05-18T19:14:33.737416+00:00 app[web.1]: bundler: failed to load command: puma (/app/vendor/bundle/ruby/2.3.0/bin/puma)
2018-05-18T19:14:33.737462+00:00 app[web.1]: Errno::EADDRINUSE: Address already in use - bind(2) for "0.0.0.0" port 36902
2018-05-18T19:14:33.737465+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/binder.rb:270:in `initialize'
2018-05-18T19:14:33.737466+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/binder.rb:270:in `new'
2018-05-18T19:14:33.737468+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/binder.rb:270:in `add_tcp_listener'
2018-05-18T19:14:33.737469+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/binder.rb:105:in `block in parse'
2018-05-18T19:14:33.737471+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/binder.rb:88:in `each'
2018-05-18T19:14:33.737472+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/binder.rb:88:in `parse'
2018-05-18T19:14:33.737474+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/runner.rb:144:in `load_and_bind'
2018-05-18T19:14:33.737475+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/cluster.rb:397:in `run'
2018-05-18T19:14:33.737477+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/launcher.rb:184:in `run'
2018-05-18T19:14:33.737478+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/lib/puma/cli.rb:78:in `run'
2018-05-18T19:14:33.737480+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/puma-3.11.4/bin/puma:10:in `<top (required)>'
2018-05-18T19:14:33.737482+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/bin/puma:23:in `load'
2018-05-18T19:14:33.737483+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/bin/puma:23:in `<top (required)>'
2018-05-18T19:14:33.833127+00:00 heroku[web.1]: State changed from starting to up
2018-05-18T19:14:33.953708+00:00 heroku[web.1]: State changed from up to crashed
2018-05-18T19:14:33.931364+00:00 heroku[web.1]: Process exited with status 1
2018-05-18T19:14:35.621801+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=MYAPPNAME request_id=74c67c85-dce7-4da8-9770-f41513d8cf31 fwd="179.178.13.25" dyno= connect= service= status=503 bytes= protocol=https
On my gemfile:
# Use Puma as the app server
gem 'puma', '~> 3.7'
on config/puma:
plugin :tmp_restart
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'] || 'development'
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
I see that an error occurred with the Address, but I don't use this address for anything at all. I tried running lsof -wni tcp:36902 and it shows nothing.
Hope I provided enough information.
Seems like puma is trying to bind listeners twice:
2018-05-18T19:14:33.736893+00:00 app[web.1]: [4] * Listening on tcp://0.0.0.0:36902
2018-05-18T19:14:33.737145+00:00 app[web.1]: [4] * Listening on tcp://0.0.0.0:36902
You may want to try moving your preload_app! below your port & environment configuration. (by calling port, it may be calling two bind functions similar to here)
I'm running Heroku w/ puma 3.11.4 currently, and my config/puma.rb looks like:
threads_count = ENV.fetch('RAILS_MAX_THREADS', 5)
threads threads_count, threads_count
environment ENV.fetch('RAILS_ENV', 'development')
port ENV.fetch('PORT', 3000)
workers ENV.fetch('WEB_CONCURRENCY', 2)
preload_app!
before_fork do
ActiveRecord::Base.connection_pool.disconnect! if defined?(ActiveRecord)
end
on_worker_boot do
ActiveRecord::Base.establish_connection if defined?(ActiveRecord)
end
# Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart
It might also be helpful to see your Procfile. Just want to confirm it looks something like:
A simple Procfile might be:
web: bundle exec puma -C config/puma.rb
I've been trouble-shooting my crashed application on Heroku without success. I'm using:
Ruby 2.1.0
Rails 4.1.6
Unicorn web server
I'm getting an Application Error when I go to my url.
These are the last few lines from heroku logs
2015-03-13T20:44:36.095469+00:00 app[web.1]: from config.ru:1:in `new'
2015-03-13T20:44:36.095481+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/bin/unicorn:23:in `load'
2015-03-13T20:44:36.095477+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/unicorn- 4.8.3/lib/unicorn/http_server.rb:764:in `build_app!'
2015-03-13T20:44:36.095483+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/bin/unicorn:23:in `<main>'
2015-03-13T20:44:36.095470+00:00 app[web.1]: from config.ru:1:in `<main>'
2015-03-13T20:44:36.095471+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn.rb:48:in `eval'
2015-03-13T20:44:36.095467+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
2015-03-13T20:44:36.095473+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn.rb:48:in `block in builder'
2015-03-13T20:44:36.095474+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:764:in `call'
2015-03-13T20:44:36.095479+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:137:in `start'
2015-03-13T20:44:36.095480+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
2015-03-13T20:44:36.912915+00:00 heroku[web.1]: Process exited with status 1
2015-03-13T20:44:37.040788+00:00 heroku[web.1]: State changed from starting to crashed
2015-03-13T20:45:09.859594+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=stand-as-witnesses-staging.herokuapp.com request_id=2228b811-6b37-482e-a1ec-630699947581 fwd="71.232.132.204" dyno= connect= service= status=503 bytes=
Heroku ps gives:
=== web (1X): `bundle exec unicorn -p $PORT -c ./config/unicorn.rb`
web.1: crashed 2015/03/13 16:44:37 (~ 19m ago)
I upgraded from Ruby 2.0.0 to 2.1.0 and from Unicorn 4.6.3 to 4.8.3 to see if that would solve the problem, but no help there.
My Procfile and app/config/unicorn.rb files are standard based on Heroku's instructions for using unicorn.
Since the app runs fine locally, can anyone point out why I'm getting this crash?
Thanks!
Seems like you should specify model class instead (as I understand this is BlockedSite) of controller in your app/admin/blocked_site.rb AA file. This should fix error:
superclass mismatch for class BlockedSitesController (TypeError)
Thanks for pointing me in the right direction. It turns out that the problem was that we had an existing file in app/controllers/admin/blocked_sites_controller.rb. When I removed that file and a couple of others in that same location, the crashes went away and I was able to navigate to my pages.
Hi I am in the midst of Ruby on Rails tutorial. MY pages are rendering perfectly on the localserver but NOT on Heroku. I have run the command "heroku run rake db:migrate". I also have gone through the Heroku logs. I am just not sure how to read them.
I am wondering if it has to do with my stylesheets but I replicated whatever was on my local server to github and heroku so not sure why it can't read it.
I am add a part of the logfile. I wish I could show snapshots but unfortunately I don't have rights to do so.
I would appreciate any help and tips on debugging this problem.
====logfile===========================================
2012-03-19T18:22:42+00:00 heroku[web.1]: State changed from starting to up
2012-03-19T18:22:43+00:00 app[web.1]: => Booting WEBrick
2012-03-19T18:22:43+00:00 app[web.1]: => Rails 3.2.0 application starting in production on http://0.0.0.0:36524
2012-03-19T18:22:43+00:00 app[web.1]: => Call with -d to detach
2012-03-19T18:22:43+00:00 app[web.1]: => Ctrl-C to shutdown server
2012-03-19T18:22:43+00:00 app[web.1]:
2012-03-19T18:22:43+00:00 app[web.1]:
2012-03-19T18:22:43+00:00 app[web.1]: Started GET "/" for 68.81.36.121 at 2012-03-19 18:22:43 +0000
2012-03-19T18:22:44+00:00 app[web.1]: Processing by StaticPagesController#home as HTML
2012-03-19T18:22:44+00:00 app[web.1]: Rendered static_pages/home.html.erb within layouts/application (11.2ms)
2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_shim.html.erb (0.2ms)
2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_header.html.erb (1.9ms)
2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_footer.html.erb (1.5ms)
2012-03-19T18:22:44+00:00 app[web.1]: Completed 200 OK in 76ms (Views: 75.7ms | ActiveRecord: 0.0ms)
2012-03-19T18:22:44+00:00 app[web.1]: cache: [GET /] miss
2012-03-19T18:22:44+00:00 heroku[router]: GET stormy-mist-1232.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=850ms status=304 bytes=0
2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from up to bouncing
2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from bouncing to created
2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from created to starting
2012-03-19T18:22:51+00:00 heroku[web.1]: Stopping process with SIGTERM
2012-03-19T18:22:51+00:00 app[web.1]: [2012-03-19 18:22:51] ERROR SignalException: SIGTERM
2012-03-19T18:22:51+00:00 app[web.1]: /usr/local/lib/ruby/1.9.1/webrick/server.rb:90:in `select'
2012-03-19T18:22:55+00:00 heroku[web.1]: Starting process with command bundle exec rails server -p 4160
2012-03-19T18:22:59+00:00 app[web.1]: DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: "http://weblog.rubyonrails.org/2012/01/04/rails-3-2-0-rc2-has-been-released." (called from at /app/config/environment.rb:5)
2012-03-19T18:22:59+00:00 app[web.1]: DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: "http://weblog.rubyonrails.org/2012/01/04/rails-3-2-0-rc2-has-been-released". (called from at /app/config/environment.rb:5)
2012-03-19T18:23:01+00:00 heroku[web.1]: Stopping process with SIGKILL
2012-03-19T18:23:01+00:00 heroku[web.1]: Error R12 (Exit timeout) -> Process failed to exit within 10 seconds of SIGTERM
2012-03-19T18:23:02+00:00 heroku[web.1]: Process exited with status 137
2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO WEBrick 1.3.1
2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO ruby 1.9.2 (2011-07-09) [x86_64-linux]
2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO WEBrick::HTTPServer#start: pid=1 port=4160
2012-03-19T18:23:05+
I hope you don't mind but I took the liberty of going to your site myself to see what the problem is. The issue is that you're configuring to use the asset pipeline but none of your assets are compiled. You can verify this is the case by visiting your main CSS file -- you'll notice there's nothing at all there.
This is likely because you forgot to include compilation directives at the top of your application.css. See the asset pipeline guide for full details, but I bet you're missing a line like this at the top of your application.css:
*= require_self
*= require_tree .
I had this problem before too, and I think it had something to do with precompiling your css file. Try going into config/environments/production.rb and add this config.assets.precompile += [ "blueprint/*.css" ]. I am assuming you're using the blueprint css file.
I get this error when I acccess my facebook iframe app:
The change you wanted was rejected.
Maybe you tried to change something you didn't have access to.
Heroku logs:
2011-06-05T08:30:41+00:00 app[web.1]: Started POST "/facebook/" for xxxx
03 at 2011-06-05 10:30:41 +0200
2011-06-05T08:30:41+00:00 heroku[router]: POST www.vinderhimlen.dk/facebook/ dyn
o=web.1 queue=0 wait=0ms service=39ms bytes=711
2011-06-05T08:30:41+00:00 app[web.1]:
2011-06-05T08:30:41+00:00 app[web.1]: ActionController::InvalidAuthenticityToken
(ActionController::InvalidAuthenticityToken):
2011-06-05T08:30:41+00:00 app[web.1]:
2011-06-05T08:30:41+00:00 app[web.1]:
2011-06-05T08:30:41+00:00 app[web.1]:
2011-06-05T08:30:45+00:00 heroku[web.1]: Stopping process with SIGTERM
2011-06-05T08:30:45+00:00 app[web.1]: >> Stopping ...
2011-06-05T08:30:45+00:00 heroku[web.1]: Process exited
Iceberg#ICEBERG-PC /c/rails/konkurranceportalen (master)
$
By default, Rails requires a token to be included as a hidden field with every POST.
This protects your app from Cross-Site Request Forgery.
See the Rails Request Forgery Protection documentation.
skip_before_filter :verify_authenticity_token may be useful for further debugging.