Its a bit strange, as the bootstrap from the link should have 2467400 blocks.
Anyway - after finishing bootstrap it should start syncing from the network.
Those errors probably
are from the network sync - I get a bunch of the same "already have block" errors when syncing any substantial amount (for example, after the client being shut down for a month). For some reason, it appears the client is asking multiple peers for the same block, or range of blocks, even though it already has them.
For example, my debug.log contains this 38 times:
ERROR: ProcessBlock() : already have block (orphan) 2035698dc4b0cf0617085d8448442a2ab6b3e63caa4ebcd01316186efe4736f7Doing some quick counting, there are over 4000 different blocks which arrived 5+ times during the one sync.
I noticed similar "already have block (orphan)" when I was syncing last time. I think its because its getting same block from different nodes at different time. I "solved" it by reducing number of connections in clam.conf
When the clam is connected to the only one other node, this orphans completely stopped appearing.