[Paraview] [PV3 HEAD] client x server connection problem (not mismatch versions)

Renato N. Elias rnelias at nacad.ufrj.br
Tue Sep 2 10:20:27 EDT 2008


I guess I found the problem. The Altix-ICE's nodes can't ping outside 
(the test I had done in the first email was using the service node).

If I try:
rsh r1i0n0 ping Windows.Laptop.Ip
the command returns:
118 packets transmitted, 0 received, 100% packet loss, time 117007ms

[]'s

Renato.

Renato N. Elias wrote:
> (...now I'm pretty sure that the problem is not version mismatch ;o)  )
>
> I'm trying to run a client x server reverse connection between an 
> Altix-ICE(server/offscreen rendering) and a Windows XP laptop.
>
> The scenario is:
>
> -- ParaView 3 CVS's HEAD (I updated both, client and server, today)
> On Windows side, I've compiled using VS2005 (Qt 4.3.4);
> On SUSE's side, I've used mvapich 1.0.3, SGI's Mesa 6.4.2;
>
> -- The connection setup is:
> On the client side: reverse connection manually configured;
> On the server side: I used the following torque's script to launch the 
> pvserver:
>
> --------------------------------------------------------------------------------------------------------------------------------------- 
>
> Torque's script (just the most relevant parts)
>
> export 
> LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/absolute/path/to/paraview/lib/directory/ 
>
>
> mpiexec -n ${NUM_PROC} 
> /absolute/path/to/paraview/bin/directory/pvserver 
> --use-offscreen-rendering -rc -ch=Windows.Laptop.Ip
> --------------------------------------------------------------------------------------------------------------------------------------- 
>
>
> -- Launching procedure:
> I've let the client waiting and submitted the paraview's job script. 
> The Torque started my job (RUN STATUS), and the following message 
> echoed on the client's screen:
>
> ------------------------------------------------------------------------------------------------------------------------------------- 
>
> ERROR: In 
> ..\..\..\ParaView3_CVS\Servers\Common\vtkServerConnection.cxx, line 67
>
> vtkServerConnection (07A9BA18): Server Connection Closed!
>
> ERROR: In 
> ..\..\..\ParaView3_CVS\Servers\Common\vtkProcessModuleConnectionManager.cxx, 
> line 680
>
> vtkProcessModuleConnectionManager (055F34B0): Handshake failed. You 
> are probably using mismatching versions of client and server.
>
> ------------------------------------------------------------------------------------------------------------------------------------- 
>
>
> The script's output says:
>
> ------------------------------------------------------------------------------------------------------------------------------------ 
>
> Process id: 0 >> ERROR: In /.../vtkClientSocket.cxx, line 53
> vtkClientSocket (0x953f90): Failed to connect to server 
> Windows.Laptop.Ip:11111
>
> Process id: 0 >> ERROR: In /.../vtkProcessModule.cxx, line 730
> vtkProcessModule (0x5a8860): Server Error: Could not connect to client.
>
> /var/spool/torque/mom_priv/epilogue: line 8: kill: (13412) - No such 
> process
> ------------------------------------------------------------------------------------------------------------------------------------ 
>
>
> If I try to ping Windows.Laptop.Ip from the server, it's there:
>
> ------------------------------------------------------------------------------------------------------------------------------------ 
>
> rnelias at service0:~> ping Windows.Laptop.Ip
> PING Windows.Laptop.Ip (Windows.Laptop.Ip) 56(84) bytes of data.
> 64 bytes from Windows.Laptop.Ip: icmp_seq=1 ttl=128 time=0.472 ms
> 64 bytes from Windows.Laptop.Ip: icmp_seq=2 ttl=128 time=0.491 ms
> ------------------------------------------------------------------------------------------------------------------------------------ 
>
>
> My guess is that something is wrongly configured, but I can figure it 
> out. Does ParaView have any kind of verbose mode where I could track 
> down where the problem is?
>
> Regards
>
> Renato.
>
>
>
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>



More information about the ParaView mailing list