Hello Guys, I installed my Start OS server on a Dell Mini about two months ago. And it was working splendid for a while. I set it with Bitcoin Core. And had a remote access via TOR. I travel frequently and it was doing just fine. I had saved the Onion address and used it from my TOR Browser saved in there. Then all of a sudden this week. I cannot access it. I have tried it several times and cleared out everything on my laptop to make sure nothing was interfering. I also confirmed TOR was working and connected to other services such as BOLTZ. All other services are working fine. Just my remote Start OS server. The error is Onion Site not Found. Which indicates most likely the site is offline. I don’t have a good technical person near the server. And I am thousands of miles away. Any ideas on how to troubleshoot this? I am down to just having them restart the server. Does the Onion address stay the same? Or will it cycle to another address?
Indeed, the onion address should stay the same. Just have whoever is there power cycle your server and I’d suspect you’ll be fine. Let us know how it goes!
Thanks datamaycare. The reboot worked. It appeared to just be offline. Probably been sitting offline for a week now.
Electrum server has an error under sync status it says “RPC error code 28 verifying blocks.”
And Bitcoin Core has under RPC and Synced categories it has the blue starting swirly. I figure it is just catching up with all of the new blocks.
I will give it a while.
Well it failed to connect again. It was going through its IDB since it had been offline for about a week. And it seemed to have connection to all services just waiting on IDB. So I disconnected my TOR connection and went to bed. Unfortunately when I check this morning it was unreachable again. I don’t understand. I have a good stable internet connection at the server. Any ideas on what is happening? If I can get it running again is there anything in the logs I should be looking for? When I did the server install I went through multiple power cycles with it. Testing it for potential power failures. And it never had a problem. I wonder what may be causing this? Any sugesstions?
You mention errors and crashing services on your server. I’d suspect these are severe enough to take down network connectivity. You may need to do the same as previously, but this time stop Electrs and Bitcoin to take a better look at what’s wrong with them.
Ok. Thanks for the advice StuPleb. I will do this. As soon as I corral someone to restart it for me. Could you please offer suggestions on what to take a look at? Where should I start?
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.