I'm getting "We're sorry, but something went wrong."
heroku logs turns up nothing useful from what I can see...
2014-10-06T20:48:04.846089+00:00 heroku[web.1]: State changed from up to starting
2014-10-06T20:48:06.519972+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2014-10-06T20:48:07.928530+00:00 app[web.1]: => Booting Thin
2014-10-06T20:48:07.928582+00:00 app[web.1]: => Rails 4.1.5 application starting in production on http://0.0.0.0:58305
2014-10-06T20:48:07.928584+00:00 app[web.1]: => Run `rails server -h` for more startup options
2014-10-06T20:48:07.928586+00:00 app[web.1]: => Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (--binding option)
2014-10-06T20:48:07.928587+00:00 app[web.1]: => Ctrl-C to shutdown server
2014-10-06T20:48:07.928589+00:00 app[web.1]: Thin web server (v1.6.2 codename Doc Brown)
2014-10-06T20:48:07.928590+00:00 app[web.1]: Maximum connections set to 1024
2014-10-06T20:48:07.928592+00:00 app[web.1]: Listening on 0.0.0.0:58305, CTRL+C to stop
2014-10-06T20:48:07.928593+00:00 app[web.1]: Exiting
2014-10-06T20:48:07.812908+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 49372 -e production`
2014-10-06T20:48:08.659411+00:00 heroku[web.1]: Process exited with status 0
2014-10-06T20:48:11.589427+00:00 heroku[web.1]: State changed from starting to up
Things work fine locally.
Looks like the following got rid of the issue (i thought db migration would happen automatically)
heroku rake db:migrate
Related
I need help...
I'm using heroku to deploy my golang app... but it seems my Procfile is not in the right format... here is the Procfile:
web: app-crm
everytime I deploy the app, it says succeeded but then after I access my endpoint, my app crashed with this message:
2021-11-15T08:00:49.813561+00:00 heroku[web.1]: State changed from crashed to starting
2021-11-15T08:00:50.113738+00:00 heroku[web.1]: Starting process with command `app-crm`
2021-11-15T08:00:51.791188+00:00 app[web.1]: bash: app-crm: command not found
2021-11-15T08:00:51.920794+00:00 heroku[web.1]: Process exited with status 127
2021-11-15T08:00:51.998349+00:00 heroku[web.1]: State changed from starting to crashed
2021-11-15T08:00:52.006946+00:00 heroku[web.1]: State changed from crashed to starting
2021-11-15T08:00:52.312734+00:00 heroku[web.1]: Starting process with command `app-crm`
2021-11-15T08:00:53.169065+00:00 app[web.1]: bash: app-crm: command not found
2021-11-15T08:00:53.278936+00:00 heroku[web.1]: Process exited with status 127
2021-11-15T08:00:53.342179+00:00 heroku[web.1]: State changed from starting to crashed
I tried to change how to access the port several times too, but it still doesn't work...
is there anyway I could fix it?
I'm trying to deploy a Nuxt SPA app to Heroku.
Locally everything works fine, but when I deploy to Heroku it gives me an application error with the info to check my heroku logs:
2019-10-11T02:49:50.897584+00:00 heroku[web.1]: State changed from crashed to starting
2019-10-11T02:49:54.670233+00:00 heroku[web.1]: Starting process with command `npm start`
2019-10-11T02:49:56.590749+00:00 app[web.1]:
2019-10-11T02:49:56.590769+00:00 app[web.1]: > sol37.web#1.0.0 start /app
2019-10-11T02:49:56.59077+00:00 app[web.1]: > nuxt start
2019-10-11T02:49:56.590772+00:00 app[web.1]:
2019-10-11T02:49:57.167804+00:00 app[web.1]: ℹ Listening on: http://localhost:49791/ 2019-10-11T02:50:02.00478+00:00 heroku[web.1]: source=web.1 dyno=heroku.149207054.9b940788-6a37-40a9-82de-b19b3519e60c sample#memory_total=55.14MB sample#memory_rss=55.14MB sample#memory_cache=0.00MB sample#memory_swap=0.00MB sample#memory_pgpgin=14487pages sample#memory_pgpgout=1392pages sample#memory_quota=512.00MB
2019-10-11T02:50:23.81059+00:00 heroku[web.1]: source=web.1 dyno=heroku.149207054.9b940788-6a37-40a9-82de-b19b3519e60c sample#memory_total=55.14MB sample#memory_rss=55.14MB sample#memory_cache=0.00MB sample#memory_swap=0.00MB sample#memory_pgpgin=14487pages sample#memory_pgpgout=1392pages sample#memory_quota=512.00MB
2019-10-11T02:50:45.744385+00:00 heroku[web.1]: source=web.1 dyno=heroku.149207054.9b940788-6a37-40a9-82de-b19b3519e60c sample#load_avg_1m=0.00
2019-10-11T02:50:45.762243+00:00 heroku[web.1]: source=web.1 dyno=heroku.149207054.9b940788-6a37-40a9-82de-b19b3519e60c sample#memory_total=55.14MB sample#memory_rss=55.14MB sample#memory_cache=0.00MB sample#memory_swap=0.00MB sample#memory_pgpgin=14487pages sample#memory_pgpgout=1392pages sample#memory_quota=512.00MB
2019-10-11T02:50:54.906637+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
I checked if I set the port somewhere manually, but I'm not doing that anywhere in the project.
Without more information, i tried to build the app on heroku directly.
("heroku run bash" and "npm run build") which gave me the following error.
ERROR in ./pages/index.vue
Module not found: Error: Can't resolve 'sass-loader' in '/app'
and 7 more of those errors all concerning sass-loader.
not sure if "npm run build" works over heroku bash, but at least it gave me some information.
I have another nuxt project that i run on the same heroku instance which works without a problem.
I tried to check what the differences are and i found that it used a lower sass-loader version, which i downgraded on my current project but it's still not working.
After that I tried to run "npm run start" which is what Heroku runs upon deployment. this gave me first an error with nuxtjs/style-ressource, which i realized i don't utilize right now, so i removed that. After that it ran without any issues, but i couldn't get it to show up in the browser.
Does anyone have any idea what else I could try?
Thanks in Advance
Carlo
I followed heroku's instructions on deploying a Sinatra application carefully but something is still going wrong. I am using sinatra-base and sinatra-partial if that makes any difference. I have all the gems declared in the gemfile and myapp.rb
Gist of my files
This is what I see on heroku logs
2013-06-11T05:09:28.982664+00:00 app[web.1]: from myapp.rb:49:in `<class:MyApp>'
2013-06-11T05:09:29.148291+00:00 app[web.1]: [2013-06-11 05:09:29] INFO WEBrick 1.3.1
2013-06-11T05:09:29.148613+00:00 app[web.1]: == Sinatra/1.4.0 has taken the stage on 4567 for production with backup from WEBrick
2013-06-11T05:09:29.148759+00:00 app[web.1]: [2013-06-11 05:09:29] INFO WEBrick::HTTPServer#start: pid=2 port=4567
2013-06-11T05:09:29.148291+00:00 app[web.1]: [2013-06-11 05:09:29] INFO ruby 1.9.2 (2011-07-09) [x86_64-linux]
2013-06-11T05:10:26.570140+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2013-06-11T05:10:26.570414+00:00 heroku[web.1]: Stopping process with SIGKILL
2013-06-11T05:10:28.018692+00:00 heroku[web.1]: Process exited with status 137
2013-06-11T05:10:28.033080+00:00 heroku[web.1]: State changed from starting to crashed
After doing a bit more research on the Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch error, it may be because of gems taking a long time to load. However, I am only using these gems so I don't know why it's timing out. Locally, it takes about 1 second to start up my application.
Heroku dynamically assigns the port. You are starting the app on port 4567 when you call the run! method in lines 85-97 of myapp.rb. You should be able to remove those three lines and use config.ru to start your app.
It you add the heroku gem to your Gemfile, you can remove the Procfile. Otherwise you should cahnge it start the app via backup:
web: bundle exec rackup config.ru -p $PORT
You could also add 'thin' to your Gemfile and use a Procfile like this
web: bundle exec thin start -R config.ru -e $RACK_ENV -p $PORT
I am trying to load a simple ruby app on heroku that periodically runs a background task using resque, which checks an email account. It works fine locally with foreman, but keeps crashing on heroku.
I think maybe the Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch comes from my while loop, which is perpetual and therefore longer than 60 seconds? Should I be using some different kind of process to launch smsnotify.rb?
Any help would be extremely appreciated!
My heroku logs:
2013-04-06T20:49:15+00:00 heroku[slugc]: Slug compilation finished
2013-04-06T20:49:18+00:00 heroku[web.1]: Starting process with command `bundle exec ruby smsnotify.rb -p 9129`
2013-04-06T20:49:21+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/activesupport-3.0.0/lib/active_support/multibyte.rb:26: warning: already initialized constant VALID_CHARACTER
2013-04-06T20:50:19+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2013-04-06T20:50:19+00:00 heroku[web.1]: Stopping process with SIGKILL
2013-04-06T20:50:20+00:00 heroku[web.1]: Process exited with status 137
2013-04-06T20:50:20+00:00 heroku[web.1]: State changed from starting to crashed
My Procfile:
web: bundle exec ruby smsnotify.rb -p $PORT
resque: env TERM_CHILD=1 bundle exec rake jobs:work
smsnotify.rb:
require "./email_checker"
require 'hirefire'
require 'resque'
Resque.redis = 'redis://redistogo:removed:removed/'
HireFire::Initializer.initialize!
while true do
Resque.enqueue(EmailChecker)
sleep 30
puts "Starting Email Job"
end
You aren't starting up a process that is binding to a port, so it is complaining.
You just need to change your Procfile to say 'worker' instead of 'web'
If you have a web frontend to this, then you will need a worker and a web
Git was deployed data to Heroku. I restart heroku and found log error as below.
$heroku restart
2013-01-25T08:17:27+00:00 heroku[web.1]: State changed from crashed to
starting 2013-01-25T08:17:30+00:00 heroku[web.1]: Starting process
with command jekyll --server 27519 2013-01-25T08:17:30+00:00
app[web.1]: /usr/bin/env: ruby1.9.1: No such file or directory
2013-01-25T08:17:32+00:00 heroku[web.1]: Process exited with status
127 2013-01-25T08:17:32+00:00 heroku[web.1]: State changed from
starting to crashed 2013-01-25T08:28:01+00:00 heroku[web.1]: State
changed from crashed to starting
Suggest improved jkyell file by #jordelver. Open file jkyell at project_jkyell/bin/ changed version number on line from
#!/usr/bin/env ruby1.9.1
to
#!/usr/bin/env ruby