关于eggjs在Linux上启动时报错的问题及解决办法

之前eggjs2.0出来以后就开始使用eggjs进行后台开发了，由于测试方便，开始时项目部署在阿里云的windows系统下面，使用npm run dev的方式进行启动

但是等到项目开发完毕后，我开始部署到生产环境的Linux系统上面，这时候问题出来了，按照eggjs

官网上面的介绍，生产环境上面的部署使用npm start的方式启动部署，但是启动一直报以下的错误

egg-scripts] Wait Start: 35...
[egg-scripts] 2018-01-23 16:12:03,863 ERROR 3941 [-/127.0.0.1/-/0ms GET /] nodejs.Error: [ClusterClient] leader does not be active in 30000ms on port:45728
[egg-scripts] at Function.waitFor (/root/egg/node_modules/[email protected]@cluster-client/lib/server.js:239:15)
[egg-scripts] at waitFor.next ()
[egg-scripts] at onFulfilled (/root/egg/node_modules/[email protected]@co/index.js:65:19)
[egg-scripts] at 
[egg-scripts] at process._tickCallback (internal/process/next_tick.js:160:7)
[egg-scripts]
[egg-scripts] pid: 3941
[egg-scripts] hostname: iZ2ze76p2wnibfx0j7dslmZ
[egg-scripts]
[egg-scripts] 2018-01-23 16:12:03,863 ERROR 3941 nodejs.Error: [ClusterClient] leader does not be active in 30000ms on port:45728
[egg-scripts] at Function.waitFor (/root/egg/node_modules/[email protected]@cluster-client/lib/server.js:239:15)
[egg-scripts] at waitFor.next ()
[egg-scripts] at onFulfilled (/root/egg/node_modules/[email protected]@co/index.js:65:19)
[egg-scripts] at 
[egg-scripts] at process._tickCallback (internal/process/next_tick.js:160:7)
[egg-scripts]
[egg-scripts] pid: 3941
[egg-scripts] hostname: iZ2ze76p2wnibfx0j7dslmZ
[egg-scripts]
[egg-scripts] 2018-01-23 16:12:03,863 ERROR 3941 [app_worker] start error, exiting with code:1
[egg-scripts] 2018-01-23 16:12:03,863 ERROR 3941 [app_worker] exit with code:1
[egg-scripts] 2018-01-23 16:12:03,869 ERROR 3925 nodejs.AppWorkerDiedError: [master] app_worker#1:3941 died (code: 1, signal: null, suicide: false, state: dead), current workers: []
[egg-scripts] at Master.onAppExit (/root/egg/node_modules/[email protected]@egg-cluster/lib/master.js:384:21)
[egg-scripts] at Master.emit (events.js:159:13)
[egg-scripts] at Messenger.sendToMaster (/root/egg/node_modules/[email protected]@egg-cluster/lib/utils/messenger.js:122:17)
[egg-scripts] at Messenger.send (/root/egg/node_modules/[email protected]@egg-cluster/lib/utils/messenger.js:87:12)
[egg-scripts] at EventEmitter.cluster.on (/root/egg/node_modules/[email protected]@egg-cluster/lib/master.js:263:22)
[egg-scripts] at EventEmitter.emit (events.js:164:20)
[egg-scripts] at ChildProcess.worker.process.once (internal/cluster/master.js:185:13)
[egg-scripts] at Object.onceWrapper (events.js:254:19)
[egg-scripts] at ChildProcess.emit (events.js:159:13)
[egg-scripts] at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12)
[egg-scripts] name: 'AppWorkerDiedError'
[egg-scripts] pid: 3925
[egg-scripts] hostname: iZ2ze76p2wnibfx0j7dslmZ
[egg-scripts]
[egg-scripts] 2018-01-23 16:12:03,870 ERROR 3925 [master] app_worker#1:3941 start fail, exiting with code:1
[egg-scripts] 2018-01-23 16:12:03,871 ERROR 3925 [master] exit with code:1
[egg-scripts] 2018-01-23 16:12:03,873 ERROR 3931 [agent_worker] receive disconnect event on child_process fork mode, exiting with code:110
[egg-scripts] 2018-01-23 16:12:03,873 ERROR 3931 [agent_worker] exit with code:110
[egg-scripts]
[egg-scripts] Start got error, see /root/logs/master-stderr.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: egg-scripts start --workers=1 --daemon
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-01-23T08_12_05_860Z-debug.log
 

 

 

 

被这个错误烦扰了很久，一直找不到问题所在，由于eggjs的社区还没有完善，很多问题找不到解决的方法，后面去eggjs在github的开源上提交issue，也得到了官方的答复，当时官方没有给出问题的解决办法，后面只能自己试错，通过观看代买了解到egg 通过cluster-client 来做进程间的高级通信，所以会开一些端口，但这些端口只是内部通信的，这就很尴尬了，因为我的端口只有部分开发，所以问题处在，eggjs在启动的时候，被我的防火墙给拒绝了，导致启动失败，后面尝试把防火墙的规则给清除了，然后重新运行命令npm start 启动成功了！

 

希望这个坑的经验能够帮到您