Updated from 7.7.0 to 8.0.0 and now cannot connect (or it disconnects after a minute and never reconnects)

[Candurin]

I had no luck in getting any sort of logs to work. Here is the output when I try and start pool controller and dash panel:

Pool Controller:

pi:~/nodejs-poolController/data $

[email protected] start
npm run build && node dist/app.js

[email protected] build
tsc

[6/5/2023, 3:39:44 PM] info: Starting Replay Capture.
Init state for Pool Controller
[6/5/2023, 3:39:44 PM] info: The current git branch output is master
[6/5/2023, 3:39:44 PM] info: The current git commit output is 64743d6
[6/5/2023, 3:39:44 PM] info: Starting up SSDP server
Error: listen EADDRINUSE: address already in use 0.0.0.0:4200
at Server.setupListenHandle [as _listen2] (node:net:1740:16)
at listenInCluster (node:net:1788:12)
at doListen (node:net:1937:7)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

DashPanel:

pi:/nodejs-poolController-dashPanel $ npm start&
[1] 2909
pi@pi:/nodejs-poolController-dashPanel $

[email protected] start
npm run build && node dist/app.js

[email protected] build
tsc

Updated configuration file
node:events:491
throw er; // Unhandled 'error' event
^

Error: listen EADDRINUSE: address already in use 0.0.0.0:5150
at Server.setupListenHandle [as _listen2] (node:net:1740:16)
at listenInCluster (node:net:1788:12)
at doListen (node:net:1937:7)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
at emitErrorNT (node:net:1767:8)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '0.0.0.0',
port: 5150
}

Node.js v18.16.0

Note: Everything was working fine in 7.7.0 but all broke after my update. Any help would be appreciated.

[tagyoureit]

The EADDRIINUSE means you already have an instance of dashPanel (at port 5150) and njsPC (at port 4200) already running. Either you didn't stop/restart the services before updating them or you created another parallel installation and started both 7.7 and 8.0 at the same time.

[tagyoureit]

If you are using PM2 than you can't use nodejs-poolController-dashPanel $ npm start& at the same time. This will start a second instance of dashPanel (or respectively, njsPC if you run the command in that directory as well).

[Candurin]

Do you recommend using PM2 or creating the local startup file with the nom start& commands?

At this point I have deleted and reinstalled everything. Now I can't get the connection to NOT disconnect.

[Candurin]

Seems like this is all related to the fact nothing is booting at startup. If I start each manually, it's fine:

pi 1797 2.0 5.3 171080 50824 pts/0 Sl 21:56 0:04 npm start
pi 1812 0.0 0.0 1940 360 pts/0 S 21:56 0:00 sh -c npm run build && node dist/app.js
pi 2093 4.0 5.4 170912 51352 pts/1 Sl 21:58 0:04 npm start
pi 2104 0.0 0.0 1940 368 pts/1 S 21:58 0:00 sh -c npm run build && node dist/app.js
pi 2393 0.0 0.0 7344 576 pts/2 S+ 22:00 0:00 grep --color=auto npm

But nothing is running when I reboot, despite my rc.local file being correct:

fi

cd ~/nodejs-poolController

npm start&​

cd ~/nodejs-poolController-dashPanel

npm start&​

exit 0

Please note that I deleted "pi" from the directory names (cd ~pi/nodejs-poolController-dashPanel) as my directory structure is as above. Additionally, I have tried with "pi" in the directory and it makes no difference

[tagyoureit]

See https://github.com/tagyoureit/nodejs-poolController/wiki/Automatically-start-at-boot---PM2-&-Systemd for the PM2 instructions and another method.

[Candurin]

Just wanted to thank you for the help. Switched to PM2 and everything working perfectly!