ArchiveSW - Display & Data Archive Storage

Developers Third-Party Integrations
, , ,
1624

Well I got my Tempest a few months ago. In that time life has changed. I can no longer access the internet (I can but it’s difficult.) I had been gifted a PiV4B recently and I’ve been playing around with it for a while. Boots to USB SSD etc…

The Pi was at the time running the most updated OS and since I really don’t have a way to re-download the older OS This is what I am working with:

PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL=“”
SUPPORT_URL="
BUG_REPORT_URL=“”
pi@raspberrypi:~ $ node -v
v12.18.2

I’ve been pounding my head against arcivesw for a while. Not a Linux guru but I have managed to get it running mostly. I have the server starting after reboots…you have no idea how many re-installs I did… That’s all sorted. The main issue I have now is that I have no data in the tables. Reading a posts here I noticed it was a problem with the node… needs to be 10. I also have these puzzling errors in a few of the logs.
Archive.err

 Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
     at healthCheck (dgram.js:888:11)
     at Socket.close (dgram.js:710:3)
     at hubExit (/home/pi/archivesw/archive.js:1247:6)
     at onExit (/home/pi/archivesw/archive.js:1239:2)
     at process.<anonymous> (/home/pi/archivesw/archive.js:1219:5)
     at process.emit (events.js:327:22) {
   code: 'ERR_SOCKET_DGRAM_NOT_RUNNING'
 }

Server.err

Error: listen EADDRINUSE: address already in use :::8080
at Server.setupListenHandle [as _listen2] (net.js:1313:16)
at listenInCluster (net.js:1361:12)
at Server.listen (net.js:1447:7)
at Object. (/home/pi/archivesw/server.js:62:12)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Object. (/usr/local/lib/node_modules/pm2/lib/ProcessContainerFork.js:32:23)
at Module._compile (internal/modules/cjs/loader.js:1138:30) {
code: ‘EADDRINUSE’,
errno: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘::’,
port: 8080
}
Panel.err
Error: listen EADDRINUSE: address already in use :::8089
at Server.setupListenHandle [as _listen2] (net.js:1313:16)
at listenInCluster (net.js:1361:12)
at Server.listen (net.js:1447:7)
at run (/home/pi/archivesw/panel.js:105:13)
at f1 (/home/pi/archivesw/panel.js:30:2)
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
code: ‘EADDRINUSE’,
errno: ‘EADDRINUSE’,
syscall: ‘listen’,
address: ‘::’,
port: 8089
}
Error [ERR_SOCKET_DGRAM_NOT_RUNNING]: Not running
at healthCheck (dgram.js:888:11)
at Socket.close (dgram.js:710:3)
at hubExit (/home/pi/archivesw/panel.js:344:6)
at onExit (/home/pi/archivesw/panel.js:336:2)
at process. (/home/pi/archivesw/panel.js:310:5)
at process.emit (events.js:327:22) {
code: ‘ERR_SOCKET_DGRAM_NOT_RUNNING’
}

I am not expecting miracles and it might be some time before I can come and check this post again to see if by some small chance you have an answer. I am an IT person so well aware that things are designed for platforms and attempting to disrupt that well… bad things happen. I really would like to make use of my tempest since its pretty much relegated to a real time sensor now. If anyone can fix it you are my hero!

1 Like