[Paraview] Paraview with Ice-T IceT
Terry Jordan
tejj at hotmail.com
Tue Apr 26 08:44:49 EDT 2005
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
----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] Paraview with Ice-T IceT
Date: Fri, 22 Apr 2005 10:01:39 -0400
The ParaView Guide is available in print only. It is not available
electronically.
On 4/22/05, Terry Jordan <tejj at hotmail.com> wrote:
> I was unable to locate a "Paraview Guide". There is no documentation in
the
> binary release and if I go to paraview.org and hit documentation it takes
me
> to a hard copy book for $72. I am unable to locate an electronic copy of
> the documentation.
>
> ----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] Paraview with Ice-T IceT
> Date: Fri, 22 Apr 2005 09:26:10 -0400
>
> You need to run a server and a client. On the server, run pvserver
> with mpirun or your choice of mpi launcher. On the client, run
> pvclient with --server-host=first_node_of_server
> Make sure that you set the DISPLAY variables appropriately on the
> cluster. How you do this depends on your environment and mpi
> implementation. There are settings that control whether the geometry
> is sent to client to be rendered locally or rendering is done on the
> server and an image sent to client. These are on the 3D View
> Properties page.
> For more information, check the tooltip help as well as the ParaView
Guide.
>
> -Berk
>
> On 4/22/05, Terry Jordan <tejj at hotmail.com> wrote:
> > I am going to use 2.0.1. 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] Paraview with Ice-T IceT
> > Date: Fri, 22 Apr 2005 09:05:50 -0400
> >
> > Which version of paraview are you running? The command line arguments
> > changed between 1.8 and 2.0.
> >
> > -Berk
> >
> > On 4/22/05, Terry Jordan <tejj at hotmail.com> wrote:
> > > I am attempting to run paraview on a 6 node cluster from a 7th head
> node.
> > I
> > > want to use paraview to render the data on the cluster and ship
back
> the
> > > interractive images back to the head node. I know this is possible
> using
> > > paraview with ice-T but I cannot find any documents on it. Could
> someone
> > > please provide assistance.
> > >
> > > Thanks in advance.
> > >
> > > _______________________________________________
> > > 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
>
>
More information about the ParaView
mailing list