blocks|key|91046|text|某个实例可能仍在运行。这会解决它的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91047|killall+node|code-block|syntax|javascript|91048|更新:此命令仅适用于Linux/Ubuntu+&+Mac。|91049|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

An instance is probably still running.
This will fix it.

<pre><code>killall node
</code></pre>

Update: This command will only work on Linux/Ubuntu &amp; Mac.

blocks|key|308251|text|这是因为您用来运行脚本的端口已在使用中。您必须停止正在使用该post的所有其他节点。为此，您可以通过以下方式检查所有节点|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308252|ps+-e|code-block|syntax|javascript|308253|或者仅对于节点进程使用ps+-ef+%7C+grep+node，这将为您提供具有id的所有节点进程的列表|offset|length|style|CODE|308254|终止所有节点进程|308255|sudo+killall+-9+node|308256|或用于特定的id+sudo+kill+-9+id。|308257|entityMap^0|0|0|B|I|0|0|0|9|F|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|11|8|@$I|12|J|13|K|L]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

This is because the port you are using to run the script is already in use.
You have to stop all other nodes which are using that post.
for that, you can check all node by 

<pre><code>ps -e
</code></pre>

OR for node process only use <code>ps -ef | grep node</code>
This will give you the list of all node process with id 

to Kill all node process

<pre><code>sudo killall -9 node
</code></pre>

Or for the specific id <code>sudo kill -9 id</code>

blocks|key|90958|text|我通过更改端口修复了这个错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|90959|app.set('port',+process.env.PORT+%7C%7C+3000); |code-block|syntax|javascript|90960|并更改为：|90961|app.set('port',+process.env.PORT+%7C%7C+8080); |90962|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I fixed the bug by changing the port which was 

<pre><code>app.set('port', process.env.PORT || 3000);&lt;br&gt;
</code></pre>

and changed to: 

<pre><code>app.set('port', process.env.PORT || 8080);&lt;br&gt;
</code></pre>

blocks|key|308108|text|Node尝试使用的端口可能已被其他程序使用。在我的例子中，它是我最近安装的ntop。我必须在浏览器中打开http://localhost:3000/才能实现它。另一种查找进程的方法是使用here。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|308109|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ntop.org/|1|http://localhost:3000/|2|http://www.cyberciti.biz/faq/what-process-has-open-linux-port/^0|11|4|0|1G|M|1|2L|4|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

The port Node is trying to use can be already used by another program. In my case it was <a href="http://www.ntop.org/" rel="nofollow">ntop</a>, which I had recently installed. I had to open <a href="http://localhost:3000/" rel="nofollow">http://localhost:3000/</a> in a browser to realize it. Another way to find the process is given <a href="http://www.cyberciti.biz/faq/what-process-has-open-linux-port/" rel="nofollow">here</a>.

blocks|key|90787|text|关闭正在运行的任何其他节点服务器，即使它们在其他终端窗口中或在不同的端口上运行。这应该可以解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|90788|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Close any other node servers that are running, even if they are in other terminal windows or running on different ports. That should fix the problem.

blocks|key|308271|text|如果您想使用相同的端口号，那么在终端中输入kill+%25，这将终止当前的后台进程，并释放端口以供进一步使用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|308272|entityMap^0|L|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

If you want to use the same port number then type <code>kill %</code> in the terminal, which kills the current background process and frees up the port for further usage.

blocks|key|308356|text|这意味着您的文件现在正在运行。只需输入以下代码，然后重试：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308357|sudo+pkill+node|code-block|syntax|javascript|308358|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

this means your file is running now. just enter below code and try again:

<pre><code>sudo pkill node
</code></pre>

blocks|key|91343|text|实际上Ctrl%2BC密钥没有释放节点进程使用的端口。所以出现了这个错误。该问题的解决方案是在server.js中使用以下代码片段：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91344|process.on('SIGINT',+function()+{
++console.log(+"\nGracefully+shutting+down+from+SIGINT+(Ctrl-C)"+);
++//+some+other+closing+procedures+go+here
++process.exit(1);
});|code-block|syntax|javascript|91345|这对我很有效。|91346|您还可以查看Graceful+shutdown+in+NodeJS上提到的其他解决方案|offset|length|91347|entityMap|0|LINK|mutability|MUTABLE|url|https://hackernoon.com/graceful-shutdown-in-nodejs-2f8f59d1c357^0|0|0|0|6|R|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Actually Ctrl+C keys not releasing port used by node process. So there is this error.
The resolution to the issue was using following code snippet in server.js:

<pre><code>process.on('SIGINT', function() {
 console.log( "\nGracefully shutting down from SIGINT (Ctrl-C)" );
 // some other closing procedures go here
 process.exit(1);
});
</code></pre>

This worked for me.

