FAQ - XDR bad proto error

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:

  1. 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.

  2. 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.

  3. Network level corruption such as corrupt network packets from NIC driver issues.

  4. 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