[Paraview] running paraview in parallel
Vishwa
dagarshali at gmail.com
Sun Feb 28 18:50:40 EST 2010
Hi,
when i try to compile mesa under redhat x-86-64 using make linux-x86-64, i
get linker errors among several .o files in src/mesa/drivers/x11 (fakeglx.o,
glxapi.o etc..) the output being multiple definitions of gnu_dev_major,
strings files etc..)
Any idea as to why this is happening..?
Regards,
Vishwa
On Sat, Feb 27, 2010 at 4:17 PM, burlen <burlen.loring at gmail.com> wrote:
> If I were you I'd get your local build of mesa going and use that (simply
> to remove all ambiguity).
>
> Were you using autotools method (eg ./configure && make) or the canned
> configurations (eg make linux)?
>
> In my experience, and I have heard of others having issues too, the
> autotools method fails. So if you were using the autotools method, then I
> suggest you try the canned configs. Do a fresh untar of mesa, cd in and try
> "make linux" (or choose one of the other configs if you like).
> When you rebuild PV be sure about the configuration in ccmake and set
> LD_LIBRARY_PATH as I mentioned before.
>
> Vishwa wrote:
>
>> I tried to install mesa locally also.. at which point it kept saying it
>> needs libdrm, and when i tried to install libdrm, it kept complaining that
>> it coudn't find pthreads-stubs.pc..so i ended up using the system mesa
>>
>> Regards,
>> Vishwa
>>
>> On Sat, Feb 27, 2010 at 3:24 PM, burlen <burlen.loring at gmail.com <mailto:
>> burlen.loring at gmail.com>> wrote:
>>
>> It's really not info info for me to give you any specific advise.
>> But my best guess is that at run time the wrong open gl liibraries
>> are being loaded. That will crash PV. You want the mesa libraries
>> from your local mesa build to be loaded, you have to prepend its
>> path to LD_LIBRARY_PATH environment var. Also double check in
>> ccmake, that all of the opengl libs come from your mesa build.
>>
>> Vishwa wrote:
>>
>>
>> The problem is that it keeps complaining about not having many
>> library files..I tried and installed them..now, when i
>> compiled, it didnt' give an error..but when opened it gave
>> segmentation fault.. i read somewhere online that u need to
>> use unlimit stacksize, which I did and still doesnt work.
>>
>> i had used -mpi opition and also to use mesa ..
>>
>> hit a wall again..
>>
>> Regards,
>> vishwa
>>
>> On Sat, Feb 27, 2010 at 3:12 PM, burlen
>> <burlen.loring at gmail.com <mailto:burlen.loring at gmail.com>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>>> wrote:
>>
>> Apparently your cluster doesn't have X11 server started.
>> The error
>> message reports this path because __FILE__ cpp macro is used.
>>
>> Question: Why is it a problem to install and run ParaView from
>> your home folder? It should be OK.
>>
>> Vishwa wrote:
>>
>> Thankyou all for responding again..:)
>>
>> I tried to compile paraview and to only hit a wall
>> after wall
>> as I have to install it to my local folder due to not
>> having
>> administrator privileges..
>>
>> so i downloaded the binaries last night and checked that it
>> worked..
>>
>> Today to my surprise, when i try to open paraview in
>> the hpc
>> headnode, where i downloaded the binaries, it gives the
>> following error..
>>
>> [vishwa at hpc4 ~]$ paraview
>> ERROR: In
>>
>> /home/kitware/ParaView-3.6/ParaView3/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
>> line 632
>> vtkXOpenGLRenderWindow (0x143bb10): Cannot create GLX
>> context. Aborting.
>>
>>
>> and i dont' have /home/kitware etc...directory...so i dont
>> understand what is happening..
>>
>> I made sure that i included the path of the bin and lib
>> in the
>> newly downloaded binary..
>>
>> Any suggestions?
>>
>> Regards,
>> vishwa
>>
>> On Sat, Feb 27, 2010 at 2:38 PM, burlen
>> <burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>
>> <mailto:burlen.loring at gmail.com <mailto:burlen.loring at gmail.com>>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>>>> wrote:
>>
>> Also be aware that there is a bug in ParaView, where
>> if the
>> server
>> startup command doesn't return for some reason, ssh
>> turns
>> into an
>> orphan process and will not relinquish the ports it
>> used,
>> preventing any further use of those ports.
>>
>> http://www.paraview.org/Bug/view.php?id=10283
>>
>> I did submit a patch to fix it but it has yet to be
>> applied.
>>
>>
>> burlen wrote:
>>
>> Your command isn't quite right, specifically how
>> you are
>> trying to specify the compute node.
>>
>> Take a look at the section here,
>>
>> http://paraview.org/Wiki/Reverse_connection_and_port_forwarding#Reverse_Connection_Over_an_ssh_Tunnel
>>
>>
>> It's a little closer to your situation.
>>
>> Vishwa wrote:
>>
>> Hi,
>> Thanks for the reply..I did look at the wiki and
>> tried the
>> following..
>>
>> I set up a server/client reverse connection and
>> trired to
>> connect.. but i coudn't.. this was the
>> command that
>> i gave
>> for the server.. olivegarden is the hostname
>> of my
>> laptop.
>>
>> ssh -i /home/dagarshali/.ssh/id_rsa
>> vishwa at hpc4.iastate.edu
>> <mailto:vishwa at hpc4.iastate.edu>
>> <mailto:vishwa at hpc4.iastate.edu
>> <mailto:vishwa at hpc4.iastate.edu>>
>> <mailto:vishwa at hpc4.iastate.edu
>> <mailto:vishwa at hpc4.iastate.edu>
>> <mailto:vishwa at hpc4.iastate.edu <mailto:vishwa at hpc4.iastate.edu>>>
>> <mailto:vishwa at hpc4.iastate.edu
>> <mailto:vishwa at hpc4.iastate.edu>
>> <mailto:vishwa at hpc4.iastate.edu
>> <mailto:vishwa at hpc4.iastate.edu>>
>> <mailto:vishwa at hpc4.iastate.edu
>> <mailto:vishwa at hpc4.iastate.edu>
>> <mailto:vishwa at hpc4.iastate.edu
>> <mailto:vishwa at hpc4.iastate.edu>>>> node083 pvserver
>> --reverse-connection --server-port=11111
>> --client-host=olivegarden
>>
>> here node083 is the node where the pvserver was
>> launched...
>>
>> so wasn't sure how to give that info in this
>> command.. or
>> am i doing something wrong.. when you say that
>> start the
>> cient, am i just creating a server/client and
>> connect in
>> manual mode..?
>>
>> Regards,
>> Vishwa
>>
>>
>>
>>
>>
>> On Sat, Feb 27, 2010 at 1:00 PM, burlen
>> <burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>
>> <mailto:burlen.loring at gmail.com <mailto:burlen.loring at gmail.com>>>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>
>> <mailto:burlen.loring at gmail.com
>> <mailto:burlen.loring at gmail.com>>>>> wrote:
>>
>> By the way a number of common scenarios,
>> issues and
>> solutions are
>> explained on the wiki
>>
>>
>> http://paraview.org/Wiki/Reverse_connection_and_port_forwarding
>>
>> Hope this helps
>>
>> Moreland, Kenneth wrote:
>>
>> Currently you are not launching the
>> server
>> in reverse
>> connection mode. To launch the server in
>> reverse
>> connection
>> mode, you need to give it the
>> arguments -rc (or
>> --reverse-connection) and
>> --client-host=/laptop.hostname.com/
>> <http://laptop.hostname.com/>
>> <http://laptop.hostname.com/>
>> <http://laptop.hostname.com/>
>> <http://laptop.hostname.com/>. When
>> given these
>> arguments,
>> the server will immediately try to make a
>> connection to
>> /laptop.hostname.com/
>> <http://laptop.hostname.com/>
>> <http://laptop.hostname.com/> <http://laptop.hostname.com/>
>> <http://laptop.hostname.com/>. Thus,
>> you first need to have your client
>> running and
>> waiting for the
>> server to connect. After getting
>> things set up,
>> you should
>> eventually try to set up your client to
>> automatically start
>> the server with an ssh call and then wait
>> for the
>> server to
>> connect back.
>>
>> -Ken
>>
>>
>> On 2/27/10 9:11 AM, "Vishwa"
>> <dagarshali at gmail.com <mailto:dagarshali at gmail.com>
>> <mailto:dagarshali at gmail.com <mailto:dagarshali at gmail.com>>
>> <mailto:dagarshali at gmail.com
>> <mailto:dagarshali at gmail.com>
>> <mailto:dagarshali at gmail.com
>> <mailto:dagarshali at gmail.com>>>
>> <mailto:dagarshali at gmail.com
>> <mailto:dagarshali at gmail.com>
>> <mailto:dagarshali at gmail.com <mailto:dagarshali at gmail.com>>
>>
>> <mailto:dagarshali at gmail.com
>> <mailto:dagarshali at gmail.com>
>> <mailto:dagarshali at gmail.com
>> <mailto:dagarshali at gmail.com>>>>> wrote:
>>
>> Hi,
>> I would to visualize the data that
>> is being
>> computed on a
>> hpc by
>> using pvserver and paraview.
>>
>> i have come across a many documents
>> saying how
>> to connect
>> and the
>> one what i thought might be
>> appropriate in my
>> case would to
>> be to
>> run pvserver on the hpc and then
>> connect
>> to it usind
>> server/client
>> reverse connection from my desktop..
>>
>> here is the procedure that i use to
>> connect to
>> the hpc to
>> submit job.
>>
>> i log in to the head node via ssh
>> john at a.b.c.d
>>
>> i then submit my job using the the
>> following
>> script via
>> qsub myscript
>>
>>
>> *#PBS
>>
>> -lmem=2Gb,nodes=1:ppn=4,cput=24:00:00,walltime=24:00:00
>> cd $PBS_O_WORKDIR
>>
>> cat ${PBS_NODEFILE} > node1
>> mpirun --machinefile
>> ${PBS_NODEFILE} -np
>> 4 pvserver
>> --use-offscreen-rendering -\
>> -server-port=11111 >log1
>> *
>> in the node1 file, i get say
>> node083 (and
>> it is
>> repeated 4
>> times)
>>
>> I am not sure how to connect to
>> this node
>> say by
>> running
>> paraview
>> from my laptop to visualize that.
>>
>> Any help would be greatly
>> appreciated..
>>
>> Regards,
>> vishwa
>>
>>
>>
>> **** Kenneth Moreland
>> *** Sandia National Laboratories
>> *********** *** *** *** email:
>> kmorel at sandia.gov <mailto:kmorel at sandia.gov>
>> <mailto:kmorel at sandia.gov <mailto:kmorel at sandia.gov>>
>> <mailto:kmorel at sandia.gov
>> <mailto:kmorel at sandia.gov> <mailto:kmorel at sandia.gov
>> <mailto:kmorel at sandia.gov>>>
>> <mailto:kmorel at sandia.gov
>> <mailto:kmorel at sandia.gov>
>> <mailto:kmorel at sandia.gov <mailto:kmorel at sandia.gov>>
>> <mailto:kmorel at sandia.gov <mailto:kmorel at sandia.gov>
>> <mailto:kmorel at sandia.gov <mailto:kmorel at sandia.gov>>>>
>>
>>
>> ** *** ** phone: (505) 844-8919
>> *** web:
>> http://www.cs.unm.edu/~kmorel <http://www.cs.unm.edu/%7Ekmorel>
>> <http://www.cs.unm.edu/%7Ekmorel>
>> <http://www.cs.unm.edu/%7Ekmorel>
>> <http://www.cs.unm.edu/%7Ekmorel>
>> <http://www.cs.unm.edu/%7Ekmorel>
>> <http://www.cs.unm.edu/%7Ekmorel>
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>> <http://www.kitware.com>
>> <http://www.kitware.com> <http://www.kitware.com>
>> <http://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
>>
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20100228/351f9605/attachment-0001.htm>
More information about the ParaView
mailing list