Edit: did a rebuild from scratch on new Raspbian Buster - all is fixed.
I’m glad you got it working. I have spent hours searching and testing to find a solution and I have no answers.
So far so good. Both up and running great.
Have you been able to add the UThing device to ArchiveSW ?
I have one ready to plug in and activate.
How do I go about deactivating the auto start for ArchiveSW?
Hi @GaryFunk,
A few days ago my raspberry pi stopped responding to my mouse and keyboard and I could not log in remotely. So I turned off the power. Once it started I checked that it was working but I didnt notice that the archive stopped working correctly. It keeps restarting. These are sections of the archive.log file from when it was working correctly:
2019-09-18 08:00:00 Archive is running
2019-09-18 09:00:00 Archive is running
2019-09-18 14:47:17 Starting Archive v1.8.16.111
2019-09-18 14:47:17 TCP client active on: 127.0.0.1:50514 to 127.0.0.1:9090
====
2019-09-18 23:59:59 Starting Archive v1.8.16.111
2019-09-18 23:59:59 TCP client active on: 127.0.0.1:53180 to 127.0.0.1:9090
2019-09-19 00:00:00 Starting Archive v1.8.16.111
2019-09-19 00:00:00 TCP client active on: 127.0.0.1:53188 to 127.0.0.1:9090
2019-09-19 00:00:09 appRestart : :
2019-09-19 00:00:10 piReboot : :
2019-09-19 00:20:53 Error in insertObsSky (1): HA_ERR_CRASHED_ON_REPAIR: Table ‘./wfarchive/SkyObservation’ is marked as crashed and last (automatic?) repair failed
2019-09-19 00:20:54 Starting Archive v1.8.16.111
2019-09-19 00:20:54 TCP client active on: 127.0.0.1:53216 to 127.0.0.1:9090
2019-09-19 00:21:03 appRestart : :
2019-09-19 00:21:25 Error in insertObsSky (1): HA_ERR_CRASHED_ON_REPAIR: Table ‘./wfarchive/SkyObservation’ is marked as crashed and last (automatic?) repair failed
====
2019-09-21 16:07:47 Starting Archive v1.8.16.111
2019-09-21 16:07:47 TCP client active on: 127.0.0.1:38988 to 127.0.0.1:9090
2019-09-21 16:07:56 appRestart : :
2019-09-21 16:08:18 Error in insertObsSky (1): HA_ERR_CRASHED_ON_REPAIR: Table ‘./wfarchive/SkyObservation’ is marked as crashed and last (automatic?) repair failed
I am guessing that I have corrupted the database table SkyObservation.
Do you have any suggestions that would help me to fix it?
cheers Ian
The SkyObservation table is damaged…I’ll send you a script to correct that.
@GaryFunk
Hey Gary,
Just an fyi.
also maybe related the bash statement no longer works for me.
bash -e <(wget -qO - http://fsoft.com/archivesw/script/install.sh)
Nore does the update bash
bash -e <(wget -qO - http://fsoft.com/archivesw/script/updaterpi.sh)
Chuck
It’s the certificate. I’ll get it fixed late tonight.
No hurry bud, was just letting you know.
I appreciate the message. I’m sitting on a craft in Charlotte waiting to get to Denver.
think I also have a crashed table
2019-10-12 14:38:39 Error in insertHubStatus (4): HA_ERR_CRASHED_ON_REPAIR: Table ‘./archivesw/HubStatus’ is marked as crashed and last (automatic?) repair failed
2019-10-12 14:38:39 Error in insertRapidWind (1): HA_ERR_CRASHED_ON_REPAIR: Table ‘./archivesw/RapidWind’ is marked as crashed and last (automatic?) repair failed
maybe time to think for a general optimising/repair script ???
Yes, I’ve been working on that. I’ll get you a file to fix that.
I had to start over with my RPi due to corruption of the fs (UPS didn’t work as planned). Because of that, I need to re-install ArchiveSW. It seems like the certificate issue is still there. Due to that, the RPi won’t run the bash/wget script to install.
No big hurry… just wanted to add another task to your list.
Thanks again for your work on this!
I plan to try this, once the certificate problem is resolved.
Oh crap. Let me set a reminder to do that when I get home. Sorry I let this go. I keep forgetting.
The certificates are updated. Let me know if you have any issues.
The site has been updated.
Thanks Gary. I’ll get it re-installed later today.
Gary,
So I got it to install but it seems like there are some errors preventing it from running. Here’s my chain of events…
- Performed updates and installed npm per the instructions
- Ran the bash script
- The webpage and panel came up, ready to configure
- Instead of manually entering all of the info, I replaced all of the files in the config folder using a backup that I had made before wiping my system (maybe this is the issue??)
- Verified that the fields were correct in the configuration web pages
- Ran the update from the web page
- Restarted all of the services from the process panel
- Now, nothing works. No web page at :8080
I’ll send you a PM with my log files.