Issue and situation This post is a second branch of Reverse client-server connection fails with more than one MPI process . Parallel jobs fall back to serial in a reverse connection between client and server within the same network – see above post for the mechanics of the error. At server and cli…

First, make sure that the VTK submodule is updated on both the client and server: git submodule update --recursive I have forgotten to do that and run into similar connection errors. If that doesn’t work, you can try a make clean in your build directory. If that still doesn’t work, delete everyth…

Resuming this topic whereby pvserver does not work in parallel mode with reverse connection, I hope that the search reporting given above is exhaustive enough. Elaborating on it, I have server and client clashing on this line of the subroutine vtkSocketCommunicator (namely from /superbuild/paraview…

That’s the solution! I can see four pvserver processes working remotely for my local viewer, as intended. No crashes @cory.quammen Please note that in the superbuild instructions at https://gitlab.kitware.com/paraview/paraview-superbuild/blob/master/README.md#building-a-specific-version the sugge…

The --recusive option just tells the VTK submodule to update its (currently one) submodule, VTK-m, which shouldn’t make a difference with regards to the client/server handshake. But that operation should be updated in the build instructions.

@ben.boeckel ? [image] cory.quammen: The --recusive option just tells the VTK submodule to update its (currently one) submodule, VTK-m, which shouldn’t make a difference with regards to the client/server handshake. But that operation should be updated in the build instructions. Reference is m…

I’m even more confused now. Those build instructions you’ve cited are for the superbuild, not paraview itself - --recursive is only useful when updating the paraview repository. The superbuild does have a submodule that requires updating, but it does not have nested submodules that would require the…

And I am ever more confused now. The errors have been launched by pvserver, and both client and sever are little endian; I cannot say which potential bad build was sending a wrong endianness or reading it wrong, though. I sort of think to have launched a make clean after each rebuild attempt as a m…

@cory.quammen Would you mind it to edit your accepted answer and add that making sure to do a make clean could also be part of the solution? There are not so many tips in the internet on sorting the endian-handshake incident. A little edit can help future readers fix their problem quickly, since the…

ParaView

vtkSocketCommunicator errors: "Could not receive tag" and "Endian handshake failed"

ParaView Support