btcd stops downloading new blocks

[dajohi]

occasionally, btcd stops processing anything it seems. It is suspected that the cause is the syncpeer disconnects before the entire block is downloaded.

12:49 @davecgh It's clearly requesting blocks after the latest one it has
12:49 @davecgh most likely because they're already queued
12:50 @davecgh what should happen is it processes the queued blocks as orphans
12:50 @davecgh while it re-requests the block that was interrupted mid-download from either another peer, or the current sync peer

14:54:00 2013-12-14 [INF] BMGR: Processed 1 block in the last 25m58.01s (649 transactions, height 274911, 2013-12-14 14:52:38 -0500 EST)
14:57:43 2013-12-14 [INF] BMGR: Processed 1 block in the last 3m42.97s (432 transactions, height 274912, 2013-12-14 14:55:56 -0500 EST)
14:58:29 2013-12-14 [INF] BMGR: Processed 1 block in the last 46.12s (94 transactions, height 274913, 2013-12-14 14:57:27 -0500 EST)
15:00:18 2013-12-14 [INF] BMGR: New valid peer [2a02:348:5e:5a29::1]:37521 (inbound)
15:00:19 2013-12-14 [INF] BMGR: Lost peer [2a02:348:5e:5a29::1]:37521 (inbound)
15:11:24 2013-12-14 [INF] BMGR: Processed 1 block in the last 12m55.01s (585 transactions, height 274914, 2013-12-14 15:09:38 -0500 EST)
15:21:13 2013-12-14 [INF] BMGR: Processed 1 block in the last 9m48.81s (418 transactions, height 274915, 2013-12-14 15:18:33 -0500 EST)
15:22:02 2013-12-14 [INF] BMGR: New valid peer [2001:470:88ff:2e::1]:56022 (inbound)
15:22:03 2013-12-14 [INF] BMGR: Lost peer [2001:470:88ff:2e::1]:56022 (inbound)
15:25:30 2013-12-14 [INF] BMGR: Processed 1 block in the last 4m16.57s (177 transactions, height 274916, 2013-12-14 15:22:48 -0500 EST)
15:28:34 2013-12-14 [WRN] PEER: Peer 81.174.134.146:4744 (inbound) no answer for 5 minutes, disconnecting
15:28:41 2013-12-14 [INF] BMGR: Lost peer 81.174.134.146:4744 (inbound)
15:29:26 2013-12-14 [INF] BMGR: New valid peer [2a02:348:5e:5a29::1]:60697 (inbound)
15:29:27 2013-12-14 [INF] BMGR: Lost peer [2a02:348:5e:5a29::1]:60697 (inbound)
15:31:46 2013-12-14 [INF] BMGR: Processed 1 block in the last 6m16.28s (271 transactions, height 274917, 2013-12-14 15:31:27 -0500 EST)
16:05:50 2013-12-14 [INF] BMGR: New valid peer 212.159.87.30:4981 (inbound)
16:05:50 2013-12-14 [INF] BMGR: Lost peer 212.159.87.30:4981 (inbound)
16:05:53 2013-12-14 [INF] BMGR: New valid peer 178.79.147.171:51920 (inbound)
16:05:53 2013-12-14 [INF] BMGR: Lost peer 178.79.147.171:51920 (inbound)
16:05:54 2013-12-14 [INF] BMGR: New valid peer 158.109.79.146:41394 (inbound)
16:05:54 2013-12-14 [INF] BMGR: Lost peer 158.109.79.146:41394 (inbound)
16:14:30 2013-12-14 [INF] CHAN: Adding orphan block 0000000000000001d241587c3cd447f8939793437beeda7b3c362469a06fe019 with parent 000000000000000270a8f575f530d3b1a98745db340e20f5d4b1fa2737039836
16:14:30 2013-12-14 [INF] BMGR: Processed 1 block in the last 42m44.44s (227 transactions, height 274917, 2013-12-14 15:31:27 -0500 EST)
16:14:30 2013-12-14 [INF] BMGR: New valid peer 77.58.144.181:58597 (inbound)
16:14:30 2013-12-14 [INF] BMGR: Lost peer 77.58.144.181:58597 (inbound)
16:14:43 2013-12-14 [INF] BMGR: New valid peer [2a02:348:5e:5a29::1]:60870 (inbound)
16:14:43 2013-12-14 [INF] BMGR: Lost peer [2a02:348:5e:5a29::1]:60870 (inbound)
16:14:53 2013-12-14 [INF] CHAN: Adding orphan block 00000000000000008dcd476edd149c66a0ff9221b6396368ef0e05f3006eca0b with parent 0000000000000001d241587c3cd447f8939793437beeda7b3c362469a06fe019
16:14:53 2013-12-14 [INF] BMGR: Processed 1 block in the last 22.66s (72 transactions, height 274917, 2013-12-14 15:31:27 -0500 EST)

[jcvernaleo]

I'm seeing the same thing on Linux. I have not seem this behavior on testnet despite running uninterrupted there for longer times.

[davecgh]

This is probably related to the new headers first code.