Forum: Managing VoltDB

Post: wire protocol violation (timeout reading message length)

wire protocol violation (timeout reading message length)
tequilamaya
May 4, 2012
Hi folks,

Have just upgraded from VoltDB 2.1.3 to VoltDB 2.6 and am now noticing the following message just after startup. The database seems to perform ok when I query via Studio.web but the following message occurs about every two seconds:

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:37757): wire protocol violation (timeout reading message length).

Any ideas???
error message has now disappeared
tequilamaya
May 7, 2012
thinking this might be an issue with an older snapshot (from v2.1.3) - not 100% sure why but the error message has now gone away (for the time being anyway)
Hi,The database is logging
aweisberg
May 7, 2012
Hi,

The database is logging that something connected, but didn't supply a login message (or any message) before timing out. I don't have a handle on what could cause that. You would probably have to plumb netstat to find out what is using the ephemeral port that Volt logs as timing out.

Since it went away it sounds like the process that was doing that has gone? There haven't been any changes to the wire protocol that would explain this.

-Ariel
still using older studio.web
tequilamaya
May 7, 2012
Hi,

The database is logging that something connected, but didn't supply a login message (or any message) before timing out. I don't have a handle on what could cause that. You would probably have to plumb netstat to find out what is using the ephemeral port that Volt logs as timing out.



Hi Ariel,

Thanks for the reply. Just realised that i was still connecting with V2.1.3 of studio.web. Do you think that may have something to do with it? Other than that I'm just relieved that it's not churning out the message every two seconds.
It's back
tequilamaya
May 8, 2012
Hi Ariel,

Just started up voltdb again this morning (two nodes) and the logging message, produced every two seconds, has returned (it ran ok yesterday). Seems to be intermittent. I've not used netstat in any great way but i'll take some time to have a look into it. Also, this logging message is occurring without studio.web running so i can rule that one out. Nothing else is connecting to it - it's just happenning straight after database start up. Like i say the database still seems to run ok but i'm concerned that it may have an effect on performance.

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42377): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42379): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42381): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42383): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42385): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42387): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42389): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42391): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42393): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42395): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42397): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42399): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42401): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42403): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42405): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42407): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection
(/192.168.0.62:42409): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42411): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42413): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection
(/192.168.0.62:42415): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42417): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42419): wire protocol violation (timeout reading message length).

[Client authenticator 0] DEBUG AUTH - Failure to authenticate connection(/192.168.0.62:42421): wire protocol violation (timeout reading message length).

etc etc
My fault
tequilamaya
May 8, 2012
Hi Ariel,

Apologies; just realised what it is. I've got other linux boxes running various other systems and i forgot to shut off the haproxy process from another box - that was what was trying to connect (still need to set that up correctly in between Railo and Volt). Got mixed up with my IP addresses, didn't notice it wasn't one of the volt nodes. Thankfully, that's that one sorted.