blocks|key|701984|text|这意味着您试图将服务器绑定到的地址正在使用中。尝试其他端口或使用该端口关闭程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|701985|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|$]]

It means the address you are trying to bind the server to is in use. Try another port or close the program using that port.

blocks|key|486299|text|运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486300|ps+-ax+%7C+grep+node|code-block|syntax|javascript|486301|你会得到类似这样的结果：|486302|60778+??+++++++++0:00.62+/usr/local/bin/node+abc.js|486303|然后执行以下操作：|486304|kill+-9+60778|486305|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Run:

<pre><code>ps -ax | grep node
</code></pre>

You'll get something like:

<pre><code>60778 ?? 0:00.62 /usr/local/bin/node abc.js
</code></pre>

Then do:

<pre><code>kill -9 60778
</code></pre>

blocks|key|486373|text|在Linux上(至少是Ubuntu衍生品)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486374|killall+node|code-block|syntax|javascript|486375|比这个表单更简单。|486376|ps+%7C+grep+<something>
kill+<somepid>|486377|如果有一个孤立的孩子持有端口，这两种方法都不会起作用。相反，请执行以下操作：|486378|netstat+-punta+%7C+grep+<port>|486379|如果端口被占用，您将看到如下所示：|486380|tcp+++++++++++0++++++0.0.0.0:<port>++++++++++0.0.0.*+++++++LISTEN+++++<pid>/<parent>|486381|现在通过pid终止：|486382|kill+-9+<pid>|486383|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

On Linux (Ubuntu derivatives at least)

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

is easier than this form.

<pre><code>ps | grep &lt;something&gt;
kill &lt;somepid&gt;
</code></pre>

Neither will work if you have a orphaned child holding the port. Instead, do this:

<pre><code>netstat -punta | grep &lt;port&gt;
</code></pre>

If the port is being held you'll see something like this:

<pre><code>tcp 0 0.0.0.0:&lt;port&gt; 0.0.0.* LISTEN &lt;pid&gt;/&lt;parent&gt;
</code></pre>

Now kill by pid:

<pre><code>kill -9 &lt;pid&gt;
</code></pre>

blocks|key|486283|text|以下命令将为您提供正在运行的节点进程的列表。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486284|ps+%7C+grep+node|code-block|syntax|javascript|486285|要释放该端口，请使用以下命令停止该进程。|486286|kill+<processId>|486287|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|$]]

The following command will give you a list of node processes running. 

<pre><code>ps | grep node
</code></pre>

To free up that port, stop the process using the following.

<pre><code>kill &lt;processId&gt;
</code></pre>

blocks|key|702155|text|当你得到一个错误错误:+listen+EADDRINUSE，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|702156|尝试运行以下shell命令：|702157|netstat+-a+-o+%7C+grep+8080
taskkill+/F+/PID+6204|code-block|syntax|javascript|702158|我对8080执行了grep，因为我知道我的服务器正在8080端口上运行。(当我开始的时候，static会告诉我：“服务”。“在http://127.0.0.1:8080”。)您可能需要搜索不同的端口。|offset|length|style|CODE|702159|entityMap|0|LINK|mutability|MUTABLE|url|http://127.0.0.1:8080/^0|0|0|0|9|4|19|6|1R|L|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$K|10|L|11|M|N]|$K|12|L|13|M|N]]|9|@$K|14|L|15|1|16]]|A|$]]|$1|O|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

When you get an error Error: listen EADDRINUSE,

Try running the following shell commands:

<pre><code>netstat -a -o | grep 8080
taskkill /F /PID 6204
</code></pre>

I <code>grep</code>ed for 8080, because I know my server is running on port 8080. (<code>static</code> tells me when I start it: 'serving "." at <a href="http://127.0.0.1:8080" rel="noreferrer">http://127.0.0.1:8080</a>'.) You might have to search for a different port.

blocks|key|702494|text|假设您的服务器在port+3000上运行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|702495|lsof+-i+tcp:3000
++++COMMAND+++PID+USER+++FD+++TYPE+DEVICE+SIZE/OFF+NODE+NAME
++++node++++11716+arun+++11u++IPv6+159175++++++0t0++TCP+*:3000+(LISTEN)|code-block|syntax|javascript|702496|之后使用kill+-9+<pid>|702497|在上面的例子中，sudo+kill+-9+11716|702498|entityMap^0|8|9|0|0|4|D|0|8|I|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

suppose your server is running on <code>port 3000</code> 

<pre><code>lsof -i tcp:3000
 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
 node 11716 arun 11u IPv6 159175 0t0 TCP *:3000 (LISTEN)
</code></pre>

after that use <code>kill -9 &lt;pid&gt;</code>

in the above case <code>sudo kill -9 11716</code>

blocks|key|702754|text|在下面的示例中，使用下面的命令杀死在某个端口3000上运行的进程|type|unstyled|depth|inlineStyleRanges|entityRanges|data|702755|kill+-9+$(lsof+-t+-i:3000)|code-block|syntax|javascript|702756|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|$]]

