[Paraview] Re: Paraview with MPI Ice-T vtkXOpenGLRenderWindow
(0x9cdb0a0): bad X server con
Terry Jordan
tejj at hotmail.com
Tue Apr 26 17:54:42 EDT 2005
Thanks for your help.
I am using .bash_profile. I have set DISPLAY=:0.0. I am able to run
"paraview" remote with rsh. Paraview pops up on the remote with no OpenGL
errors.
As you pointed out, there is no electronic guide/documentation. Also there
is no budget to plunk down $72 on a guide for 1.8 and I am running 2.0. I
find it strange anyhow that they would produce a retail guide for open
source software that is updated/changed every couple months.
Any ideas?
Thanks.
----Original Message Follows----
From: Berk Geveci <berk.geveci at gmail.com>
Reply-To: Berk Geveci <berk.geveci at gmail.com>
To: Terry Jordan <tejj at hotmail.com>
CC: paraview at paraview.org
Subject: Re: Paraview with MPI Ice-T vtkXOpenGLRenderWindow (0x9cdb0a0): bad
X server connect
Date: Tue, 26 Apr 2005 15:14:41 -0600
It looks like your displays (DISPLAY env variable) are not set
correctly. The way to do this depends on the mpi implementation.
Something like:
export DISPLAY=:0
in your .XXXshrc file might work. Each node has to have access to a
separate display when doing compositing.
As I mentioned before, this is described in more detail in the ParaView
guide.
-Berk
On 4/26/05, Terry Jordan <tejj at hotmail.com> wrote:
> I got it to build and everything works fine until I try to do a parallel
> rendering with composite. I set the composite down to 0MB to make sure
it
> is doing compositing on all data sets. So it crashes with the following
> errors:
>
> # mpirun -np 6 -machinefile /root/pv.nodefile
> /usr/local/paraview-2.0.1/bin/pvserver
> Listen on port: 11111
> Waiting for client...
> connected to port 11111
> Client connected.
> Process id: 1 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb4d0): bad X server connection.
>
>
> Process id: 1 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb4d0): bad X server connection.
>
>
> p1_27744: p4_error: interrupt SIGSEGV: 11
> Process id: 4 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 4 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p4_27720: p4_error: interrupt SIGSEGV: 11
> Process id: 3 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 3 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p3_27132: p4_error: interrupt SIGSEGV: 11
> Process id: 5 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 5 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p5_27784: p4_error: interrupt SIGSEGV: 11
> Process id: 2 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 2 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p2_26745: p4_error: interrupt SIGSEGV: 11
> ids1:~ # mpirun -np 6 -machinefile /root/pv.nodefile
> /usr/local/paraview-2.0.1/bin/pvserver
> Listen on port: 11111
> Waiting for client...
> connected to port 11111
> Client connected.
> Process id: 1 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 1 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p1_31796: p4_error: interrupt SIGSEGV: 11
> Process id: 2 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 2 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p2_31004: p4_error: interrupt SIGSEGV: 11
> Process id: 4 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 4 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p4_31161: p4_error: interrupt SIGSEGV: 11
> Process id: 3 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 3 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p3_30222: p4_error: interrupt SIGSEGV: 11
> Process id: 5 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
326
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> Process id: 5 >> ERROR: In
> /scratch/paraview-2.0.1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line
169
> vtkXOpenGLRenderWindow (0x9cdb0a0): bad X server connection.
>
>
> p5_31433: p4_error: interrupt SIGSEGV: 11
>
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>
More information about the ParaView
mailing list