bitcoin-qt shut down while downloading the blockchain

[ujiko]

Hello,
I'm on ubuntu 22.04LTS and before i was on ubuntu 20.04LTS.
Bitcoin27.1.0 works bad, after half an hour it shut down while downloading the blockchain until may 2024.
So a human presence is needed, i must sleep you know, what can i do to let the software working by night?
This appears after a crash of my database, now i was late for 17 weeks and the default progress without peers is only 0.02% per hour.
thank you for your help.

[BlackHatCoiner]

• Would be comfortable showing us the debug.log? This probably tells what the problem is.
• Had your node synced until May 2024, and then it suddenly shut down? Did you maybe configure it and restart it at some point?
• Have you tried running ./bitcoind instead of ./bitcoin-qt?

[LoyceV]

Why not continue in your earlier topic?
Start by responding to this:

So this is a tip : select your peers, it's very very important, you must disconnect who lock your downloading process

I've never had to manually block peers. It normally works fine on it's own.

Well i had to restart a new blockchain, but curiously when 2024arrive, the ratio of downloading fail under 0.02% per hour

I'm pretty sure this is just due to your Hard Drive being the bottleneck

Agreed. In 2024, Ordinal spam caused chainstate to grow fast. If you don't have enough RAM and use an SSD, this is going to be very slow. I (still) have my blocks directory on HDD, but chainstate has been on SSD for years. That makes a huge difference in download speed, while it doesn't take too much space on your SSD.
If you don't have an SSD: buy one

Chances are your hardware doesn't like what Bitcoin Core is demanding.

[ujiko]

Well i run bitcoin-qt on a ssd disk so that is not the problem.
Does bitcoind work as same as bitcoin-qt for download blockchain?
here is a crash log ;

2024-09-15T14:17:37Z Socks5() connect to 2003:f7:570b:1f25:864b:2561:42ae:59d3:8333 failed: general failure
2024-09-15T14:17:52Z UpdateTip: new best=0000000000000000000082ba91a65ce28885b541dad95a60884fb95b3780a643 height=843465 version=0x21b98000 log2_work=94.923637 tx=1004840591 date='2024-05-14T19:34:04Z' progress=0.934651 cache=91.1MiB(755673txo)

[LoyceV]

the default progress without peers is only 0.02% per hour.

You can't have any progress without peers.

Well i run bitcoin-qt on a ssd disk so that is not the problem.

Share a bit more information: start with system specs and debug.log.

Does bitcoind work as same as bitcoin-qt for download blockchain?

Yes.

[ujiko]

the default progress without peers is only 0.02% per hour.

You can't have any progress without peers.

Well i run bitcoin-qt on a ssd disk so that is not the problem.

Share a bit more information: start with system specs and debug.log.

Does bitcoind work as same as bitcoin-qt for download blockchain?

Yes.

This is wrong the progress exist without peers but it's extremely slow.
So now i am trying to work with bitcoind and i will be back if it crashed too.

[BlackHatCoiner]

Does bitcoind work as same as bitcoin-qt for download blockchain?

Yes, it's just that bitcoind gives you immediate logs in the console.

2024-09-15T14:17:37Z Socks5() connect to 2003:f7:570b:1f25:864b:2561:42ae:59d3:8333 failed: general failure
2024-09-15T14:17:52Z UpdateTip: new best=0000000000000000000082ba91a65ce28885b541dad95a60884fb95b3780a643 height=843465 version=0x21b98000 log2_work=94.923637 tx=1004840591 date='2024-05-14T19:34:04Z' progress=0.934651 cache=91.1MiB(755673txo)

No signals of an error in here, apart from failure to connect to a node. If the problem is that you cannot connect to any node (or that you rarely connect), try setting up a hidden service, because there may be problems with your IP. It had worked with me in the past.

In bitcoin.conf:

Code:

onlynet=onion
proxy=127.0.0.1:9050

https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service

[ujiko]

Apparently, the disk usage of bitcoind is lighter than bitcoin-qt, i can see it directly on the disk led.

[LoyceV]

Apparently, the disk usage of bitcoind is lighter than bitcoin-qt, i can see it directly on the disk led.

That only means it's doing less.

[ujiko]

In bitcoin.conf:

Code:

onlynet=onion
proxy=127.0.0.1:9050

https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service

This doesn't explain me why bitcoin-qt crashed but it help very much for downloading the blockchain! Thank you sir.

[nc50lc]

This doesn't explain me why bitcoin-qt crashed -snip-

May be related to Bitcoin-qt's lag during heavy script verifications and your system.

Can you check if your 'journal' has any log related to Bitcoin Core's crash?
Use the terminal and use the command: journalctl --since "date time" --until "date time" (date time in: YYYY-MM-DD HH:MM:SS format)
Set a good range to cover the date and time when Bitcoin Core crashed.

But bitcoind shouldn't be affected by the issue if it's caused by your system killing Bitcoin Core.

[ujiko]

