I created expressjs application using the following commands:
express -e folderName
npm install ejs --save
npm install
When I run the application with: node app.js, I have the following errors:
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.<anonymous> (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)
How to fix it?
You had run another server use the same port like 8080.
Maybe you had run node app in other shell, Please close it and run again.
We do get similar error when we sometimes run our express app. We have to follow the same in that case. We need to check if its running in any terminal. If you want to find and kill process, follow these steps:
If you're on Linux, this problem can also occur if Nodejs is not running as root.
Change from this:
nodejs /path/to/script.js
To this:
sudo nodejs /path/to/script.js
Just happened to me and none of the other suggestions here fixed it. Luckily I remembered the script was working the other day when running as root. Hope this helps someone!
Disclaimer: This probably isn't the best solution for a production environment. Starting your service as root may introduce some security holes to your server/applcation. In my case, this was a solution for a local service, but I'd encourage others to spend some more time trying to isolate the cause.
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.
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:
app.set('port', process.env.PORT || 3000);
In-order to fix this, terminate or close the server you are running. If you are using Eclipse IDE, then follow this,
Run > Debug
Right-click the running process and click on Terminate.
In my case I've had to run vagrant reload 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.
I fixed the bug by changing the port which was
app.set('port', process.env.PORT || 3000);
and changed to:
app.set('port', process.env.PORT || 8080);
Stop the service that is using that port.
sudo service NAMEOFSERVICE stop
In my case the issue was caused by forgetting to call next() in an expressjs `use' method call.
If the current middleware does not end the request-response cycle, it must call next() to pass control to the next middleware, otherwise the request will be left hanging.