[Paraview] bug in ParaView 3.4.0 server

[Utkarsh Ayachit]

Are you by any chance using the binaries distributed on
www.paraview.org? If so, are you trying to to run the pvserver with
mpiexec/mpirun? The distributed binaries are not built with MPI
support so cannot be run with mpi. I am asking this since in your
error messages there seem to be some mpiexec error messages.

Utkarsh

On Wed, Dec 17, 2008 at 11:51 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Is it possible for you to attach a debugger to the pvserver and
> provide the stack trace for where it crashes? My guess is it's failing
> when creating the render window.
>
> Utkarsh
>
> On Wed, Dec 17, 2008 at 11:43 AM, Stephen Wornom
> <stephen.wornom at sophia.inria.fr> wrote:
>> Utkarsh Ayachit wrote:
>>>
>>> Is there any error message shown on the server? Doesn't look like you
>>> are able to render on the server.ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x123f8e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x1083ae60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0xfb25e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x9e35e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x1f59be60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x1ba5ae60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x4bede60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x12834e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x1be08e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x15bcfe60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x88f1e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x8006e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x1e10be60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x1308ce60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x12977e60): Failed to set up server
>>> socket.
>>>
>>> ERROR: In
>>> /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx,
>>> line 180
>>> vtkProcessModuleConnectionManager (0x156dfe60): Failed to set up server
>>> socket.
>>>
>>> mpiexec: Warning: task 0 died with signal 11 (Segmentation fault).
>>> mpiexec: Warning: tasks 1,3,5,7,9,11,13,15,17,19,21,23,25,27,29,31 exited
>>> with status 1.
>>> mpiexec: Warning: tasks 2,4,6,8,10,12,14,16,18,20,22,24,26,28,30 died with
>>> signal 15 (Terminated).
>>> stephen
>>>
>>
>>> Utkarsh
>>>
>>> On Wed, Dec 17, 2008 at 10:29 AM, Stephen Wornom
>>> <stephen.wornom at sophia.inria.fr> wrote:
>>>
>>>>
>>>> Utkarsh Ayachit wrote:
>>>>
>>>>>
>>>>> Are there any error messages outputted on the server side?
>>>>> Can you try this:
>>>>> When connected to the server and looking at the outline (which you say
>>>>> is rendered fine) go to Edit|Settings. In the Options dialog open up
>>>>> the "Render View" tree on the left pane and select "Server". There in
>>>>> the "Remote Rendering Paramaters" group ensure that "Remote Render
>>>>> Threshold" is set to 0 and checked. Now hit Ok.
>>>>>
>>>>
>>>> The thresh hold was by default 3 mb. When I set it to 0, the client
>>>> crashes
>>>> each time I try to establish a connection.
>>>> Navier> Waiting for server...
>>>> ERROR: In /tmp/ParaView-3.4.0/Servers/Common/vtkServerConnection.cxx,
>>>> line
>>>> 67
>>>> vtkServerConnection (0x5dd9240): Server Connection Closed!
>>>>
>>>> Is it important that each cpu has two cores?
>>>> Stephen
>>>>
>>>>
>>>>>
>>>>>  Does the outline still
>>>>> render fine? If not I am guess there's some issue with rendering on
>>>>> the server side.
>>>>>
>>>>> Utkarsh
>>>>>
>>>>> On Wed, Dec 17, 2008 at 3:46 AM, Stephen Wornom
>>>>> <stephen.wornom at sophia.inria.fr> wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> I am trying to visualize a data set with 500,000 vertices using pv
>>>>>> 3.4.0
>>>>>> without success.
>>>>>>
>>>>>> 1-step 1: I start the server with this script
>>>>>> --------------------------------------------------
>>>>>> #!/bin/sh
>>>>>> #PBS -N "Paraview_32"
>>>>>> #PBS -l "nodes=16:nef:ppn=2"
>>>>>> #PBS -l "walltime=4:00:00"
>>>>>> cd $PBS_O_WORKDIR
>>>>>> server=`hostname`
>>>>>>
>>>>>> ulimit -s unlimited
>>>>>>
>>>>>> echo "The server is listening on host $server "
>>>>>> #/usr/local/bin/mpiexec2 /usr/local/paraview/bin/pvserver
>>>>>> --use-offscreen-rendering
>>>>>>
>>>>>> mpiexec --comm=mpich2 /home/install/paraview-340/bin/pvserver
>>>>>> --use-offscreen-rendering
>>>>>>
>>>>>> step 2: I identify which processor is listening on host
>>>>>> ---------------------------------------------------------------
>>>>>>
>>>>>> step 3: I open pv 3.4.0 on the client, enter the server name and host
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------------
>>>>>> The files are read correctly on the client and the outline of the mesh
>>>>>> can
>>>>>> be seen on the client screen. When I try to visualize a solution field
>>>>>> (points, wireframe, surface) I get the following error.
>>>>>>
>>>>>> ERROR: In /tmp/ParaView-3.4.0/Servers/Common/vtkServerConnection.cxx,
>>>>>> line 67
>>>>>> vtkServerConnection (0x5df84f0): Server Connection Closed!
>>>>>>
>>>>>> step 4: when I do on the server
>>>>>> ------------------------------------------
>>>>>> ls -al /tmp/ParaView-3.4.0/Servers/Common/vtkServerConnection.cxx
>>>>>> I get
>>>>>> cannot access
>>>>>> /tmp/ParaView-3.4.0/Servers/Common/vtkServerConnection.cxx:
>>>>>> No
>>>>>> such file or directory
>>>>>>
>>>>>> step 5: If I copy all the vtu,...etc files to the client and open pv
>>>>>> ----------------------------------------------------------------------
>>>>>> 3.4.0, we can visualize the same data with no
>>>>>> problems (the paraview server on the server is not used).
>>>>>>
>>>>>> Can anyone help resolved the problem. I can send all the files to
>>>>>> anyone
>>>>>> who
>>>>>> will help resolve the problem.
>>>>>> Thanks,
>>>>>> Stephen
>>>>>> p.s.
>>>>>> The above works correctly with a small mesh (43,000 vertices) using
>>>>>> 8-procs.
>>>>>> The above was with a mesh (500,000 vertices)using 32-processors.
>>>>>>
>>>>>> _______________________________________________
>>>>>> ParaView mailing list
>>>>>> ParaView at paraview.org
>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> ParaView mailing list
>>>>> ParaView at paraview.org
>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>
>>>>>
>>>>
>>>>
>>
>>
>