use below command to kill a process running at a certain port - 3000 in this example below 

<pre><code>kill -9 $(lsof -t -i:3000)
</code></pre>

blocks|key|487290|text|检查进程ID|type|unstyled|depth|inlineStyleRanges|entityRanges|data|487291|sudo+lsof+-i:8081|487292|而不是杀死特定的进程|487293|sudo+kill+-9+2925|487294|​|487295|📷|atomic|offset|length|487296|487297|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/d607a5bf723539798cf65bce6804751a.png|imageAlt^0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@$M|14|N|15|1|16]]|A|$]]|$1|O|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]]]

Check the Process ID

sudo lsof -i:8081

Than kill the particular Process

sudo kill -9 2925

<a href="https://i.stack.imgur.com/uh8Ad.png" rel="noreferrer"><img src="https://i.stack.imgur.com/uh8Ad.png" alt="enter image description here"></a>

blocks|key|702349|text|对我有效的一种可能的解决方案是，简单地在浏览器中关闭窗口，在那里我运行了相应的"http://localhost:3000/“脚本。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|702350|entityMap|0|LINK|mutability|MUTABLE|url|http://localhost:3000/^0|14|M|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]]]]

One possible solution that worked for me was simply to close the window in browser where I had the corresponding "<a href="http://localhost:3000/" rel="noreferrer">http://localhost:3000/</a>" script running.

blocks|key|487137|text|帕特里克建议的上述killall+-9节点的工作方式与预期一致，并解决了这个问题，但您可能想要阅读这个答案的编辑部分，了解为什么kill+-9不是最好的方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|487138|最重要的是，您可能希望针对单个进程，而不是盲目地杀死所有活动的进程。|487139|在这种情况下，首先获取在该端口(比如8888)上运行的进程的进程ID+(PID)：|487140|lsof+-i+tcp:8888|code-block|syntax|javascript|487141|这将返回如下内容：|487142|COMMAND+++PID++++USER+++FD+++TYPE+++++++++++++DEVICE+SIZE/OFF+NODE+NAME
node+++++57385+++You+++11u++IPv6+0xac745b2749fd2be3++++++0t0++TCP+*:ddi-tcp-1|487143|(听)然后就做(ps+-实际上不做。请继续阅读以下内容)：|487144|kill+-9+57385|487145|entityMap^0|9|A|1S|7|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|14|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|15|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|17|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|18|8|@]|D|@]|E|$]]|$1|U|3|V|5|L|7|19|8|@]|D|@]|E|$M|N]]|$1|W|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|X|$]]

The aforementioned <code>killall -9</code> node, suggested by Patrick works as expected and solves the problem but you may want to read the edit part of this very answer about why <code>kill -9</code> may not be the best way to do it.

On top of that you might want to target a single process rather than blindly killing all active processes.

In that case, first get the process ID (PID) of the process running on that port (say 8888):

<pre><code>lsof -i tcp:8888
</code></pre>

This will return something like:

<pre><code>COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
node 57385 You 11u IPv6 0xac745b2749fd2be3 0t0 TCP *:ddi-tcp-1
</code></pre>

