22.03.02 21:37 작성
·
212
답변 1
0
2022. 03. 02. 21:54
back쪽 monit으로 살펴보니 에러가 있었습니다.
/root/.pm2/logs/app-error.log last 15 lines:
0|app | at listenInCluster (net.js:1379:12)
0|app | at Server.listen (net.js:1465:7)
0|app | at Function.listen (/home/ubuntu/react_nodebird/back/node_modules/express/lib/application.js:618:24)
0|app | at Object.<anonymous> (/home/ubuntu/react_nodebird/back/app.js:81:5)
0|app | at Module._compile (internal/modules/cjs/loader.js:1085:14)
0|app | at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
0|app | at Module.load (internal/modules/cjs/loader.js:950:32)
0|app | at Function.Module._load (internal/modules/cjs/loader.js:790:12)
0|app | at Object.<anonymous> (/home/ubuntu/react_nodebird/back/node_modules/pm2/lib/ProcessContainerFork.js:33:23) {
0|app | code: 'EADDRINUSE',
0|app | errno: -98,
0|app | syscall: 'listen',
0|app | address: '::',
0|app | port: 3065
0|app | }
0|app | Warning: connect.session() MemoryStore is not
0|app | designed for a production environment, as it will leak
0|app | memory, and will not scale past a single process.
0|app | Error: listen EADDRINUSE: address already in use :::3065
0|app | at Server.setupListenHandle [as _listen2] (net.js:1331:16)
0|app | at listenInCluster (net.js:1379:12)
0|app | at Server.listen (net.js:1465:7)
0|app | at Function.listen (/home/ubuntu/react_nodebird/back/node_modules/express/lib/application.js:618:24)
0|app | at Object.<anonymous> (/home/ubuntu/react_nodebird/back/app.js:81:5)
0|app | at Module._compile (internal/modules/cjs/loader.js:1085:14)
0|app | at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
0|app | at Module.load (internal/modules/cjs/loader.js:950:32)
0|app | at Function.Module._load (internal/modules/cjs/loader.js:790:12)
0|app | at Object.<anonymous> (/home/ubuntu/react_nodebird/back/node_modules/pm2/lib/ProcessContainerFork.js:33:23) {
0|app | code: 'EADDRINUSE',
0|app | errno: -98,
0|app | syscall: 'listen',
0|app | address: '::',
0|app | port: 3065
0|app | }
이미 사용중인 포트라고 에러가 나는 것 같아
PID kill과 pm2 kill을 하였으나 같은 에러가 발생합니다
2022. 03. 02. 22:00
sudo pm2 kill로 종료한 후 다시 해보세요.