我正在尝试通过cmd提示在问题上显示错误并在日志中显示错误，从而在heroku的railoku应用程序上部署ruby。它正在提供应用程序错误。在命令提示符窗口上执行heroku open时出现应用程序错误。如何解决此错误。我还尝试消除了与localhost：3000上的控制台相关的问题
C:\r5.1>heroku logs --tail
2019-11-11T14:16:38.867063+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-11T14:16:43.692688+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 19801 -e production`
2019-11-11T14:16:46.394640+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-11T14:16:46.381024+00:00 heroku[web.1]: Process exited with status 127
2019-11-11T14:16:46.254086+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-11T20:00:49.460823+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-11T20:00:59.165978+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 29263 -e production`
2019-11-11T20:01:04.157480+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-11T20:01:04.118816+00:00 heroku[web.1]: Process exited with status 127
2019-11-11T20:01:03.964097+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-12T01:38:25.327629+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-12T01:38:29.528475+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 54505 -e production`
2019-11-12T01:38:31.443429+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-12T01:38:31.413452+00:00 heroku[web.1]: Process exited with status 127
2019-11-12T01:38:31.355207+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-12T04:43:24.305277+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=obscure-beyond-78036.herokuapp.com request_id=c969b84f-8226-4b14-a7a7-0dcd2f1a7ecf fwd="73.244.194.180" dyno= connect= service= status=503 bytes= protocol=https
2019-11-12T04:43:24.966438+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=obscure-beyond-78036.herokuapp.com request_id=98e6030c-5a7d-45b8-9463-b20378089873 fwd="73.244.194.180" dyno= connect= service= status=503 bytes= protocol=https
2019-11-12T04:45:44.551206+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=obscure-beyond-78036.herokuapp.com request_id=c38f043e-1c13-4227-a0ee-926e96031e96 fwd="73.244.194.180" dyno= connect= service= status=503 bytes= protocol=https
2019-11-12T04:45:44.724247+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=obscure-beyond-78036.herokuapp.com request_id=ca487a9b-815c-4198-881e-c1536624dcf0 fwd="73.244.194.180" dyno= connect= service= status=503 bytes= protocol=https
2019-11-12T07:14:57.497429+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-12T07:15:01.920946+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 19445 -e production`
2019-11-12T07:15:04.382826+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-12T07:15:04.358062+00:00 heroku[web.1]: Process exited with status 127
2019-11-12T07:15:04.270979+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-12T12:59:29.922938+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-12T12:59:34.199590+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 8495 -e production`
2019-11-12T12:59:36.058436+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-12T12:59:36.011599+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-12T12:59:36.058915+00:00 heroku[web.1]: Process exited with status 127
2019-11-12T18:57:44.195820+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-12T18:57:49.089790+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 55812 -e production`
2019-11-12T18:57:50.902911+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-12T18:57:50.891004+00:00 heroku[web.1]: Process exited with status 127
2019-11-12T18:57:50.829746+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-13T00:18:03.832712+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-13T00:18:11.709422+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 57129 -e production`
2019-11-13T00:18:14.447216+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-13T00:18:14.426285+00:00 heroku[web.1]: Process exited with status 127
2019-11-13T00:18:14.353062+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-13T06:18:16.247724+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-13T06:18:21.126039+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 56369 -e production`
2019-11-13T06:18:23.030770+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-13T06:18:23.010262+00:00 heroku[web.1]: Process exited with status 127
2019-11-13T06:18:22.964777+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-13T11:54:35.587058+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-13T11:54:43.164128+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 23216 -e production`
2019-11-13T11:54:45.221161+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-13T11:54:45.054350+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-13T11:54:45.198218+00:00 heroku[web.1]: Process exited with status 127
2019-11-13T17:32:52.968441+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-13T17:32:57.483433+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 41627 -e production`
2019-11-13T17:32:59.635352+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-13T17:32:59.617603+00:00 heroku[web.1]: Process exited with status 127
2019-11-13T17:32:59.529956+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-13T23:28:20.391491+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-13T23:28:25.383782+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 35541 -e production`
2019-11-13T23:28:26.768967+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-13T23:28:26.746187+00:00 heroku[web.1]: Process exited with status 127
2019-11-13T23:28:26.710575+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-14T05:20:57.113772+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-14T05:21:02.360484+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 39866 -e production`
2019-11-14T05:21:04.955264+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-14T05:21:04.936109+00:00 heroku[web.1]: Process exited with status 127
2019-11-14T05:21:04.867542+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-14T11:13:33.210556+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-14T11:13:37.194569+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 54606 -e production`
2019-11-14T11:13:39.024888+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-14T11:13:39.010502+00:00 heroku[web.1]: Process exited with status 127
2019-11-14T11:13:38.967553+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-14T16:42:11.985194+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-14T16:42:16.369127+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 6489 -e production`
2019-11-14T16:42:18.158327+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-14T16:42:18.141167+00:00 heroku[web.1]: Process exited with status 127
2019-11-14T16:42:18.091900+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-14T22:23:09.123597+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-14T22:23:13.156309+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 41127 -e production`
2019-11-14T22:23:14.623692+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-14T22:23:14.542462+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-14T22:23:14.601341+00:00 heroku[web.1]: Process exited with status 127
2019-11-15T04:07:18.215176+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-15T04:07:24.144091+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 28727 -e production`
2019-11-15T04:07:26.088778+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-15T04:07:26.073282+00:00 heroku[web.1]: Process exited with status 127
2019-11-15T04:07:26.028957+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-15T09:51:30.015825+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-15T09:51:35.432940+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 35443 -e production`
2019-11-15T09:51:38.061514+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-15T09:51:38.042995+00:00 heroku[web.1]: Process exited with status 127
2019-11-15T09:51:37.986622+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-15T15:32:36.641076+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-15T15:32:43.318738+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 50057 -e production`
2019-11-15T15:32:45.191239+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-15T15:32:45.171631+00:00 heroku[web.1]: Process exited with status 127
2019-11-15T15:32:45.136551+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-15T21:09:12.453945+00:00 heroku[web.1]: State changed from crashed to starting
2019-11-15T21:09:17.586328+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 32126 -e production`
2019-11-15T21:09:19.654985+00:00 heroku[web.1]: State changed from starting to crashed
2019-11-15T21:09:19.640167+00:00 heroku[web.1]: Process exited with status 127
2019-11-15T21:09:19.589960+00:00 app[web.1]: /usr/bin/env: ‘ruby\r’: No such file or directory
2019-11-17T02:02:40.834466+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=obscure-beyond-78036.herokuapp.com request_id=27b9775c-9011-4343-b386-bc8575b3b574 fwd="73.244.194.180" dyno= connect= service= status=503 bytes= protocol=https
答案 0 :(得分：0)
我会花钱在您的其中一个文件中有一个不可见的/r上。
查看以下答案：https://stackoverflow.com/a/29074011/1880203
打开./bin/中的每个文件，并确保在每个文件顶部的魔术注释之后没有空格或时髦的字符：
#!/usr/bin/env ruby