升级后迁移期间的火箭聊天错误

时间:2018-06-11 15:56:43

标签: rocket.chat

我最近在CentOS服务器上将rocket.chat从0.62升级到0.65。在运行node main.js时,我得到以下输出:

Setting default file store to FileSystem
connect deprecated multipart: use parser (multiparty, busboy, formidable) npm module instead npm/node_modules/connect/lib/middleware/bodyParser.js:56:20
connect deprecated limit: Restrict request size at location of read npm/node_modules/connect/lib/middleware/multipart.js:86:15
{"line":"160","file":"rocketchat_migrations.js","message":"Migrations: Not migrating, already at version 121","time":{"$date":1528731630704},"level":"info"}
Updating process.env.MAIL_URL
Using GridFS for custom sounds storage
Using GridFS for custom emoji storage
Push: configuring...
Push.Configure { sendTimeout: 60000,
  apn: undefined,
  gcm: 
   { apiKey: 'XXXX',
     projectNumber: 'YYYY' },
  production: true,
  sendInterval: 1000,
  sendBatchSize: 10 }
GCM configured
Push: Send worker started, using interval: 1000
Exception in callback of async function: Error: listen EADDRINUSE 0.0.0.0:3000
    at Object._errnoException (util.js:1024:11)
    at _exceptionWithHostPort (util.js:1046:20)
    at Server.setupListenHandle [as _listen2] (net.js:1351:14)
    at listenInCluster (net.js:1392:12)
    at doListen (net.js:1501:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickDomainCallback (internal/process/next_tick.js:218:9)

➔ System ➔ startup
➔ +-------------------------------------------------------------+
➔ |                        SERVER RUNNING                       |
➔ +-------------------------------------------------------------+
➔ |                                                             |
➔ |  Rocket.Chat Version: 0.65.1                                |
➔ |       NodeJS Version: 8.9.3 - x64                           |
➔ |             Platform: linux                                 |
➔ |         Process Port: 3000                                  |
➔ |             Site URL: http://ZZZZ:3000  |
➔ |     ReplicaSet OpLog: Disabled                              |
➔ |          Commit Hash: 8349c36de0                            |
➔ |        Commit Branch: HEAD                                  |
➔ |                                                             |
➔ +-------------------------------------------------------------+

虽然服务器正在运行,但我无法从浏览器访问它。什么是可能的错误?

1 个答案:

答案 0 :(得分:0)

我列出了ps -ax | grep node运行节点的所有进程,并将所有进程全部删除。我重新考虑了node main.js并解决了所有问题。