The Aerospike Knowledge Base has moved to https://support.aerospike.com. Content on https://discuss.aerospike.com is being migrated to either https://support.aerospike.com or https://docs.aerospike.com. Maintenance on articles stored in this repository ceased on December 31st 2022 and this article may be stale. If you have any questions, please do not hesitate to raise a case via https://support.aerospike.com.
FAQ - XDR bad proto error
Detail
A ‘bad proto version’ error message indicates that a destination XDR server returned a false or misleading response to the XDR client.
Warning message:
WARNING (xdr-client): (cluster.c:522) bad proto version 83 - 0x00007eee0000ee00 192.168.1.1:3000
WARNING (xdr-client): (cluster.c:522) bad proto version 0 - 0x0000000000000000 192.168.1.2:3000
The possible triggers of this error are:
-
XDR seeds are configured and point to a non-Aerospike node. This can also occur if an Aerospike node has another process running on the configured port or the seed node port is misconfigured.
-
The seed nodes are publishing the wrong IP addresses. For example, the access-address or alternate-access-address are configured with the wrong IP addresses and point to a different system.
-
Network level corruption such as corrupt network packets from NIC driver issues.
-
Rapid connection churns occurring under heavy workload and impacting destination’s networking environment.
Notes
This could be due to a particular network interface reaching a hardware limit or some firmware issue.
Applies To
Aerospike server 5.0 and later.
Keywords
BAD PROTO NETWORK CORRUPTION CONNECTIVITY XDR
Timestamp
December 2021