Issue Details

Number

31882

Title

bitcoind shouldn't fail to progress with synchronization: endless [leveldb] Generated table ... logs

Description

### Is there an existing issue for this? - [x] I have searched the existing issues ### Current behaviour bitcoind doesn't progress with synchronization despite approx. 4 months lag, doesn't consume much CPU or RAM, uses disk IO, produces large amount of logs like e.g. `[leveldb] Generated table #3982690@4: 31588 keys, 2162389 bytes` for hours (there was a test for more than 8 hours). Reproduced 3 times out of 3 tests (one with a pre-built version 27). ### Expected behaviour bitcoind finishes synchronization in an hour or so. ### Steps to reproduce Preconditions: 1) Bitcoin 28.1 2) Pruned node (550MB) Steps: 1) Launch bitcoind `bitcoind -datadir=/mnt/sd/Bitcoin_data -daemon=0 -debug=all -blocksonly=1 -debuglogfile=/tmp/debug.log -prune=550 -dbcache=2048` ### Relevant log output `2025-02-16T13:04:33Z [leveldb] Generated table #3987352@3: 31812 keys, 2161649 bytes` Also: `error code: -28` `error message:` `Starting network threads…` - after the command: `bitcoin-cli stop`. [logs.tar.gz](https://github.com/user-attachments/files/18815120/logs.tar.gz) ### How did you obtain Bitcoin Core Compiled from source ### What version of Bitcoin Core are you using? 28.1 ### Operating system and version Arch Linux ### Machine specifications Intel x64, 4GB RAM, 32GB SD (exfat), 1Gbit Ethernet, 100/10 Mbit/s FTTH.

URL

https://github.com/bitcoin/bitcoin/issue/31882

Closed by

Notes

Attention of

Kill Factor (1-10)

Save

Back to List