问题描述
我想我的Procfile中有问题。部署编译成功，但应用程序不会以此消息开始 -
2014-03-27T14：17：06.465302+ 00:00 heroku [api]：由[email protected]部署ea0e14d
2014-03-27T14：17：06.465378 + 00：00 heroku [api]：由[email protected]创建的发布v10
2014-03-27T14：17：14.091032 + 00：00 heroku [web.1]：用命令`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：没有这样的文件或目录
2014-03-27T14 ：17：16.511169 + 00：00 heroku [web.1]：进程已退出，状态为127
2014-03-27T14：17：16.521177 + 00：00 heroku [web.1]：状态从开始更改为崩溃
procfile为：
web：target / universal / stage / bin / enigmatic-dusk-7498 -Dhttp.port = $ PORT
我认为这是2.2以后的标准。
出了什么问题？神秘黄昏是Heroku给我的应用程序命名的名称。我的本地名称不同。
编辑：
根据一些建议，我尝试将procfile更改为本地应用程序名称。
新的Procfile -
web：target / universal / stage / bin / ExampleBootStrap -Dhttp.port = $ PORT
仍然失败。
2014-03-27T17：58：12.527528 + 00：00 heroku [web.1]：用命令`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：没有这样的文件或目录
2014-03-27T17：58：15.608461 + 00：00 heroku [web.1]：进程已退出，状态为127
2014-03-27T17：58：15.621947 + 00：00 heroku [web.1 ]：状态从崩溃转变为开始
2014-03-27T17：58：15.620997 + 00：00 heroku [web.1]：状态从开始变为崩溃
2014-03-27T17：58： 27.265083 + 00：00 heroku [web.1]：状态从开始变为崩溃
2014-03-27T17：58：24.366648 + 00：00 heroku [web.1]：用命令`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：没有这样的文件或目录
2014-03-27T17：58：27.250296 + 00：00 heroku [web.1]：进程退出状态127
在你的proc文件中，你必须使用小写字母 替换名为的神秘黄昏-7498，而不是你的heroku应用。
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 [email protected]
2014-03-27T14:17:06.465378+00:00 heroku[api]: Release v10 created by [email protected]
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.
这篇关于部署到Heroku Play 2.2应用程序时出错的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！