"vtkSocketCommunicator::GetVersion() returns different values on the two connecting processes"

What does an error message “vtkSocketCommunicator::GetVersion() returns different values on the two connecting processes” refer to? This post is a branch of Reverse client-server connection fails with more than one MPI process.

This occurs when I try to set up a reverse connection between client and server within a network and parallel jobs fall back to serial – see above post for the mechanics of the error. Here I am interested in understanding what the trigger of this particular mismatch is, and seeing what I could tune to work around this. For example, whose program does GetVersion() refer to?

At server and client side I work with same architectures, operating systems and compilers: x86_64, Debian GNU/Linux 10 (buster), gcc (Debian 8.3.0-6) 8.3.0. Paraview is a release build of 5.7.0 out of the Superbuild at https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/README.md. The repository has been cloned separately on client and server.

There is little and old information about this sort of error on the internet, but I could not get usable cues out of it:

https://gitlab.kitware.com/paraview/paraview/issues/18171

This error is a red herring from another error and should be improved.

Thanks for pointing out that the message in itself is an issue. Hopefully it will be fixed soon. Since deciphering that message has no purpose, the vtkSocketCommunicator errors: "Could not receive tag" and "Endian handshake failed" are then the candidate troublemakers.