events.js:160 throw er; // Unhandled 'error' event

[nickjf89-zz]

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!

• You're running version >=2.1.4 of Parse Server.
• You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Steps to reproduce

Logs/Trace

Note: If you get a browser JS error please run npm run dev. This will provide source maps and a much more useful stack trace.

events.js:160
throw er; // Unhandled 'error' event
^

Error: listen EADDRINUSE 0.0.0.0:4040
at Object.exports._errnoException (util.js:1007:11)
at exports._exceptionWithHostPort (util.js:1030:20)
at Server._listen2 (net.js:1253:14)
at listen (net.js:1289:10)
at net.js:1399:9
at _combinedTickCallback (internal/process/next_tick.js:77:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

[drew-gross]

That error means you are already running something else on port 4040. Maybe another copy of the dashboard?

[bcarlis]

Thanks Drew! EADDRINUSE does say ADDRess IN USE
I changed 8081 in my example to 7878 that I've used before that I knew was open and all is well.

[srinivas69]

Then how to stop the already running dashboard

[nickjf89-zz]

killall -9 node

[codedcontainer]

This is interesting because I do have anything that shows that I have another process running on another port. @nickjf89 I've tried to use this command, but there are no processes that can be found. I get this error when I use gulp, "gulp wiredep"

[robbonghi]

probably port is already in use so try below code
sudo pkill node

[Kimosabe2015]

Having same problem... events.js:160 throw er; // Unhandled 'error' event
Error: listen EADDRINUSE 127.0.0.1:8000

But when I enter sudo or killall command I get :command not found?

How do I download the proper commands for MinGW64 using the MinGW Installation Manager so I can use these commands? And once downloaded how do I install them so they work in Git-Bash?

[hmuschett]

run de server on other port

[bakhodir10]

good job, @drew-gross .Thanks a lot

[sanris]

If the running instances belongs to your project then.

Option #1
restart the system.

Option #2
goto command prompt and try the following command.

taskkill /f /im node*

Credits
Thanks to Bageerathan

[Cob007]

events.js:160
throw er; // Unhandled 'error' event
^

Error: connection timeout
at Db. (C:\Users\user\WebstormProjects\loginapp\node_modules\mongoose\lib\drivers\node-mongodb-native\connection.js:169:17)
at emitTwo (events.js:106:13)
at Db.emit (events.js:191:7)
at Server.listener (C:\Users\user\WebstormProjects\loginapp\node_modules\mongoose\node_modules\mongodb\lib\db.js:1786:14)
at emitOne (events.js:96:13)
at Server.emit (events.js:188:7)
at Server. (C:\Users\user\WebstormProjects\loginapp\node_modules\mongoose\node_modules\mongodb\lib\server.js:274:14)
at emitOne (events.js:96:13)
at Server.emit (events.js:188:7)
at Pool. (C:\Users\user\WebstormProjects\loginapp\node_modules\mongoose\node_modules\mongodb-core\lib\topologies\server.js:334:12)
at emitOne (events.js:96:13)
at Pool.emit (events.js:188:7)
at Connection. (C:\Users\user\WebstormProjects\loginapp\node_modules\mongoose\node_modules\mongodb-core\lib\connection\pool.js:270:12)
at Connection.g (events.js:291:16)
at emitTwo (events.js:106:13)
at Connection.emit (events.js:191:7)
at Socket. (C:\Users\user\WebstormProjects\loginapp\node_modules\mongoose\node_modules\mongodb-core\lib\connection\connection.js:183:10)
at Socket.g (events.js:291:16)
at emitNone (events.js:86:13)
at Socket.emit (events.js:185:7)
at Socket._onTimeout (net.js:339:8)
at ontimeout (timers.js:365:14)

please can anyone help me with this error???????????????????????????????????????????????

[FabMpenge]

#Cob007 I had the same issue as you during 5 days, so reading all above resolves then I found npm command killall -9 node proposed by #nickjf89. Then the issue was fixed

[Ronakpatel9994]

events.js:160
throw er; // Unhandled 'error' event
^

Error: spawn cmd ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
This is error occured when run this code
[nodemon server.js ]

Here in this proble We can run the code in another cmd Prompt and run the server successfully but if we want the continue server run then its throw the error while use ing the command in cmd
nodemom server.js

[Parveenkmr44]

Use this code to kill current port process

sudo lsof -i :8080
sudo kill -9 PID

I am using 8080 and you change it by your port that you are using in your project.