Strange Logs courtesy of 0.14 nodes

[Blockchain Mechanic]

I was wondering why my sync had slowed down so badly and decided to read the logs and maybe write a fix.... this is what i found. I usually run this node once a day just to sync then i stop it.

It appears newer versions released by Core devs are causing sync stalling in older versions.

Code:

2017-04-17 14:47:44 UpdateTip: new best=0000000000000000007e177a4121da03515eee2132a61fcdedc992111f5ca184 height=462015 version=0x20000002 log2_work=86.286199 tx=213516017$
2017-04-17 14:47:44 Pre-allocating up to position 0x5000000 in blk00836.dat
2017-04-17 14:47:44 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462295, us=41.191.238.189:54118, peer=12
2017-04-17 14:47:44 ProcessMessages(version, 102 bytes) FAILED peer=13
2017-04-17 14:47:45 connect() to [2001:0:9d38:90d7:18cb:8a6:cb53:4418]:8333 failed: Network is unreachable (101)
2017-04-17 14:47:47 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462296, us=41.191.238.189:56580, peer=14
2017-04-17 14:47:48 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data: iostream error' caught, normally caused by a message being shorter t$
2017-04-17 14:47:48 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=14
2017-04-17 14:47:48 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data: iostream error' caught, normally caused by a message being shorter t$
2017-04-17 14:47:48 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=14
2017-04-17 14:47:51 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data: iostream error' caught, normally caused by a message being shorter t$
2017-04-17 14:47:51 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=12
2017-04-17 14:47:51 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data: iostream error' caught, normally caused by a message being shorter t$
2017-04-17 14:47:51 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=12

My Node :

Code:

{
  "version": 130200,
  "protocolversion": 70015,
  "walletversion": 130000,
  "balance": xx.xxxxxxxx,
  "blocks": 462017,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 520808749422.1398,
  "testnet": false,
  "keypoololdest": 1484171182,
  "keypoolsize": 100,
  "paytxfee": 0.00000000,
  "relayfee": 0.00001000,
  "errors": ""
}

Is this accidental or is this behavior intended to force users to update?

[Meuh6879]

crappy (external) nodes.
not a problem.

compact block explanation, for sure.

[Blockchain Mechanic]

crappy (external) nodes.
not a problem.

compact block explanation, for sure.

I'm using CORE 0.13, so you are saying i'm connected to alternatives or mods ? kinda a big problem seeing as it is harder to do a simple sync.

Anyway, i'm stopping the node and deleting peers.dat to see if it helps.

[Meuh6879]

i have the same (and very little) messages with the 0.14.1 RC2.
not a problem.

sync need CPU and Hard Drive high power.
no client or internet special line.

[Foxpup]

Code:

2017-04-17 14:47:45 connect() to [2001:0:9d38:90d7:18cb:8a6:cb53:4418]:8333 failed: Network is unreachable (101)

Well, there's your problem. No version of Bitcoin supports the packet-over-air protocol. Your node is stalling because your Internet connection keeps dropping out; it's nothing to do with your peers.

[achow101]

Code:

2017-04-17 14:47:45 connect() to [2001:0:9d38:90d7:18cb:8a6:cb53:4418]:8333 failed: Network is unreachable (101)

Well, there's your problem. No version of Bitcoin supports the packet-over-air protocol. Your node is stalling because your Internet connection keeps dropping out; it's nothing to do with your peers.

No, that error is probably because their ISP does not give them IPv6 access. As you can see from the rest of the log, the node is clearly connected to other nodes and is receiving data.

OP, the section of the log you posted contains benign errors unrelated to your node and is completely useless. If you want more help, please post your machine specs and the entire debug.log.