Question

106

Node js +Error: listen EADDRINUSE + Unhandled 'error' event

rated 0 times [ 109] [ 3] / answers: 1 / hits: 20396 / 10 Years ago, mon, february 24, 2014, 12:00:00

I'm using nodeclipse plugin for eclipse to run my node js project.Following js file is working properly but h1 tag is not working .I can only see a plain text.plus I'm getting this exception in the runtime.please help me out.

javascript file

   var http = require('http');



http.createServer(function (request, response) {

    response.writeHead(200, {'Content-Type': 'text/html'});

    response.end('<html><body><h1>Home</h1> URL was: ' + request.url + '</body></html>');

}).listen(3000, 'localhost');



console.log('Server running at http://localhost:3000/');

exception

 events.js:72

        throw er; // Unhandled 'error' event

              ^

Error: listen EADDRINUSE

    at errnoException (net.js:904:11)

    at Server._listen2 (net.js:1042:14)

    at listen (net.js:1064:10)

    at net.js:1146:9

    at dns.js:72:18

    at process._tickCallback (node.js:415:13)

    at Function.Module.runMain (module.js:499:11)

    at startup (node.js:119:16)

    at node.js:902:3

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

andreguym

Add To Favorites

Follow

Total Points: 125

Total Questions: 112

Total Answers: 103

Location: Wallis and Futuna

Member since Tue, Mar 30, 2021

3 Years ago

answered 10 Years ago pranavrorys · Accepted Answer

Error: listen EADDRINUSE

This error means that you already have another process listening on port 3000.

Here is how to find out which process it is on windows

C:> netstat -a -b

(add -n to stop it trying to resolve hostnames, which will make it a lot faster)



Edit: +1 for Dane's recommendation for TCPView. Looks very useful!



-a Displays all connections and listening ports.



-b Displays the executable involved in creating each connection or listening port. In some cases well-known executables host multiple independent components, and in these cases the sequence of components involved in creating the connection or listening port is displayed. In this case the executable name is in [] at the bottom, on top is the component it called, and so forth until TCP/IP was reached. Note that this option can be time-consuming and will fail unless you have sufficient permissions. -n Displays addresses and port numbers in numerical form.