Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: listen EADDRINUSE :::51826

See original GitHub issue

Since today i got an new error… absolutely no idea where is it coming from.

`HAP-NodeJS starting… Parsing accessory: Fan_accessory.js Parsing accessory: GarageDoorOpener_accessory.js Parsing accessory: Light_accessory.js Parsing accessory: Lock_accessory.js Parsing accessory: MotionSensor_accessory.js Parsing accessory: Outlet_accessory.js Parsing accessory: TemperatureSensor_accessory.js Parsing accessory: Thermostat_accessory.js events.js:141 throw er; // Unhandled ‘error’ event ^

Error: listen EADDRINUSE :::51826 at Object.exports._errnoException (util.js:874:11) at exports._exceptionWithHostPort (util.js:897:20) at Server._listen2 (net.js🔢14) at listen (net.js:1270:10) at Server.listen (net.js:1366:5) at EventedHTTPServer.listen (/home/pi/HAP-NodeJS/lib/util/eventedhttp.js:60:19) at HAPServer.listen (/home/pi/HAP-NodeJS/lib/HAPServer.js:158:20) at Accessory.publish (/home/pi/HAP-NodeJS/lib/Accessory.js:496:16) at /home/pi/HAP-NodeJS/Core.js:32:13 at Array.forEach (native)`

Issue Analytics

State:
Created 7 years ago
Comments:6

Top GitHub Comments

1reaction

Maxmudjoncommented, Jan 29, 2017

terminal: killall node

1reaction

heuelscommented, Jan 27, 2017

Hey, @StefanMeGit. I’m almost certain it means you already have HAP-NodeJS running on your machine. Run ps aux | grep node and look in the output for PID of Core.js.

Then just kill -9 PID it.