When you have access, look at the Bitcoin logs, and the Electrs logs. You should download each while you have access, and leave them open on the screen. When either of them has errors in those logs, you’d have to tell us what they are. This may crash your server again, and which point you’d need to again regain access and Stop the two services while you wait for further instruction.
Got it. I will get back to you shortly. I hope.
Ok. I got back in. And it is up and running. I downloaded the Start OS logs. And it is in .txt format now. I tried downloading the logs for Core it accepts the command however nothing gets downloaded. Why is that?
Evidently Onion was blocking the downloads. Got it working. Now I have all three logs open in a notepad. And I appear to be going through IDB. But I have the same error message on Bitcoin Core.
Under health Checks it says RPC server is ready for connections. and it says “syncing blockchain 99.92%.”
I will keep watching it.
Bitcoin core service is now running green and is synced with network Electrum is still catching up.
Another update. Electrum finished and said I may connect wallet. I fired up sparrow and it automatically connected like before. So all good there. I will continue to monitor. Not disconnecting. Is there anything I should look for in the logs? Update Its been about 24 hours and no loss of connection. I am not sure what has changed but it seems to be working fine now. I will monitor for a few more days.
For it to be spotty for a short time, then be fine, makes me think this is an issue with the Tor network itself, rather than your server.
Could be. Its still working stable now. I will give an update in a few days. Update…well guys I think we are good. Its been a few days and not a hiccup. Everything is working well. I guess Stu was right. It must have been a TOR issue. Thanks for all of the help guys. I really do appreciate it. This one was tricky because I am so far away from the server. Lets call this one fixed.
I’ve been running Start9 on a Lenovo Thinkcenter M710q since last year, and it’s been running great and was solidly reliable until yesterday. Our power went out for almost four hours, and when electricity was finally restored, everything came back up except the Start9 node. I’ve booted up in kiosk mode and have tried repairing the drive, restarting the system and rebuilding the system multiple times, but nothing has been working. I’ve heard Beethoven’s 5th so many times I’m tired of the joke by now.
Good thing I made a backup of the entire system last Wednesday, so I know I can restore everything from scratch, but I’d prefer just getting it back online within the next couple of days. Any suggestions would be most appreciated.
Here is the error I see when I start up in kiosk mode:
Disk management error.
enabling repair mode Opening filesystem to check… Checking filesystem on /dev/mapper/EMBASSY_2EFTXWVBRYNUGUU7XHGUU3DY0ZBB5LAVGVHS6476HBMTVPVAYB4A_package-data UUID: ab6fllda-38c5-4cb3-b263-dabe8a9928d6 repair mode will force to clear out log tree, are you sure? [y/N]:
How do I get around this startup problem? I re-boot, repair and rebuild, but nothing changes.
You¡ll need to do this…
Looks like my Dell Start9 server failed to connect remotely again. I will try to have someone go and reboot it. I am far away again. I will let you know what I find. Stu do you think this StartOS v.0.40 will help my issue also?
Maybe. In situations where something is happening that you can’t quite determine what it is… just up and replacement a component might make the problem go away. In your case, maybe a newer linux kernel will have the fix for some obscure hardware issue, for example.
Hello Stu. I am locked out again. Getting the Onion site not found error. I have had the system reset by someone at the server. But its not coming back. I have tried clearing cache on my Tor browser. I have asked AI for troubleshooting steps. It gives me things that don’t really work. I am at kind of a loss right now. I can get to other Onion servers. I really don’t know anything about TOR. Do you have any other suggestions I can try? I got the logs off of my TOR browser and its most recent entry is “General SOCKS server failure”
That last error is one that basically means Tor on your server is disconnected and can’t connect… 99% of the time, this will be because of some issue with the Tor network. Tor is awesome in many ways, but its biggest weakness is stability.
For many people who aren’t permanently away from their server, they can always get home and reset tor that night or something, in your case if you’re always away from home, you probably need to look at implementing some other tricks prior to StartOS v0.4.0. – one I like and recommend is running a VPN server on your home router or another device on the LAN, connecting and accessing the server UI via the local IP address (i.e. 192.168.1.21)… this rudimentary access would then let you do things like reset Tor (System → Experimental Features → Reset Tor), restart services, initiate backups all without using Tor.
Thanks Stu. I appreciate the input and the ideas. I will see if I can do something. I will go back to the server in a few weeks. What happens in StartOS v0.40 that can help my specific situation?
Is there a TOR reset on the server now? You mentioned (System>Experimental Features>Reset Tor) How is this accessed?
StartOS v0.4.0 fixes this because things like the VPN I mentioned are more the default, and Tor is more an optional backup. In v0.4.0. setting up this stuff will be done by a nice GUI and there’ll be guides to do it. With v0.4.0 should anything go wrong networking wise it’ll be external to the server, since everything the server will do will be much more in the realms of “run-of-the-mill”.
Thats fantastic Stu. This seems like a massive change. I am so looking forward to this. When do you think this will be released for general distribution? Any estimates?
Any estimate would either hopium or a lie.
I think it’s reasonable to expect a stable beta this side of the new year. In fact, there’s a stable alpha version in testing that some people are using now.
Gotcha. I will be anxiously looking for it.