Heroku上部署的应用程序在启动时崩溃[重复]

【问题标题】：Deployed app on Heroku crashed at startup [duplicate]Heroku上部署的应用程序在启动时崩溃[重复]
【发布时间】：2022-01-14 21:18:01
【问题描述】：

如果我从终端运行应用程序，它正在工作，我的意思是它正在浏览器中运行。 问题是当我尝试在 Heroku 上托管它时。我的应用程序有后端：带有 Express 的 Nodejs 和数据库：MySQL。 我看到我有错误，但我不理解它们，并且我尝试了多种方法来使其工作，但我做不到。 错误日志：

2022-01-14T11:42:19.516824+00:00 app[web.1]: 
2022-01-14T11:42:19.516835+00:00 app[web.1]: > presidentialelections@0.0.0 start /app
2022-01-14T11:42:19.516835+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:42:19.516835+00:00 app[web.1]: 
2022-01-14T11:42:19.520231+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:42:19.524055+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:42:19.524197+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:42:19.524258+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:42:19.524466+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:42:19.526613+00:00 app[web.1]: npm ERR! presidentialelections@0.0.0 start: `nodemon ./bin/www` 
2022-01-14T11:42:19.526650+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:42:19.526699+00:00 app[web.1]: npm ERR!
2022-01-14T11:42:19.526737+00:00 app[web.1]: npm ERR! Failed at the presidentialelections@0.0.0 start script.2022-01-14T11:42:19.526788+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:42:19.532863+00:00 app[web.1]:
2022-01-14T11:42:19.532933+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:42:19.532983+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2022-01-14T11_42_19_527Z-debug.log 
2022-01-14T11:42:19.647800+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:42:19.723822+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:42:22.997860+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=867758f1-1252-4674-a7cc-261fbe9f98d1 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:42:23.312967+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=5cb55772-dad6-486d-bc15-d37731d94661 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:46:57.000000+00:00 app[api]: Build started by user daviddserb@yahoo.com
2022-01-14T11:47:11.000000+00:00 app[api]: Build succeeded
2022-01-14T11:47:11.297457+00:00 app[api]: Deploy 7ee73460 by user daviddserb@yahoo.com
2022-01-14T11:47:11.297457+00:00 app[api]: Release v4 created by user daviddserb@yahoo.com
2022-01-14T11:47:12.210235+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T11:47:14.084097+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T11:47:15.244156+00:00 app[web.1]:
2022-01-14T11:47:15.244170+00:00 app[web.1]: > presidentialelections@0.0.0 start /app
2022-01-14T11:47:15.244170+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:47:15.244170+00:00 app[web.1]:
2022-01-14T11:47:15.248738+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:47:15.254959+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:47:15.255206+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:47:15.255316+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:47:15.255405+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:47:15.259050+00:00 app[web.1]: npm ERR! presidentialelections@0.0.0 start: `nodemon ./bin/www` 
2022-01-14T11:47:15.259107+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:47:15.259167+00:00 app[web.1]: npm ERR!
2022-01-14T11:47:15.259216+00:00 app[web.1]: npm ERR! Failed at the presidentialelections@0.0.0 start script.2022-01-14T11:47:15.259274+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:47:15.266461+00:00 app[web.1]:
2022-01-14T11:47:15.266545+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:47:15.266590+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2022-01-14T11_47_15_260Z-debug.log 
2022-01-14T11:47:15.397039+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:47:15.454442+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:47:18.779406+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=325e420b-9e58-4f7e-bad0-4872dc699fe0 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:47:19.023207+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=e081eb63-0cff-4e27-a710-1d60cbc9beb1 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:48:40.000000+00:00 app[api]: Build started by user daviddserb@yahoo.com
2022-01-14T11:48:53.770119+00:00 app[api]: Deploy 7fc9ef13 by user daviddserb@yahoo.com
2022-01-14T11:48:53.770119+00:00 app[api]: Release v5 created by user daviddserb@yahoo.com
2022-01-14T11:48:54.000000+00:00 app[api]: Build succeeded
2022-01-14T11:48:54.117745+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T11:48:55.999691+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T11:48:56.952415+00:00 app[web.1]:
2022-01-14T11:48:56.952427+00:00 app[web.1]: > presidentialelections@0.0.0 start /app
2022-01-14T11:48:56.952428+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T11:48:56.952428+00:00 app[web.1]:
2022-01-14T11:48:56.962683+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T11:48:56.968511+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T11:48:56.968735+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T11:48:56.968786+00:00 app[web.1]: npm ERR! file sh
2022-01-14T11:48:56.968886+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T11:48:56.972412+00:00 app[web.1]: npm ERR! presidentialelections@0.0.0 start: `nodemon ./bin/www` 
2022-01-14T11:48:56.972521+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T11:48:56.972620+00:00 app[web.1]: npm ERR!
2022-01-14T11:48:56.972734+00:00 app[web.1]: npm ERR! Failed at the presidentialelections@0.0.0 start script.2022-01-14T11:48:56.972822+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-01-14T11:48:56.977729+00:00 app[web.1]:
2022-01-14T11:48:56.977829+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T11:48:56.977880+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2022-01-14T11_48_56_974Z-debug.log 
2022-01-14T11:48:57.123929+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T11:48:57.256711+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-14T11:49:03.042405+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=40e7bba7-b78d-4472-b652-c1b296a4343a fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:49:03.312210+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=4b214bf1-4d44-4895-8bc7-2d8cc34e172d fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:51:59.531549+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=c38f2d45-f1a5-43a9-9f4e-e2f34ef4d1bb fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:51:59.801198+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=a5c7fb1c-5ce3-4ccf-81ac-3cb8fdce759f fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:56:02.383069+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-ravine-23602.herokuapp.com request_id=22db8c3d-1714-42f8-a40f-9e02d0cc737a fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T11:56:02.634499+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=pacific-ravine-23602.herokuapp.com request_id=fc256052-006a-4289-a836-ce8094e64944 fwd="86.120.247.90" dyno= connect= service= status=503 bytes= protocol=https
2022-01-14T12:05:20.233183+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-14T12:05:22.754848+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-14T12:05:23.970064+00:00 app[web.1]:
2022-01-14T12:05:23.970078+00:00 app[web.1]: > presidentialelections@0.0.0 start /app
2022-01-14T12:05:23.970079+00:00 app[web.1]: > nodemon ./bin/www
2022-01-14T12:05:23.970079+00:00 app[web.1]:
2022-01-14T12:05:23.973595+00:00 app[web.1]: sh: 1: nodemon: not found
2022-01-14T12:05:23.978419+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-14T12:05:23.978592+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-14T12:05:23.978667+00:00 app[web.1]: npm ERR! file sh
2022-01-14T12:05:23.978764+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-14T12:05:23.981475+00:00 app[web.1]: npm ERR! presidentialelections@0.0.0 start: `nodemon ./bin/www`
2022-01-14T12:05:23.981519+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-14T12:05:23.981564+00:00 app[web.1]: npm ERR!
2022-01-14T12:05:23.982264+00:00 app[web.1]: npm ERR! Failed at the presidentialelections@0.0.0 start script.2022-01-14T12:05:23.982320+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There 
is likely additional logging output above.
2022-01-14T12:05:23.984901+00:00 app[web.1]:
2022-01-14T12:05:23.984998+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-14T12:05:23.985048+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2022-01-14T12_05_23_982Z-debug.log
2022-01-14T12:05:24.128019+00:00 heroku[web.1]: Process exited with status 1
2022-01-14T12:05:24.211507+00:00 heroku[web.1]: State changed from starting to crashed

