Re: [Paraview] bug in ParaView 3.4.0 server
Maybe a bug in the Mesa implementation? Or somehow a mismatch between OpenGL libraries? Can you try to compile the latest Mesa from source and use that? -berk On Thu, Jan 22, 2009 at 4:07 AM, Nicolas Niclausse nicolas.niclau...@sophia.inria.fr wrote: Berk Geveci ecrivait le 29.12.2008 22:54: Looking more carefully at the server errors, it looks like you are running a server that is not MPI enabled. Yes, you were right. The builds fails to use MPI; I was using VTK_USE_MPI instead of PARAVIEW_USE_MPI (it did not complain, and build everything without mpi) Now it works much better, however: - it crash when the client connects if I use the --use-offscreen-rendering option : mpiexec: Warning: tasks 0-1 died with signal 11 (Segmentation fault) using pvserver with gdb: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912515311328 (LWP 8537)] 0x003e3de53637 in glMatrixMode () from /usr/lib64/libGL.so.1 (gdb) bt #0 0x003e3de53637 in glMatrixMode () from /usr/lib64/libGL.so.1 #1 0x01b6a266 in vtkOpenGLRenderWindow::OpenGLInit () #2 0x01b8884d in vtkXOpenGLRenderWindow::Start () #3 0x01afb820 in vtkRenderWindow::DoStereoRender () #4 0x01afb713 in vtkRenderWindow::DoFDRender () #5 0x01afc4d6 in vtkRenderWindow::DoAARender () #6 0x01afac8e in vtkRenderWindow::Render () #7 0x01b893e0 in vtkXOpenGLRenderWindow::Render () #8 0x019d509e in vtkMultiProcessController::ProcessRMI () #9 0x019d553b in vtkMultiProcessController::ProcessRMIs () #10 0x00a76404 in vtkRemoteConnection::ProcessCommunication () #11 0x00a419a7 in vtkProcessModuleConnectionManager::MonitorConnections () #12 0x00a47558 in vtkProcessModule::StartServer () #13 0x00a46f61 in vtkProcessModule::Start () #14 0x00a89c09 in vtkPVMain::Run () #15 0x00a328ab in main () /usr/lib64/libGL.so.1 comes from: mesa-libGL-6.5.2-10.fc7 Without the option, a warning message remote rendering disabled pops up, but everything seems to work fine. -- Nicolas NICLAUSSE Service DREAM INRIA Sophia Antipolis http://www-sop.inria.fr/ 2004 route des lucioles - BP 93Tel: (33/0) 4 92 38 76 93 06902 SOPHIA-ANTIPOLIS cedex (France) Fax: (33/0) 4 92 38 76 02 ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] bug in ParaView 3.4.0 server
Looking more carefully at the server errors, it looks like you are running a server that is not MPI enabled. In fact, it looks like the pvserver from our binary distribution. Each server node is reporting the following error: ERROR: In /tmp/ParaView-3.4.0/Servers/Common/vtkProcessModuleConnectionManager.cxx, line 180 vtkProcessModuleConnectionManager (0x15bcfe60): Failed to set up server socket. Only the first node is supposed to execute that code. Also, the path of the error is the path we used to build our binaries which is unlikely to be the same as yours. Can you verify that /usr/local/paraview/bin/pvserver (the one in Stephen's PBS script) is the right executable? Nicolas sent the ldd output of /home/install/paraview-340/bin/pvserver. -berk On Fri, Dec 19, 2008 at 7:44 AM, Nicolas Niclausse nicolas.niclau...@sophia.inria.fr wrote: Berk Geveci ecrivait le 17.12.2008 19:02: Can you send us the CMakeCache.txt file from your build? On the server, can you run pvserver --ldd and send us the output? If pvserver --ldd fails, try ldd pvserver ldd /home/install/paraview-340/bin/pvserver libhistory.so.5 = /usr/lib64/libhistory.so.5 (0x2aabe000) libreadline.so.5 = /usr/lib64/libreadline.so.5 (0x003e40a0) libGL.so.1 = /usr/lib64/libGL.so.1 (0x003e3de0) libOSMesa.so.6 = /usr/lib64/libOSMesa.so.6 (0x2acc7000) libXt.so.6 = /usr/lib64/libXt.so.6 (0x003e3f60) libSM.so.6 = /usr/lib64/libSM.so.6 (0x003e4060) libICE.so.6 = /usr/lib64/libICE.so.6 (0x003e3fe0) libX11.so.6 = /usr/lib64/libX11.so.6 (0x003e3d20) libXext.so.6 = /usr/lib64/libXext.so.6 (0x003e3ee0) libpthread.so.0 = /lib64/libpthread.so.0 (0x003e3ca0) libm.so.6 = /lib64/libm.so.6 (0x003e3c20) libdl.so.2 = /lib64/libdl.so.2 (0x003e3be0) libstdc++.so.6 = /usr/lib64/libstdc++.so.6 (0x00346020) libgcc_s.so.1 = /lib64/libgcc_s.so.1 (0x00345fe0) libc.so.6 = /lib64/libc.so.6 (0x003e3ba0) libtinfo.so.5 = /lib64/libtinfo.so.5 (0x003e3ea0) libXxf86vm.so.1 = /usr/lib64/libXxf86vm.so.1 (0x003e3d60) libdrm.so.2 = /usr/lib64/libdrm.so.2 (0x003e3c60) libselinux.so.1 = /lib64/libselinux.so.1 (0x003e3ce0) libXau.so.6 = /usr/lib64/libXau.so.6 (0x2b109000) libXdmcp.so.6 = /usr/lib64/libXdmcp.so.6 (0x003e3da0) /lib64/ld-linux-x86-64.so.2 (0x003e3b60) libsepol.so.1 = /lib64/libsepol.so.1 (0x2b30b000) compiled on a fedora 7 x86-64 OS, using gcc (4.1.2 20070925) and mpich2. cmake args: cmake .. \ -DCMAKE_CXX_FLAGS:STRING=-DMPICH_IGNORE_CXX_SEEK \ -DCMAKE_EXE_LINKER_FLAGS:STRING=-L/usr/lib64 \ -DCMAKE_INSTALL_PREFIX:PATH=/usr/local/paraview \ -DCMAKE_MODULE_LINKER_FLAGS:STRING=-L/usr/lib64 \ -DCMAKE_SHARED_LINKER_FLAGS:STRING=-L/usr/lib64 \ -DMPI_INCLUDE_PATH:PATH=/opt/mpich2/gnu/include \ -DMPI_LIBRARY:FILEPATH=/opt/mpich2/gnu/lib/libmpich.a \ -DOPENGL_gl_LIBRARY:FILEPATH=/usr/lib64/libGL.so \ -DOPENGL_glu_LIBRARY:FILEPATH=/usr/lib64/libGLU.so \ -DVTK_MPIRUN_EXE:FILEPATH=/opt/mpich2/gnu/bin/mpirun \ -DVTK_MPI_NUMPROC_FLAG:STRING=-np \ -DVTK_USE_64BIT_IDS:BOOL=ON \ -DVTK_USE_MPI:BOOL=ON \ -DVTK_OPENGL_HAS_OSMESA:BOOL=ON \ -DX11_X11_LIB:FILEPATH=/usr/lib64/libX11.so \ -DX11_Xext_LIB:FILEPATH=/usr/lib64/libXext.so we are using offline-rendering with pvserver. -- Nicolas NICLAUSSE Service DREAM INRIA Sophia Antipolis http://www-sop.inria.fr/ 2004 route des lucioles - BP 93Tel: (33/0) 4 92 38 76 93 06902 SOPHIA-ANTIPOLIS cedex (France) Fax: (33/0) 4 92 38 76 02 ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
[Paraview] bug in ParaView 3.4.0 server
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@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] bug in ParaView 3.4.0 server
Is there any error message shown on the server? Doesn't look like you are able to render on the server. Utkarsh On Wed, Dec 17, 2008 at 10:29 AM, Stephen Wornom stephen.wor...@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.wor...@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@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] bug in ParaView 3.4.0 server
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.ayac...@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.wor...@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.wor...@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
Re: [Paraview] bug in ParaView 3.4.0 server
Can you send us the CMakeCache.txt file from your build? On the server, can you run pvserver --ldd and send us the output? If pvserver --ldd fails, try ldd pvserver -berk On Wed, Dec 17, 2008 at 3:46 AM, Stephen Wornom stephen.wor...@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@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] bug in ParaView 3.4.0 server
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.wor...@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@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] bug in ParaView 3.4.0 server
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.wor...@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.wor...@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.wor...@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
Re: [Paraview] bug in ParaView 3.4.0 server
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. 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.wor...@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@paraview.org http://www.paraview.org/mailman/listinfo/paraview ___ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview
