每次使用Nodemon保存时都会生成EADDRINUSE

kxxlusnw  于 2023-05-28  发布在  Node.js
关注(0)|答案(3)|浏览(161)

我使用Ubuntu 20.04,Nodemon 2.0.4,Node 14.9.0和Express 4.17.1。每次我保存代码时,都会得到这个错误:

events.js:291
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::3000
    at Server.setupListenHandle [as _listen2] (net.js:1318:16)
    at listenInCluster (net.js:1366:12)
    at Server.listen (net.js:1452:7)
    at Function.listen (/home/ubuntu/kopum/node_modules/express/lib/application.js:618:24)
    at Object.<anonymous> (/home/ubuntu/kopum/app.js:37:5)
    at Module._compile (internal/modules/cjs/loader.js:1075:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1096:10)
    at Module.load (internal/modules/cjs/loader.js:940:32)
    at Function.Module._load (internal/modules/cjs/loader.js:781:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1345:8)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '::',
  port: 3000
}
[nodemon] app crashed - waiting for file changes before starting...

然后我试着在终端上运行这个:

sudo lsof -i :3000
kill -9 {PID}

然后我通过运行nodemon app.js重新启动Nodemon,一切都恢复正常。但是当我添加一些代码并保存它时,EADDRINUSE又回来了。

kmb7vmvb

kmb7vmvb1#

当我遇到类似问题时,一个简单的解决方法是稍微延迟Nodemon的重启:

nodemon --delay 500ms app.js

这似乎为正确释放端口给予了一点时间。

9ceoxa92

9ceoxa922#

似乎nodemon在启动前没有正确地杀死子进程;
编辑package.json文件中的scripts属性,并添加一个kill命令,以在服务器启动之前终止侦听端口的所有进程。

"scripts": {
    "start": "npm run kill && nodemon app.js",
    "kill": "kill -9 $(lsof -i :3000) &>/dev/null | exit 0"
}
fzsnzjdm

fzsnzjdm3#

尝试在每个保存命令后运行npx kill-port 3000

相关问题