I don't know what else to give you, so please, if you need some other files or information about my project, let me know and I will upload them.

【问题讨论】：

  • 这能回答你的问题吗？ Heroku failing node app - try to run nodemon instead of node
  • TL;DR：这（可能）失败，因为您已将 nodemon 定义为 dev 依赖项，并且默认情况下从 Heroku 构建中删除了 dev 依赖项。但这很好！首先，您不应该在 Heroku 上使用 nodemon。确保您的 start 脚本或 Procfile 运行 node 而不是 nodemon。
  • 是的，我也已经尝试过了。我又试了一次，所以在我的启动脚本中，我没有 nodemon 了，我有： node ./bin/www 但它仍然无法正常工作。我是否必须像 node_modules 和 package.json 一样重新安装？我问是因为它仍然说完全相同的东西，找不到 nodemon，即使我不再使用它了......
  • 你有Procfile吗？如果存在，它将优先于您的 start 脚本。
  • 我也尝试过 Procfile，但仍然是同样的错误。无论如何，现在我又从底层做了我的项目，现在我不再使用 nodemon 了。我没有 nodemon 错误，但现在我有一个新错误：“警告：connect.session() MemoryStore 不是为生产环境设计的，因为它会泄漏内存，并且不会扩展到单个进程。” .无论如何，感谢您的时间和您的回答，我现在会尝试为新错误寻求帮助...

标签： node.js heroku


【解决方案1】：

似乎您正在使用“nodemon”。可能如果您使用“npm i -g nodemon”安装 你可以看到那个错误。所以你的电脑上安装了nodemon，但你的项目没有nodemon。只需在定位项目时在终端中运行npm i nodemon。最后再次部署。我很抱歉英语不好。

【讨论】：

  • “在你的终端中运行npm i nodemon，同时找到项目”——由于 Heroku 的临时文件系统，这在 Heroku 上不起作用。所有依赖项必须在构建时安装。
猜你喜欢
  • 2020-11-08
  • 2016-12-14
  • 2019-05-03
  • 2011-09-23
  • 1970-01-01
  • 2015-10-11
  • 2021-04-09
  • 2018-02-11
相关资源
最近更新 更多
热门标签
Java Python linux javascript Mysql C# Docker 算法 前端 SpringBoot Redis Vue spring 设计模式 .net core .net kubernetes c++ 数据库 数据结构 大数据 js 机器学习 微服务 Android Go 程序员 面试 JVM ASP.net core 云原生 人工智能 后端 PHP git CSS golang k8s Nginx Django mybatis 深度学习 多线程 React 架构 devops 爬虫 云计算 Spring Boot LeetCode