ProcessMessage(ping, 0 bytes) FAILED

[zvs]

Code:

2013-11-07 23:00:12 receive version message: version 70001, blocks=0, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=88.198.17.xx:42873
2013-11-07 23:09:17 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-07 23:09:17 ProcessMessage(ping, 0 bytes) FAILED
2013-11-07 23:18:37 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-07 23:18:37 ProcessMessage(ping, 0 bytes) FAILED
2013-11-07 23:27:38 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-07 23:27:38 ProcessMessage(ping, 0 bytes) FAILED
2013-11-07 23:36:58 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-07 23:36:58 ProcessMessage(ping, 0 bytes) FAILED
2013-11-07 23:46:18 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-07 23:46:18 ProcessMessage(ping, 0 bytes) FAILED
2013-11-07 23:55:38 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-07 23:55:38 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 00:04:58 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 00:04:58 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 00:13:59 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 00:13:59 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 00:23:19 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 00:23:19 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 00:32:19 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 00:32:19 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 00:41:40 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 00:41:40 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 00:51:00 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 00:51:00 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 01:00:20 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 01:00:20 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 01:09:21 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 01:09:21 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 01:18:41 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 01:18:41 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 01:28:01 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 01:28:01 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 01:37:21 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 01:37:21 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 01:46:42 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 01:46:42 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 01:56:02 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 01:56:02 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 02:05:22 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 02:05:22 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 02:14:22 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 02:14:22 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 02:23:43 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 02:23:43 ProcessMessage(ping, 0 bytes) FAILED
2013-11-08 02:33:03 ProcessMessages(ping, 0 bytes) : Exception 'CDataStream::read() : end of data' caught, normally caused by a message being shorter than its stated length
2013-11-08 02:33:03 ProcessMessage(ping, 0 bytes) FAILED

9m or 9m20s between each, started after node @ 88.197.17.xx connected.  Didn't have any other of these messages in the prior 15 hours or so of log.

used tcpkill to kill that connection and nothing in 20 minutes now.

showed up as:

        "addr" : "88.198.17.xx:42873",
        "addrlocal" : "xxxxxxxx:8333",
        "services" : "00000000",
        "lastsend" : 1383878216,
        "lastrecv" : 1383878203,
        "bytessent" : 1501084,
        "bytesrecv" : 99201,
        "conntime" : 1383865212,
        "pingtime" : 0.00000000,
        "version" : 70001,
        "subver" : "/BQS:0.0.1/",
        "inbound" : true,
        "startingheight" : 0,
        "banscore" : 0

[zvs]

Oh, there's also at least a dozen peers connected to me that essentially never send data, just receive it.

re: connected at height 0 (or sometimes -1)    (and no they aren't downloading the blockchain, heh)

[zebedee]

Heh, just noticed this.  On my experimental server it shows up as:

2014-10-13 18:37:55.275618500 blockd: in:88.198.17.7/54537 (/BQS:0.0.1/): protocol: ill-formed ping command

Basically, BQS, whatever it is, is advertising a network protocol version that it isn't conforming to.  I don't get the above from any other connections.

[Newar]

Heh, just noticed this.  On my experimental server it shows up as:

2014-10-13 18:37:55.275618500 blockd: in:88.198.17.7/54537 (/BQS:0.0.1/): protocol: ill-formed ping command

Basically, BQS, whatever it is, is advertising a network protocol version that it isn't conforming to.  I don't get the above from any other connections.

That BQS IP 88.198.17.7 seems to be Mycelium: https://bitcointalk.org/index.php?topic=725391.msg8200412#msg8200412

I take it nobody has contacted them so far?


Edit: Oh, OP is from last year.

[zebedee]

Heh, just noticed this.  On my experimental server it shows up as:

2014-10-13 18:37:55.275618500 blockd: in:88.198.17.7/54537 (/BQS:0.0.1/): protocol: ill-formed ping command

Basically, BQS, whatever it is, is advertising a network protocol version that it isn't conforming to.  I don't get the above from any other connections.

That BQS IP 88.198.17.7 seems to be Mycelium: https://bitcointalk.org/index.php?topic=725391.msg8200412#msg8200412

I take it nobody has contacted them so far?


Edit: Oh, OP is from last year.

Cool.  I'll, um, ping them.