BTC Node Issues and Syncing Confusion

Been running my BTC Node for like 3 years now. Noticed some weird stuff recently. Sometimes it kicks off peers and shows a wallet as lost. Here are some logs from my node... 2024-08-11T19:44:35Z New outbound peer connected: version: 70016, blocks=856354, peer=2166 (outbound-full-relay) 2024-08-11T19:47:45Z Timeout downloading headers from peer=2121, disconnecting 2024-08-11T18:52:22Z New outbound peer connected: version: 70016, blocks=856347, peer=2067 (outbound-full-relay) 2024-08-11T18:58:52Z Timeout downloading headers from peer=2003, disconnecting.

Can you share more lines from your debug.log? Like from the last "Bitcoin Core version..." part? It helps to spot any issues. Also, snip the repeated "New outbound.." and "Timeout" lines to make it shorter. You can use [code][/code] tags for that.

I mean, if those timeouts aren't constant and syncing isn't totally wrecked, it's pretty normal. Peers can drop connections or not respond sometimes. Your node just moves on to the next peer for the data.

Thanks for the input! I added some more debug info. My node seems fine. But I’m curious, do all nodes work like mine? It keeps removing old blocks and downloading headers, even from the first peers. I’m kinda new to this... -11-15T01:14:53Z init message: Starting network threads... 2023-11-15T01:14:53Z net thread start 2023-11-15T01:14:53Z dnsseed thread start 2023-11-15T01:14:53Z Waiting 300 seconds before querying DNS seeds.

Check the dates on your logs. They’re from last year, so they might not reflect what’s happening now.

Debug Report Mod note: Consecutive posts merged, code tags added.

That’s just how it goes for a full node with pruning enabled. The logs from 2023 hint you’ve got the "prune" setting turned on. Those parts you posted earlier? I told you to snip those out since they’re not key for debugging. You still need to show the settings and configs. If it's about "block removal," that's because of the prune setting in your GUI.