2014-07-17 79 views
1

我的应用程序的日志在加载时产生了这组错误,即使NodeBB绑定到端口,Heroku错误,因为它说它无法绑定到端口。任何想法,为什么这是或如果这是有关的设置我有地方?在Heroku上查看NodeBB应用程序时的应用程序错误

Jul 17 05:41:28 fateoftime app/web.1: info: Initializing NodeBB v0.4.3 
Jul 17 05:41:28 fateoftime app/web.1: info: * using configuration stored in: /app/config.json 
Jul 17 05:41:28 fateoftime app/web.1: info: * using redis store at ray.redistogo.com:9748 
Jul 17 05:41:28 fateoftime app/web.1: info: * using themes stored in: /app/node_modules 
Jul 17 05:41:29 fateoftime app/web.1: info: Enabling 'trust proxy' 
Jul 17 05:41:29 fateoftime app/web.1: info: [user.startJobs] Registering User Jobs 
Jul 17 05:41:29 fateoftime app/web.1: info: [sounds] Sounds OK 
Jul 17 05:41:29 fateoftime app/web.1: warn: [plugins/nodebb-plugin-mentions] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. 
Jul 17 05:41:29 fateoftime app/web.1: warn: [plugins/nodebb-plugin-mentions] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-plugin-mentions". 
Jul 17 05:41:29 fateoftime app/web.1: info: [meta/css] Minifying LESS/CSS 
Jul 17 05:41:29 fateoftime app/web.1: info: [themes] Compiling templates 
Jul 17 05:41:29 fateoftime app/web.1: info: NodeBB attempting to listen on: 127.0.0.1:16312 
Jul 17 05:41:29 fateoftime app/web.1: info: [themes] Successfully compiled templates. 
Jul 17 05:41:30 fateoftime app/web.1: info: NodeBB is now listening on: 127.0.0.1:16312 
Jul 17 05:41:30 fateoftime app/web.1: info: NodeBB v0.4.3 Copyright (C) 2013-2014 NodeBB Inc. 
Jul 17 05:41:30 fateoftime app/web.1: info: [meta/css] Done. 
Jul 17 05:41:31 fateoftime heroku/web.1: Starting process with command `node app.js` 
Jul 17 05:41:37 fateoftime app/web.1: info: NodeBB Ready 
Jul 17 05:41:37 fateoftime app/web.1: info: [meta/js] Compilation complete 
Jul 17 05:42:27 fateoftime heroku/web.1: State changed from starting to crashed 
Jul 17 05:42:31 fateoftime heroku/web.1: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch 
Jul 17 05:42:31 fateoftime heroku/web.1: Stopping process with SIGKILL 
Jul 17 05:42:31 fateoftime heroku/web.1: Process exited with status 137 
Jul 17 08:12:48 fateoftime heroku/router: at=error code=H10 desc="App crashed" method=GET path="/" host=www.fateoftime.com request_id=43be8d61-3251-4bb9-b5b1-8eb06092f140 fwd="104.36.225.21" dyno= connect= service= status=503 bytes= 

回答

1

免责声明:我在Heroku的

节点平台的所有者,您所看到的问题是,nodebb崩溃启动后不久(但后绑定)。当Heroku检查以确保您的应用程序正确启动时,它会看到该端口不再被绑定(因为nodebb已崩溃)。要解决它,你必须找出为什么nodebb在60秒内崩溃。

我只是重复nodebb的Heroku的说明这里没有任何问题,所以你可以尝试的第一件事就是逐字经历他们:

https://docs.nodebb.org/en/latest/installing/cloud/heroku.html

你在0.4.3?