(LISTEN)
Then just do (ps - actually do not. Please keep reading below):

<pre><code>kill -9 57385
</code></pre>

blocks|key|487187|text|这在Mac上有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|487188|第1步。|487189|sudo+lsof+-i+tcp:3000+(or+whatever+port+you+want+to+kill)|code-block|syntax|javascript|487190|上面的命令将为您提供当前持有该端口的进程Id。|487191|第2步。|487192|Kill+-9+<pid>|487193|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|V|8|@]|9|@]|A|$G|H]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

This works on Mac:

Step 1. 

<pre><code>sudo lsof -i tcp:3000 (or whatever port you want to kill)
</code></pre>

Above command will give you the Process Id(s) currently holding the port.

Step 2. 

<pre><code>Kill -9 &lt;pid&gt;
</code></pre>

blocks|key|486697|text|我创建了两个服务器，监听相同的端口8081，从相同的代码运行，同时学习|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486698|第1个服务器创建应已完成，第2个服务器创建失败，错误为EADDRINUSE|486699|node.js回调延迟可能是无法正常工作的原因，或者第二台服务器创建有异常，程序退出，因此第一台服务器也被关闭|486700|2服务器问题提示，来自：How+to+fix+Error:+listen+EADDRINUSE+while+using+nodejs?|offset|length|486701|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9898372/nodejs-error-listen-eaddrinuse^0|0|0|0|C|1J|0|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|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I created 2 servers, listening on same port 8081, running from same code, while learning

1st server creation shud have worked
2nd server creation failed with EADDRINUSE

node.js callback delays might be reason behind neither worked, or 2nd server creation had exception, and program exited, so 1st server is also closed

2 server issue hint, I got from: 
<a href="https://stackoverflow.com/questions/9898372/nodejs-error-listen-eaddrinuse">How to fix Error: listen EADDRINUSE while using nodejs?</a>

blocks|key|486848|text|错误:听EADDRINUSE来解决它在Ubuntu中运行在终端netstat+-nptl和此kill+-9+{process-number}之后，此命令是杀死节点进程，现在您可以尝试再次运行节点server.js命令|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|486849|例如|486850|收听EADDRINUSE+:8080|486851|netstat+-nptl|486852|tcp6+0+0:9000：*监听9660/java|486853|tcp6+0+0:5800：*监听-|486854|tcp6+0+0:5900：*监听-|486855|tcp6+0+0:8080：*监听10401个/节点|486856|tcp6+0+0:20080：*监听9660/java|486857|tcp6+0+0:80：*监听-|486858|tcp6+0+0:22：*监听-|486859|tcp6+0+0:10137：*监听9660/java|486860|kill+-9+10401|486861|entityMap^0|V|D|1A|O|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1C|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1D|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1E|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1F|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1G|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1H|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|1I|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|1J|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|1K|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|1L|8|@]|D|@]|E|$]]|$1|13|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|14|$]]

Error: listen EADDRINUSE to solve it in Ubuntu run in terminal <code>netstat -nptl</code> and after this <code>kill -9 {process-number}</code> this command is to kill node process and now you can try to run again node server.js command

Ex 

listen EADDRINUSE :::8080

netstat -nptl 

tcp6 0 0 :::9000 :::* LISTEN 9660/java 
tcp6 0 0 :::5800 :::* LISTEN - 
tcp6 0 0 :::5900 :::* LISTEN - 
tcp6 0 0 :::8080 :::* LISTEN 10401/node 
tcp6 0 0 :::20080 :::* LISTEN 9660/java 
tcp6 0 0 :::80 :::* LISTEN - 
tcp6 0 0 :::22 :::* LISTEN - 
tcp6 0 0 :::10137 :::* LISTEN 9660/java 

kill -9 10401

blocks|key|486501|text|我在我的Mac和Raspberry+Pi上安装了node+red。有完全相同的问题，做'killall‘没有帮助。一旦我关闭了树莓派，并重新启动了我的电脑，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486502|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|$]]

I have node red installed on my Mac and my Raspberry Pi. Had the exact same problem and doing 'killall' didn't help. Once I shut down the Raspberry Pi and restarted my computer it worked fine.

