EADDRINUSE: address already in use 127.0.0.1:8090

theaddies

When I boot up the MagicMirror I will get a blank screen with a cursor. The message in the log is the following. If I simply change the port to anything else, 8080 then the mirror boots up fine. If I get the error I switch it back to 8090 and it goes away again. I have nothing running on the machine. It is a raspberry pi II with only MagicMirror. TIA

/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|MagicMir | [19.02.2023 07:55.11.006] [ERROR] Error: listen EADDRINUSE: address already in use 127.0.0.1:8090
0|MagicMir |     at Server.setupListenHandle [as _listen2] (node:net:1432:16)
0|MagicMir |     at listenInCluster (node:net:1480:12)
0|MagicMir |     at GetAddrInfoReqWrap.doListen [as callback] (node:net:1629:7)
0|MagicMir |     at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:111:8) {
0|MagicMir |   code: 'EADDRINUSE',
0|MagicMir |   errno: -98,
0|MagicMir |   syscall: 'listen',
0|MagicMir |   address: '127.0.0.1',
0|MagicMir |   port: 8090
0|MagicMir | }
0|MagicMir | [19.02.2023 07:55.11.008] [ERROR] MagicMirror² will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|MagicMir | [19.02.2023 07:55.11.010] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
0|MagicMir | [2472:0219/075514.107308:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
0|MagicMir | [2505:0219/075514.639247:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

sdetweil

@theaddies that means something is using the port , maybe you have two instances of mm trying to run

do

pm2 status

are there 2 apps defined?

theaddies

@sdetweil Thanks for the reply. I think I did have 2 instances at one time, but I deleted the other one. It does not show up on pm2 status. Is there anything else to remove? Thansk.

sdetweil

@theaddies look for running processes

pm2 stop all
ps -ef | grep node

or

ps -ef | grep npm

theaddies

@sdetweil I found /usr/bin node serveronly.

is that the culpirit?

theaddies

@sdetweil I suppose this makes sense but I killed it and it immediately restarted. I don’t know how to remove it.

sdetweil

@theaddies you must have added it as part of the manual install instructions

do the reverse to take it out…

theaddies

@sdetweil thanks for the reply but I have no idea what I see did

sdetweil

@theaddies sorry. no idea myself.

I gave up long ago trying to remember the 900 different ways to auto start things on the myriad different platforms.