Fresh sync hangs on hardfork blocks and requires a restart of the daemon.

[ombre-projects]

Fresh sync hangs on hardfork blocks and requires a restart of the daemon.

[mrheinen]

Here are some logs from when it hangs:

2018-Aug-07 11:29:36.725174 [P2P9][158.69.52.139:19743 OUT]Sync data returned a new top block candidate: 71999 -> 222107 [Your node is 150108 blocks (104 days) behind] 
SYNCHRONIZATION started
2018-Aug-07 11:29:37.473893 [P2P8]IP 158.69.52.139 blocked.
2018-Aug-07 11:31:01.838768 [P2P4][46.98.69.245:19743 OUT]Sync data returned a new top block candidate: 71999 -> 222108 [Your node is 150109 blocks (104 days) behind] 
SYNCHRONIZATION started
2018-Aug-07 11:31:04.422285 [P2P7]IP 46.98.69.245 blocked.
2018-Aug-07 11:32:05.613522 [P2P8][185.47.62.242:19743 OUT]Sync data returned a new top block candidate: 71999 -> 222110 [Your node is 150111 blocks (104 days) behind] 
SYNCHRONIZATION started
2018-Aug-07 11:32:50.339284 [P2P2]IP 185.47.62.242 blocked.

.... snip ... snip

2018-Aug-07 11:51:45.284126 [P2P0]BlockchainLMDB::block_rtxn_start
2018-Aug-07 11:51:45.284150 [P2P0]Block with hash d9a70491b107e0f46d528fb22698dcb7125cc56381a35761acdcf0d808a3be83 not found in db
2018-Aug-07 11:51:45.284171 [P2P0]mdb_txn_safe: destructor
2018-Aug-07 11:51:45.284187 [P2P0]Skipping out of date node: 87991, id: <d9a70491b107e0f46d528fb22698dcb7125cc56381a35761acdcf0d808a3be83>
2018-Aug-07 11:51:45.284205 [P2P0][192.187.117.162:19743 OUT]COMMAND_HANDSHAKE invoked, but process_payload_sync_data returned false, dropping connection.
2018-Aug-07 11:51:45.284295 [P2P2][192.187.117.162:19743 OUT]COMMAND_HANDSHAKE Failed
2018-Aug-07 11:51:45.284387 [P2P2][192.187.117.162:19743 OUT]Failed to HANDSHAKE with peer 192.187.117.162:19743
info   {5} {p1} 2018-08-07 11:51:45.284443 [net_node.inl+990 ::make_new_connection_from_peerlist] Handshake failed

status
Height: 71999/222110 (32.4%) on mainnet, not mining, net hash 1.90 MH/s, v3 (next fork in 1 blocks), up to date, 0+1 connections

So the daemon is at version 3... however, the hardfork happens at: 72000:

{ 3, 72000, 0, 1524577218 }, // Roughly the 20th of April.

So that's where the confusion seems to be.