eaddress in use

[Binog]

Hey, do have a blank screen. and the logs show:

/home/pi/.pm2/logs/mm-error.log last 15 lines:
0|mm | [01.09.2021 18:00.08.684] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
0|mm | [01.09.2021 18:09.09.021] [ERROR] Whoops! There was an uncaught exception…
0|mm | [01.09.2021 18:09.09.036] [ERROR] Error: listen EADDRINUSE: address already in use 127.0.0.1:8080
0|mm | at Server.setupListenHandle [as _listen2] (net.js:1313:16)
0|mm | at listenInCluster (net.js:1361:12)
0|mm | at GetAddrInfoReqWrap.doListen [as callback] (net.js:1498:7)
0|mm | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:68:8) {
0|mm | code: ‘EADDRINUSE’,
0|mm | errno: ‘EADDRINUSE’,
0|mm | syscall: ‘listen’,
0|mm | address: ‘127.0.0.1’,
0|mm | port: 8080
0|mm | }
0|mm | [01.09.2021 18:09.09.038] [ERROR] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm | [01.09.2021 18:09.09.039] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

this is with a clean install of Magicmirror and the sample.config.

[Binog]

@bkeyport

As the new system is running, I did change the port !

Thx !

[mumblebaj]

@binog said in eaddress in use:

EADDRINUSE

The EADDRINUSE error usually means that another instance of the mirror is running. If you start the mirror with pm2, you can do a pm2 list to show the current processes that are running under pm2. You can then stop that process with pm2 stop #id or process stop all. Then you should be able to start the mirror again.

[Binog]

@mumblebaj
Thank You for reply ! None the less, there was no other instance running, I double checked it, nore was an instance under npm running. I finally decided to format the card and start over,… thx

[BKeyport]

@binog Even though it’s fixed, there could be another issue - something else running on port 8080. I always change the default ports… 60001, 60002, etc. Less mess.

[nickthebeer]

Can you run the following commands from the CLI to check if anything is using that port

sudo netstat -punta | grep LIST
sudo netstat -punta | grep 8080

[Binog]

Thank You, Nickthebeer and BKeyport

I’ll try in future, I finally decided to reinstall the whole system.

[mumblebaj]

@binog That is a pity. We could probably have found the issue and save your current state prior to the issue. Hope it is running fine now though.

[cowboysdude]

@bkeyport 1st thing I do is change the port always :)

[BKeyport]

@cowboysdude

As well as the sample config is documented, I’m shocked that the port line is blank.

I’d totally have it:

port: 8080 // Change this! Recommended over 60000 to avoid conflict 

But, hey, I’m just a hack, ya know? 😉

[Binog]

@bkeyport

As the new system is running, I did change the port !

Thx !