blocks|key|702459|text|您可能尝试在两个不同的选项卡中运行npm+start命令，当npm+start已经在某些tab.check中运行一次时，它无法运行npm+start。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|702460|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|$]]

It may be possible that you have tried to run the npm start command in two different tabs .you cant run npm start when it is already running in some tab.check it once .

blocks|key|702619|text|对于已经尝试了上述所有方法，但仍然找不到rouge进程的任何人，请再次尝试所有这些方法，但请确保在命令前包含"sudo“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|702620|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|$]]

To anyone who has tried all of the above, but still can't find the rouge process, try them all again but make sure you include "sudo" in front of the commands.

blocks|key|702685|text|如果你更喜欢UI，在windows任务管理器中找到进程Node.js并杀死它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|702686|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 like UI more, find the process Node.js in windows task manager and kill it.

blocks|key|702704|text|ps+-ef+%7Cgrep节点查找app.js，杀死app.js的pid|type|unstyled|depth|inlineStyleRanges|entityRanges|data|702705|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|$]]

ps -ef |grep node
find app.js ,
kill pid of app.js

blocks|key|487080|text|只需在ubantu的终端中将节点作为pkill+-9节点删除，而不是开始节点|type|unstyled|depth|inlineStyleRanges|entityRanges|data|487081|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|$]]

simply kill the node
as 
pkill -9 node
in terminal of ubantu 
than start node

blocks|key|703106|text|您需要尝试在终端上使用以下命令来终止端口|type|unstyled|depth|inlineStyleRanges|entityRanges|data|703107|$+sudo+killall+-9+nodejs|code-block|syntax|javascript|703108|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|$]]

You will need to kill the port by trying to use the following command on the terminal

<pre><code>$ sudo killall -9 nodejs
</code></pre>

blocks|key|487411|text|我只需删除(cmd)终端并打开另一个终端，然后再次运行node+myfile.js|type|unstyled|depth|inlineStyleRanges|entityRanges|data|487412|它对我来说太棒了。|487413|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I Just delete that (cmd) Terminal and open another terminal and run again
node myfile.js
it works awesomely for me.

blocks|key|703066|text|我使用命令netstat+-ano+%7C+grep+"portnumber"来列出该进程的端口号/PID。然后，您可以使用taskkill+-f+//pid+111111终止该进程，最后一个值是您在第一个命令中找到的pid。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|703067|我有时遇到的一个问题是，即使在终止进程之后，节点也会重新生成，因此我必须使用良好的旧任务管理器来手动终止节点进程。|703068|entityMap^0|5|W|1O|O|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

I used the command <code>netstat -ano | grep "portnumber"</code> in order to list out the port number/PID for that process. 
Then, you can use <code>taskkill -f //pid 111111</code> to kill the process, last value being the pid you find from the first command.

One problem I run into at times is node respawning even after killing the process, so I have to use the good old task manager to manually kill the node process.

blocks|key|486546|text|在window中，请执行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|486547|taskkill+/F+/PID+1952|code-block|syntax|javascript|486548|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|$]]

In window, please execute this command: 

<pre><code>taskkill /F /PID 1952
</code></pre>

i am testing a server written in nodejs on windows 7
and when i try to run the tester in the command line i get the following error

<pre><code>Error: listen EADDRINUSE
at errnoException (net.js:614:11)
at Array.0 (net.js:704:26)
at EventEmitter._tickCallback (node.js:192:40)
</code></pre>

how can I fix it without rebooting?

how to release localhost from Error: listen EADDRINUSE

我在Windows7上测试用nodejs编写的服务器，当我尝试在命令行中运行测试程序时，我得到了以下错误Error: listen EADDRINUSEat errnoException (net.js:614:11)at Array.0 (net.js:704:26)at EventEmitter._tickCallback (node.js:192:40)我如何才能在不重启的情况下修复它？

问如何从错误中释放localhost : listen EADDRINUSE
EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从错误中释放localhost : listen EADDRINUSEEN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从错误中释放localhost : listen EADDRINUSE
EN