Events. Js: 182
throw er;// Unhandled ‘error’ event
^
the error: Listen EADDRINUSE :::8000
at object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at server.setuplistenhandle [as] _listen2] (net. Js: 1315:14)
the at listenInCluster (net. Js: 1363:12)
the at Server. Listen (net. Js: 1463:7)
ats Function. Listen (G: \ webstorm \ movieManageWeb \ node_modules \ _express @ 4.16.2 @ express \ lib \ application js: 618-24)
the at Object. & lt; anonymous> (G: \ webstorm \ movieManageWeb \ app js: rising)
at the Module. The _compile (Module. Js: 569:30)
at the Object. The Module. _extensions.. Js (module. Js: 580:10)
at the module. The load (module. Js: 503:32)
the at tryModuleLoad (module. Js: 466:12)
at the Function, the module. _load (module. Js: 458:3)
the at Function.Module.runMain (module.js:605:10)
at startup (bootstrap_node.js:158:16)
at bootstrap_node.js:575:3
EADDRINUSE is err Address in use, which translates to using the wrong port
Actually, after the previous command runs, it still occupies port 8000. There are two solutions.
1, you can reset another port number.
2. Kill the process that was still occupying port 8000.
throw er;// Unhandled ‘error’ event
^
the error: Listen EADDRINUSE :::8000
at object.exports._errnoException (util.js:1022:11)
at exports._exceptionWithHostPort (util.js:1045:20)
at server.setuplistenhandle [as] _listen2] (net. Js: 1315:14)
the at listenInCluster (net. Js: 1363:12)
the at Server. Listen (net. Js: 1463:7)
ats Function. Listen (G: \ webstorm \ movieManageWeb \ node_modules \ _express @ 4.16.2 @ express \ lib \ application js: 618-24)
the at Object. & lt; anonymous> (G: \ webstorm \ movieManageWeb \ app js: rising)
at the Module. The _compile (Module. Js: 569:30)
at the Object. The Module. _extensions.. Js (module. Js: 580:10)
at the module. The load (module. Js: 503:32)
the at tryModuleLoad (module. Js: 466:12)
at the Function, the module. _load (module. Js: 458:3)
the at Function.Module.runMain (module.js:605:10)
at startup (bootstrap_node.js:158:16)
at bootstrap_node.js:575:3
EADDRINUSE is err Address in use, which translates to using the wrong port
Actually, after the previous command runs, it still occupies port 8000. There are two solutions.
1, you can reset another port number.
2. Kill the process that was still occupying port 8000.
Read More:
- Error: listen eadrinuse: address already in use
- Error starting userland proxy: listen TCP 0.0.0.0:9000: Listen: address already in use
- filezilla Failed to create listen socket on port 21 for IPv4 solution
- Solution to the problem that listen TCP 0.0.0.0:3306: bind: address already in use port is occupied in Linux centos7
- Error: listen EADDRINUSE :::3000
- Nodejs exception error: listen eacces 127.0.0.1:8000
- listen EADDRINUSE 127.0.0.1:3000
- Error: listen eaddnotavail: address not available
- Vue start error: listen eadrnotavail
- Error: listen EADDRNOTAVAIL: address not available 192.168.43.149:8002
- The Tomcat connector configured to listen on port 7014 failed to start
- Some error occurred error: listen eaddinuse: address already in use 127.0.0.1:3000
- The Tomcat connector configured to listen on port 8080 failed to start. The port may already be in u
- Error receiving broadcast Intent { act=com.supersdk.listen.PayListen_defeat flg=0x10 (has extras)
- Box mount Cody_ How to listen to Pandora in Cody
- Events.js:167 throw er appears when starting node service under linux; // Unhandled ‘error’ event solution
- Solution / error of. Net framework 4.0 installation failure HResult 0xc8000222 solution
- Error: Cannot find module’webpack/bin/config-yargs’ solution
- Solution to can’t bind to local 8600 for debugger
- The error record when docker starts Nacos, and the solution to the problem of port occupation