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?
Related
I am developing node.js app on heroku. For now it runs on single (free) dyno.
For some reason suddenly my app crashed and now it crashes all the time (I observed it after adding NewRelic and Librato addons - app is kind of restarted when adding those addons) - app crashed for the first time after one of those addons were added. So I removed both addons but problem still remained. I wanted to check whats wrong and I commented my app code and replaced it with simple example from the web:
index.js
var http = require('http');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello World\n');
}).listen(process.env.PORT);
console.log('Server running at http://127.0.0.1:1337/');
Procfile
web: node index.js
engines in packages.json (node installed by heroku is 0.10.26)
"engines": {
"node": "0.10.x"
},
This code works on my pc (tested with foreman).
When I try to deploy it to heroku app crashes - here is the log:
2014-04-25T09:43:42+00:00 heroku[slug-compiler]: Slug compilation started
2014-04-25T09:43:47.850609+00:00 heroku[api]: Release v30 created by xxx
2014-04-25T09:43:47.850538+00:00 heroku[api]: Deploy 562babb by xxx
2014-04-25T09:43:47+00:00 heroku[slug-compiler]: Slug compilation finished
2014-04-25T09:43:48.588089+00:00 heroku[web.1]: State changed from crashed to starting
2014-04-25T09:43:55.655057+00:00 heroku[web.1]: Starting process with command `node index.js`
2014-04-25T09:43:57.931274+00:00 heroku[web.1]: Process exited with status 8
2014-04-25T09:43:57.945393+00:00 heroku[web.1]: State changed from starting to crashed
when I try to heroku restart:
2014-04-25T09:44:43.071357+00:00 heroku[web.1]: State changed from crashed to starting
2014-04-25T09:44:51.834860+00:00 heroku[web.1]: Starting process with command `node index.js`
2014-04-25T09:44:54.250631+00:00 heroku[web.1]: State changed from starting to crashed
2014-04-25T09:44:54.235545+00:00 heroku[web.1]: Process exited with status 8
This make me crazy - I deployed many node apps to heroku which are runing in production and had never such problems - whats going on???
When I changed node engine version to 0.10.20 (I am using this v localy) then app started and was working but when I did heroku restart it crashed again...
State changed from up to starting
2014-04-25T10:10:12.990317+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2014-04-25T10:10:15.145758+00:00 heroku[web.1]: Process exited with status 143
2014-04-25T10:10:16.151380+00:00 heroku[web.1]: Starting process with command `node index.js`
2014-04-25T10:10:18.905637+00:00 heroku[web.1]: Process exited with status 8
2014-04-25T10:10:18.929730+00:00 heroku[web.1]: State changed from starting to crashed
after second restart app was up and runing again, and after third restart it crashed again (it always crashes/exits with status 8).
The problem could be on Heroku itself. There was an incident report created about an hour ago but it is still unclear what is causing the problem:
https://status.heroku.com/incidents/614
Meanwhile, you might want to rollback to the previous working build of your app via HerokuDashboard.
add this config to package.json:
"scripts": {
"start": "node index.js"},
index.js is name of of file you want to start you app from here like www.js or server.js
www.piero.ir/en
I think i am having a problem in my Procfile. The deploy is compiled successfully but the app does not start with this message --
2014-03-27T14:17:06.465302+00:00 heroku[api]: Deploy ea0e14d by xxxx#gmail.com
2014-03-27T14:17:06.465378+00:00 heroku[api]: Release v10 created by xxxx#gmail.com
2014-03-27T14:17:14.091032+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/enigmatic-dusk-7498 -Dhttp.port=32253`
2014-03-27T14:17:15.199466+00:00 app[web.1]: bash: target/universal/stage/bin/enigmatic-dusk-7498: No such file or directory
2014-03-27T14:17:16.511169+00:00 heroku[web.1]: Process exited with status 127
2014-03-27T14:17:16.521177+00:00 heroku[web.1]: State changed from starting to crashed
The procfile reads:
web: target/universal/stage/bin/enigmatic-dusk-7498 -Dhttp.port=$PORT
which i guess is the standard for play 2.2 onwards.
What is wrong? enigmatic dusk is the name given by heroku to my app. my local name is different.
EDIT:
As per some suggestions i tried changing the procfile to my local app-name.
New Procfile -
web: target/universal/stage/bin/ExampleBootStrap -Dhttp.port=$PORT
Still it fails.
2014-03-27T17:58:12.527528+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/ExampleBootStrap -Dhttp.port=38392`
2014-03-27T17:58:13.948429+00:00 app[web.1]: bash: target/universal/stage/bin/ExampleBootStrap: No such file or directory
2014-03-27T17:58:15.608461+00:00 heroku[web.1]: Process exited with status 127
2014-03-27T17:58:15.621947+00:00 heroku[web.1]: State changed from crashed to starting
2014-03-27T17:58:15.620997+00:00 heroku[web.1]: State changed from starting to crashed
2014-03-27T17:58:27.265083+00:00 heroku[web.1]: State changed from starting to crashed
2014-03-27T17:58:24.366648+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/ExampleBootStrap -Dhttp.port=33223`
2014-03-27T17:58:25.666535+00:00 app[web.1]: bash: target/universal/stage/bin/ExampleBootStrap: No such file or directory
2014-03-27T17:58:27.250296+00:00 heroku[web.1]: Process exited with status 127
In your procfile, you must replace enigmatic-dusk-7498 with the name of your play project in lower case letters, not you heroku app.
I updated my rails app on heroku with push, but when I used the command heroku open my command prompt read
no such file or directory .heroku/client/vendor/gems/addressable-2.3.2/data/unicode.data(Errno::ENOENT)
not sure what is going on. I did heroko logs and I got a long list of some weird feedback that I don't understand. Anyway hope this is all helpful. Does anyone know what's going on?
here is my heroku logs
2013-08-26T23:29:23+00:00 heroku[slug-compiler]: Slug compilation started
2013-08-26T23:30:40.856501+00:00 heroku[api]: Scale to web=1 by lanners.marshall
#yahoo.com
2013-08-26T23:30:41.479196+00:00 heroku[api]: Attach HEROKU_POSTGRESQL_GOLD reso
urce by lanners.marshall#yahoo.com
2013-08-26T23:30:41.517670+00:00 heroku[api]: Release v3 created by lanners.mars
hall#yahoo.com
2013-08-26T23:30:41.596604+00:00 heroku[api]: Add DATABASE_URL config by lanners
.marshall#yahoo.com
2013-08-26T23:30:41.622576+00:00 heroku[api]: Release v4 created by lanners.mars
hall#yahoo.com
2013-08-26T23:30:41.670403+00:00 heroku[api]: Deploy 6bdd211 by lanners.marshall
#yahoo.com
2013-08-26T23:30:41.698072+00:00 heroku[api]: Release v5 created by lanners.mars
hall#yahoo.com
2013-08-26T23:30:45.518833+00:00 heroku[web.1]: Starting process with command `b
in/rails server -p 39588 -e $RAILS_ENV`
2013-08-26T23:30:46.148345+00:00 app[web.1]: /usr/bin/env: ruby.exe: No such fil
e or directory
2013-08-26T23:30:47.474136+00:00 heroku[web.1]: Process exited with status 127
2013-08-26T23:30:47.484121+00:00 heroku[web.1]: State changed from starting to c
rashed
2013-08-26T23:30:47.484721+00:00 heroku[web.1]: State changed from crashed to st
arting
2013-08-26T23:30:51.551472+00:00 heroku[web.1]: Starting process with command `b
in/rails server -p 43747 -e $RAILS_ENV`
2013-08-26T23:30:53.341195+00:00 app[web.1]: /usr/bin/env: ruby.exe: No such fil
e or directory
2013-08-26T23:30:55.337892+00:00 heroku[web.1]: Process exited with status 127
2013-08-26T23:30:55.329904+00:00 heroku[web.1]: State changed from starting to c
rashed
2013-08-26T23:41:15.238982+00:00 heroku[web.1]: State changed from crashed to st
arting
2013-08-26T23:41:18.948180+00:00 heroku[web.1]: Starting process with command `b
in/rails server -p 28272 -e $RAILS_ENV`
2013-08-26T23:41:19.673459+00:00 app[web.1]: /usr/bin/env: ruby.exe: No such fil
e or directory
2013-08-26T23:41:21.166624+00:00 heroku[web.1]: State changed from starting to c
rashed
2013-08-26T23:41:21.182154+00:00 heroku[web.1]: Process exited with status 127
2013-08-26T23:41:29.185339+00:00 heroku[web.1]: Stopping process with SIGKILL
2013-08-26T23:41:29.185135+00:00 heroku[web.1]: Error R99 (Platform error) -> Fa
iled to launch the dyno within 10 seconds
2013-08-26T23:51:49.427744+00:00 heroku[web.1]: State changed from crashed to st
arting
2013-08-26T23:51:52.685493+00:00 heroku[web.1]: Starting process with command `b
in/rails server -p 24715 -e $RAILS_ENV`
2013-08-26T23:51:53.320123+00:00 app[web.1]: /usr/bin/env: ruby.exe: No such fil
e or directory
2013-08-26T23:51:54.877945+00:00 heroku[web.1]: Process exited with status 127
2013-08-26T23:51:54.895579+00:00 heroku[web.1]: State changed from starting to c
rashed
2013-08-27T00:02:12.823833+00:00 heroku[web.1]: State changed from crashed to st
arting
2013-08-27T00:02:17.454356+00:00 heroku[web.1]: Starting process with command `b
in/rails server -p 35817 -e $RAILS_ENV`
2013-08-27T00:02:18.536931+00:00 app[web.1]: /usr/bin/env: ruby.exe: No such fil
e or directory
2013-08-27T00:02:20.493992+00:00 heroku[web.1]: Process exited with status 127
2013-08-27T00:02:27.748278+00:00 heroku[web.1]: Stopping process with SIGKILL
2013-08-27T00:02:27.748030+00:00 heroku[web.1]: Error R99 (Platform error) -> Fa
iled to launch the dyno within 10 seconds
2013-08-27T00:12:27.719245+00:00 heroku[web.1]: State changed from crashed to st
arting
2013-08-27T00:12:30.128833+00:00 heroku[web.1]: Starting process with command `b
in/rails server -p 51549 -e $RAILS_ENV`
2013-08-27T00:12:31.578894+00:00 heroku[web.1]: State changed from starting to c
rashed
2013-08-27T00:12:31.542115+00:00 heroku[web.1]: Process exited with status 127
2013-08-27T00:12:30.563854+00:00 app[web.1]: /usr/bin/env: ruby.exe: No such fil
e or directory
2013-08-27T00:12:40.521830+00:00 heroku[web.1]: Error R99 (Platform error) -> Fa
iled to launch the dyno within 10 seconds
2013-08-27T00:12:40.522094+00:00 heroku[web.1]: Stopping process with SIGKILL
Read the error log, and do a SO search. The giveaway is the ruby.exe. This is a windows executable name. Heroku runs Linux, where executables don't end in .exe
To fix this, in your procfile, change ruby.exe to ruby. And use unix line endings while we're at it. And then commit your files and re-push. This article has some helpful information on how to let git manage line ending conventions for you.
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
I created a sample app called stock portfolio manager
https://github.com/rohanmoitra/foliomanage and deployed it on heroku. But whenever I try to run heroku rake db:migrate it times out and gives the following error.
2012-10-22T22:28:35+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process
failed to bind to $PORT within 60 seconds of launch
2012-10-22T22:28:35+00:00 heroku[web.1]: Stopping process with SIGKILL
2012-10-22T22:28:36+00:00 heroku[web.1]: Process exited with status 137
2012-10-22T22:28:36+00:00 heroku[web.1]: State changed from starting to crashed
Has anyone encountered this error before? Any help would be deeply appreciated
You shouldn't do migrations on heroku boot. The latter is limited to 60 seconds. Run migrations separately as a rake task. If you really, really want to do this though, you have to work around the boot timeout (https://github.com/dblock/heroku-forward could help).