You can also check for other solutions mentioned at <a href="https://hackernoon.com/graceful-shutdown-in-nodejs-2f8f59d1c357" rel="nofollow noreferrer">Graceful shutdown in NodeJS</a>

blocks|key|90826|text|如果你已经尝试杀死所有监听3000+(+express框架设置使用的默认设置)的节点实例和其他服务都没有用，你应该检查以确保你的环境没有将'port‘定义为意想不到的东西。否则，您很可能会得到相同的错误。在express框架的app.js文件中，您将注意到第15行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|90827|app.set('port',+process.env.PORT+%7C%7C+3000);|code-block|syntax|javascript|90828|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you've tried killing all node instances and other services listening on 3000 (the default used by the express skeleton setup) to no avail, you should check to make sure that your environment is not defining 'port' to be something unexpected. Otherwise, you'll likely get the same error. In the express skeleton's app.js file you'll notice line 15:

<pre><code>app.set('port', process.env.PORT || 3000);
</code></pre>

blocks|key|308616|text|我今天遇到了同样的问题，端口没有被使用。以下方法很有帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308617|rm+-rf+node_modules+&&+npm+cache+clean+&&+npm+install
npm+start|code-block|syntax|javascript|308618|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I ran into the same issue today and the port was not used. The following approach helped:

<pre><code>rm -rf node_modules &amp;&amp; npm cache clean &amp;&amp; npm install
npm start
</code></pre>

blocks|key|90912|text|在我的例子中，我也不得不运行vagrant+reload。即使在我的虚拟机中没有节点进程运行我的express应用程序，我仍然会收到这个错误，直到重新加载vagrant+box。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|90913|entityMap^0|E|E|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

In my case I've had to run <code>vagrant reload</code> as well. Even with no node processes running my express app in my virtual machine I was still getting this error until reloading the vagrant box.

blocks|key|90969|text|停止正在使用该端口的服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|90970|sudo+service+NAMEOFSERVICE+stop|code-block|syntax|javascript|90971|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Stop the service that is using that port.

<pre><code>sudo service NAMEOFSERVICE stop
</code></pre>

blocks|key|308203|text|这对我很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308204|http://www.codingdefined.com/2015/09/how-to-solve-nodejs-error-listen.html|offset|length|308205|只需在项目属性中更改端口号即可。|308206|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|22|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

This worked for me.

<a href="http://www.codingdefined.com/2015/09/how-to-solve-nodejs-error-listen.html" rel="nofollow">http://www.codingdefined.com/2015/09/how-to-solve-nodejs-error-listen.html</a>

Just change the port number from the Project properties.

blocks|key|91152|text|您还可以从Gruntfile.js更改端口，然后再次运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91153|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can also change the port from Gruntfile.js and run again.

blocks|key|91164|text|在多次终止同一进程并且无法定位端口8000上运行的其他进程之后，我意识到我正在尝试在端口8000上运行两次：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91165|之前：|91166|MongoClient.connect(db.url,+(err,+database)+=>+{
++if+(err)+return+console.log(err);
++require('./app/routes')(app,+database);

++app.listen(port,+()+=>+{
++++console.log('We+are+live+on+'+%2B+port);
++});
});

require('./app/routes')(app,+{});
app.listen(port,+()+=>+{
++console.log("We+are+live+on+"+%2B+port);
});|code-block|syntax|javascript|91167|之后：|91168|MongoClient.connect(db.url,+(err,+database)+=>+{
++if+(err)+return+console.log(err);
++require('./app/routes')(app,+database);

++app.listen(port,+()+=>+{
++++console.log('We+are+live+on+'+%2B+port);
++});
});

require('./app/routes')(app,+{});|91169|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

After killing the same process multiple times and not being able to locate what else was running on port 8000, I realized I was trying to run on port 8000 twice:

Before:

<pre><code>MongoClient.connect(db.url, (err, database) =&gt; {
 if (err) return console.log(err);
 require('./app/routes')(app, database);

 app.listen(port, () =&gt; {
 console.log('We are live on ' + port);
 });
});

require('./app/routes')(app, {});
app.listen(port, () =&gt; {
 console.log("We are live on " + port);
});
</code></pre>

After:

<pre><code>MongoClient.connect(db.url, (err, database) =&gt; {
 if (err) return console.log(err);
 require('./app/routes')(app, database);

 app.listen(port, () =&gt; {
 console.log('We are live on ' + port);
 });
});

require('./app/routes')(app, {});
</code></pre>

