Error upgrading from 0.13.1 to 0.13.2 #9666

issue yield65 opened this issue on February 1, 2017

yield65 commented at 11:13 PM on February 1, 2017: none

I was running a prune node version 0.13.1 on ubuntu Linux generic [#68](/bitcoin-bitcoin/68/)-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

After upgrading via apt-get (never had a problem with that) I got this errors:

2017-02-01 19:46:53 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data: iostream error' caught, normally caused by a message being shorter than its stated length
2017-02-01 19:46:53 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=11
2017-02-01 19:46:53 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data: iostream error' caught, normally caused by a message being shorter than its stated length
2017-02-01 19:46:53 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=11

Complete log in here:

http://paste.ubuntu.com/23907839/

sipa commented at 11:18 PM on February 1, 2017: member

Those messages indicate you have a misbehaving peer, not a bug in your own node.
paveljanik commented at 6:58 AM on February 2, 2017: contributor

sendcmpct, 5 bytes is very common log entry these days. Do we have any idea, why/who can send this?
jonasschnelli added the label P2P on Feb 2, 2017
laanwj commented at 8:15 AM on February 2, 2017: member

Ah, yes, we should probably stop logging errors for random peer's misbehavior unless debug=net or so. Just like the random transaction validation errors that used to be thrown into the log before this was fixed a while ago, this is confusing.
laanwj closed this on Feb 2, 2017
yield65 commented at 6:33 PM on February 2, 2017: none

I just ignored the messages and leave it like that, after little more than half an hour it started to sync again.

Thank you, regards.
scottie commented at 7:50 AM on June 16, 2018: none

cause ?
MarcoFalke locked this on Sep 8, 2021

Contributors

Labels

Linked (view graph)

#68 Specify location for wallet.dat file