I have been running a bitcoin core and LND node on Start9 for a while now. I had some major difficulty with bitcoin core remaining in a continuing state of "starting" after full sync. I uninstalled and started again, and everything has been fine for months. Yesterday I updated bitcoin core to 28-00-1. Once again I am having this problem, which of course screws up electrs, LND, and Alby Hub too. Has anyone else experienced this? Suggestions?
pull down to refresh
51 sats \ 5 replies \ @fiatbad 8 Jan
I updated everything on mine about an hour ago. No issues.
But if I'd seen your post first, I probably would have waited a bit longer to update!
Hope the re-install fixes you up.
reply
0 sats \ 4 replies \ @siggy47 OP 8 Jan
Thanks
reply
41 sats \ 3 replies \ @fiatbad 14 Jan
Just for the sake of my own curiosity.... did you ever get things straightened out?
reply
0 sats \ 2 replies \ @siggy47 OP 14 Jan
Funny you should ask. As I said, I uninstalled bitcoin core, LND, and electrs. Well, I decided to completely uninstall all of my server apps too, and just use the device for my node. Core synced quickly and is running fine. LND, on the other hand, is now continually restarting like core had been. Since I didn't get to the point of opening any channels, I will probably wipe the drive and start again. I checked the hardware. It seems to be functioning fine.
reply
41 sats \ 1 reply \ @fiatbad 14 Jan
Did you check the LND logs?
This past week I set up a new Start9 node, and LND would NOT connect to any peers to sync the chain. A full week went by and it just kept giving the same log error.
I finally resolved it by manually adding it as a peer to my primary node. Once LND had one peer to talk to, it was able to sync within a few hours. Simple.
Maybe it's the same issue you're having? If so, you can add my node as a peer if you want. Just DM me.
Also, I had tons of issues with LND syncing when I was using one of Start9's raspberry Pi nodes from a few years back. It was not powerful enough, and the Start9 team told me so straight up. That's probably why they stopped selling those low powered machines. Can you imagine if we were trying to run BCH nodes?! Fucking nightmarish.
reply
0 sats \ 0 replies \ @siggy47 OP 14 Jan
Thanks for the advice! I have another node, so I will give it a try. Just so you know, I'm using a Start9 server, which should be powerful enough.
reply
62 sats \ 18 replies \ @nym 8 Jan
What does the log show when it stops?
reply
6 sats \ 11 replies \ @siggy47 OP 8 Jan
I should have checked. I just uninstalled it.
reply
41 sats \ 10 replies \ @nym 8 Jan
Not a bad idea. Sometimes it is easier to start fresh anyway.
reply
0 sats \ 0 replies \ @ama 8 Jan
Usually not necessary if you aren't running MICROS~1 software.
reply
0 sats \ 8 replies \ @siggy47 OP 8 Jan
Last time this happened I spent days on forums, reading guides, etc, with no clear-cut answers. I did discover that I'm not the only one experiencing the issue.
reply
51 sats \ 7 replies \ @DarthCoin 8 Jan
Like nym said, first thing you need to look into logs. Both bitcoin and electrs. Sometimes bitcoin take long time to catch up the blocks and indexes from the moment you stop it to update. Electrs is waiting for bitcoin to finish and then it start its own index that also can take for a while.
Meanwhile all other dependent services like LN node are just waiting.
Maybe you have a bad sector of that drive and is hanging.
Maybe some new settings for new update you need to do, be aware of this PSA from LND guys, valid for core 28.0.1 with LND.
https://xcancel.com/roasbeef/status/1842956355516223824
reply
0 sats \ 6 replies \ @siggy47 OP 8 Jan
I guess it's possible that I didn't wait long enough, but it took a while to say "running", then it switched to "starting" about an hour later.
reply
41 sats \ 5 replies \ @DarthCoin 8 Jan
logs. You need logs, otherwise we are just guessing around.
reply
110 sats \ 4 replies \ @siggy47 OP 8 Jan
This is exactly what I am dealing with:
https://community.start9.com/t/bitcoin-core-continually-status-starting/1852
view replies
0 sats \ 5 replies \ @siggy47 OP 9 Jan
Sorry. I got busy. I don't know if this helps:
reply
41 sats \ 4 replies \ @nym 9 Jan
Crashes with exit code 1 can sometimes be due to insufficient resources such as memory, CPU, or disk space.
You could try starting each app sequentially instead of all at once if possible with StartOS.
reply
0 sats \ 3 replies \ @siggy47 OP 9 Jan
Thanks
reply
41 sats \ 2 replies \ @nym 9 Jan
I tried StartOS and Umbrel a while back. They are nice it just always felt slow like I was working in a VM because it was slow, and I wasn't sure how everything worked in the background. Now I just recommend raw dogging it on a spare laptop running Debian, Bitcoin Core, Fulcrum or Electrs, and the wallet of your choice. And don't forget to install your firewall like gufw.
reply
0 sats \ 1 reply \ @siggy47 OP 9 Jan
I'm sure you're right. I have to bite the bullet and just do it.
reply
41 sats \ 0 replies \ @nym 9 Jan
I understand being cautious. I mean we are talking about real money.
Bitcoin Core has a binary to install now and once the chain syncs the only thing you really need to adjust if needed is the bitcoin.conf file. The electrum server only usually that config file changed.
reply
41 sats \ 2 replies \ @0xbitcoiner 8 Jan
If this is the message: “Server is still in the process of starting”
reply
33 sats \ 1 reply \ @siggy47 OP 8 Jan
No, that's not the message. Core is just continually starting. Last time it happened it went on for weeks. FYI, sync was complete and everything was working fine for months before that.
reply
62 sats \ 0 replies \ @0xbitcoiner 8 Jan
reply