blocks|key|91202|text|我也遇到了同样的问题，我发现我之前用CTRL%2BC取消的一个nodejs进程仍在运行。Windows10中的问题是，Ctrl+%2B+C+Doesn't+Kill+Gracefully+nodejs。我打开了任务管理器并手动终止了进程。GitHub上提供的解决方案对我不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|91203|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nodejs/node/issues/16103^0|1L|W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I had the same problem and I found out, that a nodejs process that I had previously canceled with CTRL+C was still running. The problem in Windows 10 is, that <a href="https://github.com/nodejs/node/issues/16103" rel="nofollow noreferrer">Ctrl + C Doesn't Kill Gracefully</a> nodejs. I opened the task manager and killed the process manually. The solutions provided on GitHub didn't work for me.

blocks|key|308403|text|如果您使用的是node.js，则可以从windows的任务管理器结束进程|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308404|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you using windows, then you can end process from task manager for node.js

blocks|key|91306|text|所有的答案对我都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91307|当我重新启动计算机时，我可以让服务器启动并运行。|91308|Mac|91309|shutdown+now+-r|offset|length|style|CODE|91310|Linux|91311|sudo+shutdown+now+-r|91312|entityMap^0|0|0|0|0|F|0|0|0|K|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@$H|V|I|W|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|Q|$]]

None of the answers worked for me.

When I restarted my computer I could get the server up and running. 

Mac 
 <code>shutdown now -r</code>

Linux 
 <code>sudo shutdown now -r</code>

blocks|key|308515|text|->check端口8080上运行的是什么，或者您要检查的端口是什么|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308516|lsof+-i+@localhost:8080|code-block|syntax|javascript|308517|如果某个程序正在运行，您可以将其关闭或使用某个kill命令将其关闭|308518|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

->check what’s running on port 8080 or what ever port u want to check

<pre><code>lsof -i @localhost:8080
</code></pre>

if something is running u can close it or use some kill command to close it

blocks|key|308553|text|很简单，只需在Visual+Studio代码中检查你的终端，因为我正在运行我的节点应用程序，并且我休眠了我的笔记本电脑，然后第二天早上，我打开我的笔记本电脑，继续开发软件。我再次运行命令nodemon+app.js，第一次是从晚上运行，第二次是运行我的最新命令，所以两个命令提示符正在侦听相同的端口，这就是为什么会出现这个问题。只需关闭一个termianl或所有终端，然后运行node+app.js或nodemon+app.js|type|unstyled|depth|inlineStyleRanges|entityRanges|data|308554|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Simple just check your teminal in Visual Studio Code
Because me was running my node app and i hibernate my laptop then next morning i turn my laptop on back to development of software. THen i run the again command nodemon app.js
First waas running from night and the second was running my latest command so two command prompts are listening to same ports that's why you are getting this issue.
Simple Close one termianl or all terminal then run your node app.js or nodemon app.js

blocks|key|91597|text|我的答案是其中一个解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91598|如果您正在尝试使用以下命令运行angular应用程序|91599|ng+serve+--open|code-block|syntax|javascript|91600|--open在默认浏览器中打开url此标记导致问题。我不知道angular+10版本之后的目的是什么，它不能工作。我还在分析|91601|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

My answers is one of the solution
If you are trying to run angular application with below command
<pre><code>ng serve --open
</code></pre>
--open Opens the url in default browser this tag is causing the issue. i don't know what is the purpose after angular 10 version which is not working. I am still analysing

blocks|key|91107|text|只需更改您的端口，可能您的当前端口正在被iis或其他服务器使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91108|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just change your port,might be your current port is in use by iis or some other server.

blocks|key|91515|text|npm+install+--save+--save-exact+react-scripts@2.1。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|91516|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

npm install --save --save-exact react-scripts@2.1.

I created expressjs application using the following commands:

<pre><code>express -e folderName
npm install ejs --save
npm install
</code></pre>

When I run the application with: <code>node app.js</code>, I have the following errors:

<pre><code>events.js:72
 throw er; // Unhandled 'error' event
 ^
Error: listen EADDRINUSE
 at errnoException (net.js:884:11)
 at Server._listen2 (net.js:1022:14)
 at listen (net.js:1044:10)
 at Server.listen (net.js:1110:5)
 at Object.&lt;anonymous&gt; (folderName/app.js:33:24)
 at Module._compile (module.js:456:26)
 at Object.Module._extensions..js (module.js:474:10)
 at Module.load (module.js:356:32)
 at Function.Module._load (module.js:312:12)
 at Function.Module.runMain (module.js:497:10)
</code></pre>

How to fix it?

ExpressJS - throw er Unhandled error event

Visual Studio

服务器

虚拟机

GitHub

Ubuntu

Linux

我使用以下命令创建了expressjs应用程序：express -e folderNamenpm install ejs --savenpm install当我使用：node app.js运行应用程序时，我有以下错误：events.js:72    throw er; // Unhandled 'error' event          ^Error: listen EADDRINUSE    

问ExpressJS -引发er未处理的错误事件
EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ExpressJS -引发er未处理的错误事件EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ExpressJS -引发er未处理的错误事件
EN