gpt4 book ai didi

node.js - Heroku node.js 应用程序在 heroku 打开时崩溃

转载 作者:可可西里 更新时间:2023-11-01 11:21:04 25 4
gpt4 key购买 nike

在我尝试“heroku open”之前,我一直在关注 Heroku 上的“node.js 入门”教程,没有任何问题。 heroku 日志如下:

2015-09-06T01:40:57.721184+00:00 heroku[web.1]: State changed from crashed to starting
2015-09-06T01:41:03.369114+00:00 heroku[web.1]: Starting process with command `npm start`
2015-09-06T01:41:06.941642+00:00 app[web.1]:
2015-09-06T01:41:06.941663+00:00 app[web.1]: > my-site@1.0.0 start /app
2015-09-06T01:41:06.941665+00:00 app[web.1]: > node server.js
2015-09-06T01:41:06.941666+00:00 app[web.1]:
2015-09-06T01:41:12.745724+00:00 app[web.1]: events.js:85
2015-09-06T01:41:12.745730+00:00 app[web.1]: throw er; // Unhandled 'error' event
2015-09-06T01:41:12.745731+00:00 app[web.1]: ^
2015-09-06T01:41:12.745733+00:00 app[web.1]: Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED
2015-09-06T01:41:12.745734+00:00 app[web.1]: at RedisClient.on_error (/app/node_modules/redis/index.js:185:24)
2015-09-06T01:41:12.745735+00:00 app[web.1]: at Socket.<anonymous> (/app/node_modules/redis/index.js:95:14)
2015-09-06T01:41:12.745736+00:00 app[web.1]: at Socket.emit (events.js:107:17)
2015-09-06T01:41:12.745737+00:00 app[web.1]: at net.js:459:14
2015-09-06T01:41:12.745739+00:00 app[web.1]: at process._tickCallback (node.js:355:11)
2015-09-06T01:41:12.789099+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2015-09-06T01:41:12.782590+00:00 app[web.1]:
2015-09-06T01:41:12.789353+00:00 app[web.1]: npm ERR! node v0.12.7
2015-09-06T01:41:12.790048+00:00 app[web.1]: npm ERR! npm v2.11.3
2015-09-06T01:41:12.790211+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2015-09-06T01:41:12.790403+00:00 app[web.1]: npm ERR! my-site@1.0.0 start: `node server.js`
2015-09-06T01:41:12.790668+00:00 app[web.1]: npm ERR!
2015-09-06T01:41:12.790523+00:00 app[web.1]: npm ERR! Exit status 1
2015-09-06T01:41:12.790800+00:00 app[web.1]: npm ERR! Failed at the my-site@1.0.0 start script 'node server.js'.
2015-09-06T01:41:12.791028+00:00 app[web.1]: npm ERR! This is most likely a problem with the my-site package,
2015-09-06T01:41:12.791621+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2015-09-06T01:41:12.791492+00:00 app[web.1]: npm ERR! not with npm itself.
2015-09-06T01:41:12.791865+00:00 app[web.1]: npm ERR! You can get their info via:
2015-09-06T01:41:12.791747+00:00 app[web.1]: npm ERR! node server.js
2015-09-06T01:41:12.791990+00:00 app[web.1]: npm ERR! npm owner ls my-site
2015-09-06T01:41:12.792118+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2015-09-06T01:41:12.739572+00:00 app[web.1]: Listening on localhost: 6596
2015-09-06T01:41:12.794869+00:00 app[web.1]:
2015-09-06T01:41:12.788632+00:00 app[web.1]: npm ERR! Linux 3.13.0-61-generic
2015-09-06T01:41:12.795086+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2015-09-06T01:41:12.795203+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2015-09-06T01:41:14.558203+00:00 heroku[web.1]: State changed from starting to crashed
2015-09-06T01:41:14.544183+00:00 heroku[web.1]: Process exited with status 1
2015-09-06T01:41:39+00:00 app[heroku-redis]: source=REDIS sample#active-connections=1 sample#load-avg-1m=0.065 sample#load-avg-5m=0.055 sample#load-avg-15m=0.045 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15405664kB sample#memory-free=14101096kB sample#memory-cached=514208kB sample#memory-redis=294000bytes
2015-09-06T01:42:20+00:00 app[heroku-redis]: source=REDIS sample#active-connections=1 sample#load-avg-1m=0.085 sample#load-avg-5m=0.06 sample#load-avg-15m=0.05 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15405664kB sample#memory-free=14101344kB sample#memory-cached=514208kB sample#memory-redis=294000bytes
2015-09-06T01:43:43+00:00 app[heroku-redis]: source=REDIS sample#active-connections=1 sample#load-avg-1m=0.05 sample#load-avg-5m=0.06 sample#load-avg-15m=0.045 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15405664kB sample#memory-free=14101108kB sample#memory-cached=514208kB sample#memory-redis=294000bytes
2015-09-06T01:44:27+00:00 app[heroku-redis]: source=REDIS sample#active-connections=1 sample#load-avg-1m=0.02 sample#load-avg-5m=0.05 sample#load-avg-15m=0.045 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15405664kB sample#memory-free=14101176kB sample#memory-cached=514212kB sample#memory-redis=294000bytes
2015-09-06T01:45:46+00:00 app[heroku-redis]: source=REDIS sample#active-connections=1 sample#load-avg-1m=0.005 sample#load-avg-5m=0.04 sample#load-avg-15m=0.04 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15405664kB sample#memory-free=14101240kB sample#memory-cached=514212kB sample#memory-redis=294000bytes
2015-09-06T01:46:24+00:00 app[heroku-redis]: source=REDIS sample#active-connections=1 sample#load-avg-1m=0.035 sample#load-avg-5m=0.04 sample#load-avg-15m=0.04 sample#read-iops=0 sample#write-iops=0 sample#memory-total=15405664kB sample#memory-free=14100784kB sample#memory-cached=514212kB sample#memory-redis=294000bytes

问题出在我没有经验的 Redis 上。

Redis Heroku 作为插件安装,在我的本地机器上运行 npm start 时一切正常。

有没有人以前遇到过这个或有任何想法?

最佳答案

您可能有一个本地运行的 Redis 服务器,但是您的 Heroku 实例无法连接到您的本地 Redis 实例,如果您在 Heroku 运行中使用相同的配置,它会寻找一些东西在同一个端点上(我猜是 127.0.0.1 端口 3000 之类的)。

https://devcenter.heroku.com/articles/heroku-redis

在 Redis-to-Go 上,您可以获得可以测试的免费/纳米计划。 http://redistogo.com/只需连接远程即可。这是通过 Heroku 进行配置的替代方法,我想我在几个月前验证了该方法的有效性。它仍然应该。

您可以使用 ~~foreman start~~ now heroku local 在更接近部署环境的条件下在本地测试 Heroku 应用程序 https://devcenter.heroku.com/articles/heroku-local ,并在 process 上查看 https://devcenter.heroku.com/articles/procfile

关于node.js - Heroku node.js 应用程序在 heroku 打开时崩溃,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/32419526/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com