I believe bitcoin-qt does a memory violation because it buffering the tx before saving it in datadir, so i bypass this by using bitcoind which save directly the blocks in datadir. Thank you for the tip.

[ujiko]

bitcoind crashed too after 217MiB downloaded and there is nothing mentioned in journalctl! So i'm going to install an older version of bitcoin core.

[nc50lc]

I believe bitcoin-qt does a memory violation because it buffering the tx before saving it in datadir, so i bypass this by using bitcoind which save directly the blocks in datadir. Thank you for the tip.

There's no difference in Bitcoin-qt and bitcoind's internal working, Bitcoin-qt basically has bitcoind running in the background controlled with GUI elements.
The suggestions was based on the lingering issue of Bitcoin-qt freezing during heavy script verifications that may have been a flag for the system to kill it.

Talking about buffering, for UTXO set;
If you didn't set a custom dbbatchsize, it'll write from dbcache to datadir in 16MiB batches.
If your dbcache is high, you can experiment with higher size like dbbatchsize=1073741824 for 1GiB batches.

bitcoind crashed too after 217MiB downloaded and there is nothing mentioned in journalctl! So i'm going to install an older version of bitcoin core.

You probably deduced this already, but in that case, it has something to do with the normal IBD process, not just an issue with bitcoin-qt.
But since there's no logs provided, people can only do guesswork.

Do you have any other settings in your bitcoin.conf file that can cause instability depending on the hardware?
e.g.: par, dbcache, dbbatchsize, etc. / your machine's specs.

Also (since this mostly an isolated case), consider a hardware issue, try stress-testing your machine's RAM, CPU, HDD.

[ABCbits]

bitcoind crashed too after 217MiB downloaded and there is nothing mentioned in journalctl! So i'm going to install an older version of bitcoin core.

As stated by other member, check debug.log file which generated by Bitcoin Core. You can find that file on directory which store blockchain file. And unless you start bitcoind using SystemD service, AFAIK log produced by bitcoind wouldn't shown on journalctl.

[ujiko]

Talking about buffering, for UTXO set;
If you didn't set a custom dbbatchsize, it'll write from dbcache to datadir in 16MiB batches.
If your dbcache is high, you can experiment with higher size like dbbatchsize=1073741824 for 1GiB batches.

That interesting me because with every crash give up more than 200MiB lost, so can i ask to bitcoind to set dbcachesize explicitly?

Do you have any other settings in your bitcoin.conf file that can cause instability depending on the hardware?
e.g.: par, dbcache, dbbatchsize, etc. / your machine's specs.

Also (since this mostly an isolated case), consider a hardware issue, try stress-testing your machine's RAM, CPU, HDD.

This is not a hardware problem because i used to run bitcoin core since 2022, but after a mistake i lost all the db. The problem came when the timestamp of the txo start in april 2024.
Note that any version of the bitcoin core do the same error.

[LoyceV]

This is not a hardware problem because i used to run bitcoin core since 2022, but after a mistake i lost all the db. The problem came when the timestamp of the txo start in april 2024.
Note that any version of the bitcoin core do the same error.

Your logic to rule out hardware errors is flawed.

[ujiko]

Here is my hardware (2 years old), i put it on my board to not use your memory storage ;
https://www.kohaku.fr/phpBB3/viewtopic.php?t=9
Here is my software ;
https://www.kohaku.fr/phpBB3/viewforum.php?f=2

[Cricktor]

I run Ubuntu 22.04.5 LTS on a Lenovo Thinkpad T520 with 8GB RAM and a sort of ancient CPU Intel® Core™ i5-2520M. I'm still on Bitcoin Core v26.0.0 installed from binaries from bitcoincore.org, not from the Snap store. Storage is an internal 1TB SATA SSD.

I can report that my system and Core runs for days or weeks continuously. I reboot it only when a reboot is required after installation of certain updates that ask for a reboot. Of course I shutdown bitcoind gracefully before I reboot. Currently my Bitcoin Core started last time on August 22^nd and from then on 24/7...

I didn't observe issues during IBD (which is years ago, so not comparable with OPs situation), nor if I have to rescan the blockchain when I fiddle around with some old or new wallets that I create for specific reasons. Of course my rock-solid experience is only for the version of Bitcoin Core that I run, but I doubt that v27.1.0 would behave less stable.

I will upgrade my Core on this machine soonish and can report back after a week or two of 24/7 runtime.


P.S.
I installed my Ubuntu from an official Ubuntu image downloaded from ubuntu.com, all software or images are checked via checksums and/or signatures.

[ujiko]

i believe ubuntu is not clean and maybe have a backdoor.
i don't know how to catch the fault when bitcoind crash (which is not a snap)
in fact it's easy to upgrade bitcoin core, i just did it ;

tar xzf bitcoin-27.1-x86_64-linux-gnu.tar.gz
sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-27.1/bin/*

My mistake on the old db is to have run bitcoin-qt with 1 sudo, fatal error.