Ok, looks like we have a problem.
My newest ("whydah") version based on 0.10.2 LTC has been widely used for mining, and v3 blocks fork kicks in.
This version is not accepting v2 blocks any more!
There is probably some major network fork, where v12 ("newprovidence", "queens annie revenge") and earlier miners are still mining (LTC versions 0.8 and older, v2 blocks), but newest clients not want to accept theirs blocks.
I`m now starting older version of daemon on my node to see where it goes and will compare what block see "whydah" and where is "newprovidence".
My "newprovidence" windows is on block 1005625 78f08433a1d4ba604356ecd8a7c25fd948c09d3cfa1a97bd48cec0db96544cb9 and showing "2 days behind".
edit:
My "whydah" is in same place, log shows:
2015-12-16 08:30:01 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 08:30:01 ERROR: invalid header received
2015-12-16 08:30:01 ProcessMessage(headers, 16039 bytes) FAILED peer=10
2015-12-16 08:30:01 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 08:30:01 ERROR: invalid header received
2015-12-16 08:30:01 ProcessMessage(headers, 16039 bytes) FAILED peer=1
2015-12-16 08:30:01 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 08:30:01 ERROR: invalid header received
2015-12-16 08:30:01 ProcessMessage(headers, 16039 bytes) FAILED peer=7
edit2:
Found node that is still mining v2 blocks (or is connected to one that is mining):
receive version message: /Satoshi:0.12.0/: version 80000, blocks=1006075, us=91.235.254.37:53998, peer=12, peeraddr=93.100.107.4:1336
2015-12-16 12:34:47 connect() to 70.163.93.56:1336 failed after select(): Connection refused (111)
2015-12-16 12:36:23 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 12:36:23 ERROR: invalid header received
2015-12-16 12:36:23 ProcessMessage(headers, 36534 bytes) FAILED peer=12
2015-12-16 12:37:00 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 12:37:00 ERROR: invalid header received
edit3:
My windoze v12 node is synced up to 1006406 bf311a20f9c704c30256b17867c44a7468e40ac31704ec1e9cedc1c882656aea and showing up "Warning: This version is obsolete, upgrade required!" and counting
My linux v12 node still syncing (830xxx atm)...
Linux v13 stopped on 1005625.
Looks like v13 need moar tuning to adapt to longer chain and finally fix sync issues in first few hundred thousand blocks.
Miners, pls NOT mine on v13 "wyhdah" any more! When my node sync it will be v12 until v13 is finished.
Also, when we launch mining on v13, versions prior v12 will not connect to network (v13 need nodes that have "get headers" message, older clients not have it) and mining will be possible ONLY on v13 (because of v3 block version)!
So, if you are using ANY version under v12 upgrade NOW!