Going to add to the additional “Bitcoin Node Not Starting” topics. Sorry ppl:
My node was working fine before upgrading to the latest version of Umbrel and updating my Bitcoin SW. Now i’m stuck starting. I’ve deleted the .json files and tried resyncing like previous posts have stated. Still not moving forward. Looking at the logs, it just seems like something is constantly failing to connect/poll. I’m getting multiple Gzip: Deflate error 0 and not able to connect. I’m very limited on my Linux skills so patience is appreciated. I’ve attached the Bitcoin logs.
I’m trying to clear out space just in case it’s a SSD space issue and when trying to clear the unused Docker data (docker system prune -a), I get the following:
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Head “http://%2Fvar%2Frun%2Fdocker.sock/_ping”: dial unix /var/run/docker.sock: connect: permission denied
Well, before you go any further, it would be a good idea to find out the cause of the problem. If you don’t know the possible cause, you’re probably making the problem worse. Something I think you’ve already done.
I’ve seen your log and it’s riddled with errors regarding your node not being able to establish a connection to sync, but with what you’ve done, it seems like you’ve made things more complicated because I don’t see any docker-related errors.
I’ll try to understand your context (correct me if I’m wrong).
You’ve upgraded to v1.3. This version has been causing a lot of problems and the possible source of the conflict.
From what you’ve posted, I assume you’re on a Raspberry PI with a 1TB drive.
With a 1TB drive you’ll need to expand your storage soon. The blockchain alone weighs 706GB right now. Your drive indicates it only has 69GB left. There’s not much time left.
Now, what I would personally do. Since you will have to change the disk to a larger one, I would install everything from scratch with the new larger disk. This way you make sure there are no previous errors.
You have 2 options left, download the blockchain again or backup it from your current disk. Then just copy/paste it, which will make the whole process faster.
Anyway, without having more information about your situation at the moment, this is what I can tell you.
Honestly, I when I saw how large the blockchain was getting, that was the first thing I thought was it was time to upgrade the SSD and start from scratch.
I have no idea what they did with the last update to v1.3. All I know is that it is causing issues when upgrading. Now, if you install v1.3 from scratch, it doesn’t cause those issues.
My nodes crashed when I tried to upgrade and I had to fix this kind of disaster by implementing certain measures. I don’t have time nor do I want to go through all this with every update.
This ain’t my first rodeo with Umbrel and their updates. I always get excited for the new updates but as soon as I select “update,” I start to get PTSD about having the reconfigure/reinstalling the OS just because of these issues.
I just updated to 1.3 and am having the same problem. This has happened every time ive updated. Normally, I reindex and everything works but this time nothing works. I reeeally don’t want to have to rebuild everything AGAIN! I don’t want to have to close my lightning channel and lose money!
If anyone comes up with something, i would greatly appreciate trying another solution, lol!
thanks for your comment. I’ve added the “reindex=1” to the conf file, but now it looks like it’s downloading the entire blockchain once again. It’s strange. Because I’m wondering where it should now place the entire blockchain, because my old blockchain which is probably not completely synchronised since >8 days, since the update to 1.3 is also still available.
How was it in your case? I understood your comment, that this will force the bitcoin node only to resync, not to download the complete blockchain once again. Also I can see no connections to Peers.
Ahh ok. It looks like in my case it’s also working. Within the last 24 hours, I’m already 21% and the space only slightly increased, so it looks it’s also going to work.
How is this going? I’ve had to do this the previous times i’ve done the OS updates…honestly, we shouldn’t have to do this everytime and update gets pushed out.
