Yes, you can delete all of them. I correct this issue in the upcoming update.
3 Likes
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
Am I so far behind the update hangs ?? Even a force update doesn’t really go any further
UpdateFiles.log Delete
====
2020-07-16 21:32:45 Starting UpdateFiles v1.8.16.030
2020-07-16 21:32:45 Getting files for update 1.8.16.033
2020-07-16 21:32:45 Checking for new Script files
2020-07-16 21:32:48 Checking for new JavaScript files
2020-07-16 21:33:01 Checking for new Config files
2020-07-16 21:33:05 Checking for new Panel files
2020-07-16 21:33:07 Checking for new Views files
2020-07-16 21:33:26 Checking for new Desktop files
====
2020-07-16 21:37:47 Starting UpdateFiles v1.8.16.030
2020-07-16 21:37:47 Getting files for update 1.8.16.033
2020-07-16 21:37:48 Checking for new Script files
2020-07-16 21:37:49 Getting file ==>: script/updatefiles.sh
2020-07-16 21:37:49 Checking for new JavaScript files
2020-07-16 21:37:49 Getting file ==>: /alert.js
2020-07-16 21:37:50 Getting file ==>: /altertables.js
2020-07-16 21:37:50 Getting file ==>: /archive.js
2020-07-16 21:37:51 Getting file ==>: /backfill.js
2020-07-16 21:37:51 Getting file ==>: /bucket.js
2020-07-16 21:37:52 Getting file ==>: /cwop.js
2020-07-16 21:37:53 Getting file ==>: /dailystats.js
2020-07-16 21:37:53 Getting file ==>: /mooncalc.js
2020-07-16 21:37:54 Getting file ==>: /panel.js
2020-07-16 21:37:54 Getting file ==>: /piio.js
2020-07-16 21:37:55 Getting file ==>: /pwsw.js
2020-07-16 21:37:55 Getting file ==>: /server.js
2020-07-16 21:37:56 Getting file ==>: /start.js
2020-07-16 21:37:56 Getting file ==>: /suncalc.js
2020-07-16 21:37:57 Getting file ==>: /updatefiles.js
2020-07-16 21:37:57 Getting file ==>: /util.js
2020-07-16 21:37:58 Getting file ==>: /weathercalc.js
2020-07-16 21:37:58 Getting file ==>: /windy.js
2020-07-16 21:37:58 Checking for new Config files
2020-07-16 21:37:59 Getting file ==>: config/alertT.json
2020-07-16 21:37:59 Getting file ==>: config/configT.json
2020-07-16 21:38:00 Getting file ==>: config/eventT.json
2020-07-16 21:38:00 Getting file ==>: config/piioT.json
2020-07-16 21:38:01 Getting file ==>: config/panelT.json
2020-07-16 21:38:01 Getting file ==>: config/uploadT.json
2020-07-16 21:38:01 Checking for new Panel files
2020-07-16 21:38:02 Getting file ==>: panel/index.html
2020-07-16 21:38:03 Getting file ==>: panel/index.css
2020-07-16 21:38:03 Getting file ==>: panel/index.js
2020-07-16 21:38:03 Checking for new Views files
2020-07-16 21:38:04 Getting file ==>: views/about.ejs
2020-07-16 21:38:04 Getting file ==>: views/alert.ejs
2020-07-16 21:38:05 Getting file ==>: views/config.ejs
2020-07-16 21:38:05 Getting file ==>: views/devices.ejs
2020-07-16 21:38:06 Getting file ==>: views/footer.ejs
2020-07-16 21:38:06 Getting file ==>: views/head.ejs
2020-07-16 21:38:07 Getting file ==>: views/header.ejs
2020-07-16 21:38:07 Getting file ==>: views/help.ejs
2020-07-16 21:38:08 Getting file ==>: views/index.ejs
2020-07-16 21:38:09 Getting file ==>: views/logs.ejs
2020-07-16 21:38:10 Getting file ==>: views/panel.ejs
2020-07-16 21:38:10 Getting file ==>: views/piio.ejs
2020-07-16 21:38:11 Getting file ==>: views/process.ejs
2020-07-16 21:38:11 Getting file ==>: views/server.ejs
2020-07-16 21:38:12 Getting file ==>: views/upload.ejs
2020-07-16 21:38:12 Getting file ==>: views/about.htm
2020-07-16 21:38:13 Getting file ==>: views/alert.htm
2020-07-16 21:38:14 Getting file ==>: views/config.htm
2020-07-16 21:38:14 Getting file ==>: views/devices.htm
2020-07-16 21:38:15 Getting file ==>: views/help.htm
2020-07-16 21:38:15 Getting file ==>: views/index.htm
2020-07-16 21:38:16 Getting file ==>: views/logs.htm
2020-07-16 21:38:16 Getting file ==>: views/panel.htm
2020-07-16 21:38:17 Getting file ==>: views/piio.htm
2020-07-16 21:38:17 Getting file ==>: views/process.htm
2020-07-16 21:38:18 Getting file ==>: views/server.htm
2020-07-16 21:38:18 Getting file ==>: views/upload.htm
2020-07-16 21:38:18 Checking for new Desktop files
2020-07-16 21:38:19 Getting file ==>: script/start1.sh
2020-07-16 21:38:19 Getting file ==>: script/start2.sh
1 Like
I will be working on the site and the code this weekend. I’ve been lazy this year.
1 Like
You had good reasons for that. Not in a hurry, just that Tempest is now widely deploying … and time to migrate my setup to for the Tempest
Guess we’re going to have some betafuntesting soon 
1 Like
I have three Tempest and the more reason I need to get it done.
3 Likes
You Rock Gary. Just messing around with it has given me more respect for your code than I can put to words. When you are not tying to shoehorn it into a linux install that it was not designed for, looks like it would go very smoothly.
Bit of RTFM for me, I spent 8 hours on a weak wireless signal trying to download the raspbian image this supports only to find out, the Pi4 wont boot with it. They changed the boot loader. So yeah RTFM folks, will save you hours.
1 Like
Well dang. I will order an RPi to test with.
1 Like
They deprecated Rasbian Stretch on the Pi4. It’s all Raspbian Buster now for Pi3 and Pi4
5 Likes
Well crap. Time to update.
4 Likes
tell me about it… i found out the hard way with my PI that was running pihole for years with no issues but stretch was no longer supported. Its ok tho fresh installs are nice!
2 Likes
I’ve been using archivesw with great success, awesome work. I just got a Tempest, does archivesw support the Tempest?
Haven’t seen much activity here lately… wondering if you are still supporting archivesw ?
I have two systems up and running now for years? Thank You.
I have two important questions that I need to resolve going forward.
- How can I clean the system - ie. remove all the data collected, and start anew including *.logs
- Can/Does archivesw support the Tempest module/device? I would Like to configure one of my systems for that platform.
This project is now dead.