[Paraview] Paraview 3.0.2 crashes when trying to connect to a server. A bug?

[Moreland, Kenneth]

We usually advise people not to use the renderserver/dataserver setup
unless you have a good reason to use it.  The simple client/server mode
usually works more efficiently because there is less copying of data
around.

If you still care about your problem (and you probably shouldn't), it
looks like the render server is reporting its hostnames as localhost.
That hostname is, of course, wrong when the data server tries to connect
to the render server.  You can use the --machines option to specify the
correct hostnames.

-Ken

> -----Original Message-----
> From: Marc Baaden [mailto:baaden at smplinux.de]
> Sent: Friday, June 29, 2007 4:58 PM
> To: Moreland, Kenneth
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] Paraview 3.0.2 crashes when trying to connect
to a
> server. A bug?
> 
> 
> Another issue.
> I was trying the client / dataserver /renderserver model with the
> renderserver on the machine that crashed the client and the dataserver
> on the client machine. When I try to connect, I get this:
> 
> 
> :528;  om-mpirun -np 4 ./pvrenderserver --use-offscreen-rendering
> Listen on port: 22221
> RenderServer: Waiting for client...
> Client connected.
> Connect: id :0  host: localhost  Port:53168
> Connect: id :1  host: localhost  Port:512
> Connect: id :2  host: localhost  Port:512
> Connect: id :3  host: localhost  Port:512
> Process id: 0 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkClientSocket.cxx, line 53
> vtkClientSocket (0x4444f40): Failed to connect to server
localhost:53168
> 
> Process id: 1 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkClientSocket.cxx, line 53
> vtkClientSocket (0x4444c70): Failed to connect to server localhost:512
> 
> Process id: 1 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkSocketCommunicator.cxx, line 468
> vtkSocketCommunicator (0x4444c30): Can not connect to localhost on
port
> 512
> 
> Process id: 3 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkClientSocket.cxx, line 53
> vtkClientSocket (0x4444c40): Failed to connect to server localhost:512
> 
> Process id: 2 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkClientSocket.cxx, line 53
> vtkClientSocket (0x4444c70): Failed to connect to server localhost:512
> 
> Process id: 2 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkSocketCommunicator.cxx, line 468
> vtkSocketCommunicator (0x4444c30): Can not connect to localhost on
port
> 512
> 
> Process id: 3 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkSocketCommunicator.cxx, line 468
> vtkSocketCommunicator (0x4444c00): Can not connect to localhost on
port
> 512
> 
> Process id: 0 >> ERROR: In /opt/src/paraview-
> cvs/VTK/Parallel/vtkSocketCommunicator.cxx, line 468
> vtkSocketCommunicator (0x4445050): Can not connect to localhost on
port
> 53168
> 
> [lux:08657] *** Process received signal ***
> [lux:08653] *** Process received signal ***
> [lux:08653] Signal: Bus error (10)
> [lux:08653] Associated errno: Unknown error: 1802794550 (1802794550)
> [lux:08653] Signal code:  (829651315)
> [lux:08653] Failing at address: 0x69737365
> [ 1] [0xbfffd338, 0x00000014] (-P-)
> [ 2] [lux:08655] *** Process received signal ***
> (_ZN9vtkSocket4SendEPvi + 0x18) [0xbfffd398, 0x006e8fee]
> [ 3] (_ZN21vtkSocketCommunicator10SendTaggedEPviiiPKc + 0x2c)
[0xbfffd428,
> 0x006deab8]
> [ 4] (_ZN21vtkSocketCommunicator4SendEPiiii + 0x62) [0xbfffd468,
> 0x006e086c]
> [ 5] (_ZN26vtkMPIMToNSocketConnection7ConnectEv + 0x339) [0xbfffd4d8,
> 0x000091b9]
> [ 6]
>
(_Z33vtkMPIMToNSocketConnectionCommandP26vtkClientServerInterpreterP13vt
kO
> bjectBasePKcRK21vtkClientServerStreamRS5_ + 0x936) [0xbfffd678,
> 0x002f474e]
> [ 7]
>
(_ZN26vtkClientServerInterpreter20ProcessCommandInvokeERK21vtkClientServ
er
> Streami + 0x17e) [0xbfffd798, 0x006d9ac8]
> [ 8]
>
(_ZN26vtkClientServerInterpreter17ProcessOneMessageERK21vtkClientServerS
tr
> eami + 0x134) [0xbfffd898, 0x006dab68]
> [ 9] [lux:08659] *** Process received signal ***
>
(_ZN26vtkClientServerInterpreter13ProcessStreamERK21vtkClientServerStrea
m
> + 0x28) [0xbfffd8d8, 0x006dadac]
> [10]
> (_ZN17vtkSelfConnection20ProcessStreamLocallyER21vtkClientServerStream
+
> 0x31) [0xbfffd908, 0x0003ad13]
> [11]
>
(_ZN20vtkMPISelfConnection30SendStreamToServerNodeInternalEiR21vtkClient
Se
> rverStream + 0x1be) [0xbfffd968, 0x0000c574]
> [12]
>
(_ZN20vtkMPISelfConnection22SendStreamToDataServerER21vtkClientServerStr
ea
> m + 0x65) [0xbfffd998, 0x0000c62f]
> [13]
> (_ZN26vtkProcessModuleConnection10SendStreamEjR21vtkClientServerStream
+
> 0x57) [0xbfffd9c8, 0x0000df97]
> [14]
>
(_ZN33vtkProcessModuleConnectionManager10SendStreamEijR21vtkClientServer
St
> reami + 0x41) [0xbfffd9f8, 0x0000f441]
> [15] (_ZN16vtkProcessModule10SendStreamEijR21vtkClientServerStreami +
> 0x66) [0xbfffda48, 0x000146a8]
> [16] (_Z22vtkClientConnectionRMIPvS_ii + 0x7a) [0xbfffda98,
0x00006122]
> [17] (_ZN25vtkMultiProcessController10ProcessRMIEiPvii + 0x263)
> [0xbfffdae8, 0x006d754b]
> [18] (_ZN25vtkMultiProcessController11ProcessRMIsEii + 0x3f4)
[0xbfffdb78,
> 0x006d7c32]
> [19] (_ZN19vtkRemoteConnection20ProcessCommunicationEv + 0x24)
> [0xbfffdbb8, 0x0003868e]
> [20] (_ZN33vtkProcessModuleConnectionManager18MonitorConnectionsEm +
> 0x608) [0xbfffdc48, 0x00011c58]
> [21] (_ZN16vtkProcessModule11StartServerEm + 0x197) [0xbfffdc88,
> 0x00013eb9]
> [22] (_ZN16vtkProcessModule5StartEiPPc + 0x387) [0xbfffdcd8,
0x0001345d]
> [23] (_ZN9vtkPVMain3RunEP12vtkPVOptions + 0x1dd) [0xbfffdd28,
0x00045d5b]
> [24] (main + 0x8e) [0xbfffdd68, 0x00004552]
> [25] (_start + 0xd8) [0xbfffdda8, 0x00003e52]
> [26] (start + 0x29) [0xbfffddc0, 0x00003d79]
> [27] [0x00000000, 0x00000002] (FP-)
> [lux:08653] *** End of error message ***
> om-mpirun noticed that job rank 0 with PID 8653 on node
lux.lbt.ibpc.fr
> exited on signal 10 (Bus error).
> 3 additional processes aborted (not shown)
> 
>   Marc Baaden
> 
> 
> --
>  Dr. Marc Baaden  - Institut de Biologie Physico-Chimique, Paris
>  mailto:baaden at smplinux.de      -      http://www.baaden.ibpc.fr
>  FAX: +33 15841 5026  -  Tel: +33 15841 5176  ou  +33 609 843217
> 
>