MantisBT - ParaView
View Issue Details
0016094ParaView(No Category)public2016-04-26 07:422016-07-13 07:29
Dheeraj KV 
Utkarsh Ayachit 
highminorhave not tried
closedunable to reproduce 
4.4 
 
TBD
incorrect functionality
0016094: Paraview 4.4 reverse connection failingwith below given error
HI

I am trying reverse connection in HPC. On the server side I have started pvserver in reverse connection providing the hostname of the client machine.
The pvserver is ruuning on the compute node of HPC.
I get the following error:
On server
ERROR: In /dat/usr/x082685/Source/paraview/ParaView-v4.4.0-source/VTK/Common/System/vtkSocket.cxx, line 481
vtkClientSocket (0x2f5a500): Socket error in call to connect. Connection timed out.

ERROR: In /dat/usr/x082685/Source/paraview/ParaView-v4.4.0-source/VTK/Common/System/vtkClientSocket.cxx, line 53
vtkClientSocket (0x2f5a500): Failed to connect to server USE145JS2N:11111

ERROR: In /dat/usr/x082685/Source/paraview/ParaView-v4.4.0-source/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 309
vtkTCPNetworkAccessManager (0x1cee940): Connect timeout.

On client
RROR: In C:\bbd\b51c3c7f\source-paraview\VTK\Parallel\Core\vtkSocketCommunicator.cxx, line 809
vtkSocketCommunicator (000000000DE300D0): Could not receive tag. 1010580540


ERROR: In C:\bbd\b51c3c7f\source-paraview\VTK\Parallel\Core\vtkSocketCommunicator.cxx, line 435
vtkSocketCommunicator (000000000DE300D0): Endian handshake failed.


ERROR: In C:\bbd\b51c3c7f\source-paraview\ParaViewCore\ClientServerCore\Core\vtkTCPNetworkAccessManager.cxx, line 424
vtkTCPNetworkAccessManager (0000000009FCABE0):
**********************************************************************
Connection failed during handshake. This can happen for the following reasons:
 1. Connection dropped during the handshake.
 2. vtkSocketCommunicator::GetVersion() returns different values on the
    two connecting processes (Current value: 100).
 3. ParaView handshake strings are different on the two connecting
    processes (Current value: paraview.4.4).
**********************************************************************



ERROR: In C:\bbd\b51c3c7f\source-paraview\VTK\Parallel\Core\vtkSocketCommunicator.cxx, line 809
vtkSocketCommunicator (000000000BA9AA70): Could not receive tag. 1010580540


ERROR: In C:\bbd\b51c3c7f\source-paraview\VTK\Parallel\Core\vtkSocketCommunicator.cxx, line 435
vtkSocketCommunicator (000000000BA9AA70): Endian handshake failed.


ERROR: In C:\bbd\b51c3c7f\source-paraview\ParaViewCore\ClientServerCore\Core\vtkTCPNetworkAccessManager.cxx, line 424
vtkTCPNetworkAccessManager (0000000009FCABE0):
**********************************************************************
Connection failed during handshake. This can happen for the following reasons:
 1. Connection dropped during the handshake.
 2. vtkSocketCommunicator::GetVersion() returns different values on the
    two connecting processes (Current value: 100).
 3. ParaView handshake strings are different on the two connecting
    processes (Current value: paraview.4.4).
**********************************************************************

It works well for Forward connection, but reverse connection is giving error.
I tried telnet from the compute server(linux) to the client desktop (windows) with port 11111 at it connects well.


Hackathon-July-2016
Issue History
2016-04-26 07:42Dheeraj KVNew Issue
2016-04-26 07:42Dheeraj KVAssigned To => Utkarsh Ayachit
2016-07-12 11:33Utkarsh AyachitAssigned ToUtkarsh Ayachit =>
2016-07-12 11:33Utkarsh AyachitTag Attached: Hackathon-July-2016
2016-07-13 03:41Jean M. FavreNote Added: 0036350
2016-07-13 07:29Utkarsh AyachitStatusbacklog => closed
2016-07-13 07:29Utkarsh AyachitAssigned To => Utkarsh Ayachit
2016-07-13 07:29Utkarsh AyachitResolutionopen => unable to reproduce

Notes
(0036350)
Jean M. Favre   
2016-07-13 03:41   
I have tested PV4.4 running on a Windows machine using the pre-compiled executable provided by Kitware, connecting, in reverse-connection mode to a remote Cray machine. There were no issues. I could not reproduce the problem.

The client-server connection worked very well, with GPU_accelerated remote rendering.