[Paraview] Not being able to connect to pvserver
Burlen Loring
bloring at lbl.gov
Thu Jan 31 12:32:51 EST 2013
Hi Pradeep,
> servermanger.Connect("amber")
>
> What is amber? I tried replacing it by the IP of my
> pvserver, the server name etc. but nothing seems to be working.
You'll make things immensely easier on yourself if you use ssh tunnels
for remote connections. In that case you connect to one end of the
tunnel bound to a port on your client ("localhost").
to answer your question: amber is a host name.
Re: questions about python, the best source of information is the file
"simple.py" in your source tree (in python cli there's also
"help(funcname)"). For example:
def Connect(ds_host=None, ds_port=11111, rs_host=None, rs_port=11111):
"""Creates a connection to a server. Example usage:
> Connect("amber") # Connect to a single server at default port
> Connect("amber", 12345) # Connect to a single server at port 12345
> Connect("amber", 11111, "vis_cluster", 11111) # connect to data
server, render server pair"""
> While connecting to my pvserver from the GUI, when I try to use the
> "-display" flag as mentioned on this page
> <http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#X_Connections> using
> the following command on my remote machine:
I've always managed to get by with the environment variable DISPLAY.
> Is this related to OSMesa? I still haven't installed PV with OSMesa
> support.
DISPLAY is an X11 parameter. With OSMesa you shouldn't need to set DISPLAY.
> * I am not able to reproduce this error all the time. But often,
> while I am working on my local client GUI connected to the
> pvserver, sometimes PV stops communicating to the server giving
> the following errors in the terminal:
>
>
> --------------------------------------------------------------------------------------------------------------------------------------
> ERROR: In
> /Users/pradeep/softwares/ParaView/VTK/Common/System/vtkSocket.cxx,
> line 572 vtkClientSocket (0x7fd0fcc3ef60): Socket error
> in call to send. Broken pipe.
99.999999999999% of the time that's a result of the server unexpectedly
terminating. You should be able to check the terminal output of the
server for clues about what happened.
On 01/31/2013 01:42 AM, Pradeep Jha wrote:
> Hello,
>
> I have some more questions.
>
> * How do I connect to the remote server using pvpython from command
> line? All the online instructions have this example:
>
>
> servermanger.Connect("amber")
>
> What is amber? I tried replacing it by the IP of my
> pvserver, the server name etc. but nothing seems to be working.
>
> * While connecting to my pvserver from the GUI, when I try to use
> the "-display" flag as mentioned on this page
> <http://www.paraview.org/Wiki/Setting_up_a_ParaView_Server#X_Connections> using
> the following command on my remote machine:
>
> "/usr/lib64/openmpi/1.4-gcc/bin//mpirun -np 1
> /usr/local/bin//pvserver -rc -ch=133.6.71.88 --server-port=11111
> -display:0.0"
>
> It doesn't work giving me the following error:
> "Got unknown argument: -display:0.0".
>
> Is this related to OSMesa? I still haven't installed PV
> with OSMesa support.
>
> * I am not able to reproduce this error all the time. But often,
> while I am working on my local client GUI connected to the
> pvserver, sometimes PV stops communicating to the server giving
> the following errors in the terminal:
>
>
> --------------------------------------------------------------------------------------------------------------------------------------
> ERROR: In
> /Users/pradeep/softwares/ParaView/VTK/Common/System/vtkSocket.cxx,
> line 572 vtkClientSocket (0x7fd0fcc3ef60): Socket error
> in call to send. Broken pipe.
>
> ERROR: In
> /Users/pradeep/softwares/ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
> line 735
> vtkSocketCommunicator (0x7fd0fcc366f0): Could not send tag.
>
> ERROR: In
> /Users/pradeep/softwares/ParaView/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
> line 812
> vtkSocketCommunicator (0x7fd0fcc366f0): Could not receive
> tag. 41232
>
> ERROR: In
> /Users/pradeep/softwares/ParaView/VTK/Common/System/vtkSocket.cxx,
> line 572
> vtkClientSocket (0x7fd0fcc3ef60): Socket error in call to
> send. Broken pipe.
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Right now this is happening quite randomly and I am not
> able to trace what exactly am I doing to cause this error.
>
> Thanks,
> Pradeep
>
>
> On 31 janv. 2013, at 10:27, Pradeep Jha
> <pradeep at ccs.engg.nagoya-u.ac.jp
> <mailto:pradeep at ccs.engg.nagoya-u.ac.jp>> wrote:
>
>> Thanks a lot for your detailed response Burlen.
>>
>>
>> 2013/1/31 Burlen Loring <bloring at lbl.gov <mailto:bloring at lbl.gov>>
>>
>>>
>>> Presently, I have PV 3.98 installed from source with MPI support
>>> on my local Mac and a remote Linux machine. I ran the pvsc file
>>> that you sent from my local Mac but I was not sure what goes in
>>> the input for "MPI Root" and "ParaView Root". I left those two
>>> fields blank and tried to connect and gave me the following error:
>> Sorry if that wasn't clear. for example if you have mpi installed
>> in "/op/mpi/mpich/1.4.1" then you put that for "MPI Root".
>> Likewise if you have your PV build at
>> "/home/pradeep/ParaView/3.98.0" you put that.
>>
>>
>> On 01/30/2013 01:40 AM, Pradeep Jha wrote:
>>> Hello Burlen,
>>>
>>> thanks for the detailed response. I am still not able to get it
>>> work and somethings are still not clear to me. I want to ask
>>> some very fundamental questions as this is my first time trying
>>> to set up a something over the networks myself and the online
>>> instructions are a bit too technical for me.
>>>
>>> Presently, I have PV 3.98 installed from source with MPI support
>>> on my local Mac and a remote Linux machine. I ran the pvsc file
>>> that you sent from my local Mac but I was not sure what goes in
>>> the input for "MPI Root" and "ParaView Root". I left those two
>>> fields blank and tried to connect and gave me the following error:
>>>
>>> ------------------------------------------------------------------------
>>> pradeep at laptop subset]$MPI_NP=4
>>> MPI_ROOT=
>>> PV_ROOT=
>>> PV_SERVER_PORT=11111
>>> REMOTE_USER=pradeep
>>> SERVER_HOST=83.shin.fluid.cse.nagoya-u.ac.jp
>>> <http://83.shin.fluid.cse.nagoya-u.ac.jp/>
>>> SSH_PATH=/usr/bin/ssh
>>> XTERM_PATH=/usr/bin/xterm
>>> Accepting connection(s): laptop.local:11111
>>> Server launch command is : /usr/bin/xterm -T "ParaView Server
>>> pradeep at 83.shin.fluid.cse.nagoya-u.ac.jp:11111
>>> <http://pradeep@83.shin.fluid.cse.nagoya-u.ac.jp:11111/>" -e
>>> /usr/bin/ssh -t -R 11111:localhost:11111
>>> pradeep at 83.shin.fluid.cse.nagoya-u.ac.jp
>>> <mailto:pradeep at 83.shin.fluid.cse.nagoya-u.ac.jp> DISPLAY=:0
>>> xhost + ;
>>> LD_LIBRARY_PATH=/lib:/lib/paraview-3.98/:LD_LIBRARY_PATH
>>> DISPLAY=:0 /bin/mpirun -np 4 /bin/pvserver --reverse-connection
>>> --server-port=11111 --client-host=localhost
>>> The process failed to start. Either the invoked program is
>>> missing, or you may have insufficient permissions to invoke the
>>> program.
>>> Server launch timed out.
>>> ---------------------------------------------------------------------------
>>>
>>> Here are my questions:
>>>
>>> 1. How do I get the above thing working?
>>> 2. What did you mean by "Production setting"?
>>> 3. I am right now testing PV on small test cases over machines
>>> (my Mac and the remote Linux) which have both graphics
>>> hardware. For such a case why do I need "reverse
>>> connection"? Should I always use "reverse connection"?
>>> 4. I don't understand when I initiate a pvserver on the remote
>>> Linux machine and try to connect it from local Mac, why
>>> doesn't it ask for a password?
>>> 5. My understanding is that when I get this connection going,
>>> all my data should be on the server. I simply use the local
>>> Mac GUI and I should be able to visualize and browse through
>>> data at the remote end. Is that correct?
>>> 6. When I am at lab, I have a static IP for my Mac and I can
>>> log into it from other computers. But I cannot access my Mac
>>> from outside when I am not in the lab. Does this mean I
>>> cannot use pvserver outside the lab? Or is this link
>>> <https://hpcforge.org/plugins/mediawiki/wiki/pv-meshless/index.php/Launching_ParaView_on_HPC_Machines#Step_2>
>>> is talking about this problem?
>>> 7.
>>> Once I manage to understand and get it working, I want to
>>> use PV using a supercomputing facility. On the
>>> supercomputing facility I can install PV on my login node
>>> (which has 64 processors) but not on the supercomputing
>>> cluster. If I want to use the cluster (which has around
>>> 50,000 processors) to visualize a big
>>> data (around 800GB if possible), will installing Paraview
>>> with MPI support on the login node, which is accesible by
>>> the cluster, be sufficient?
>>>
>>> I guess these questions are extremely basic but I am responsible
>>> for figuring this whole thing out myself and with not much
>>> direct experience in networking. So it is troubling me a bit.
>>>
>>> Hoping to hear from you,
>>> Pradeep
>>>
>>>
>>> 2013/1/30 Burlen Loring <bloring at lbl.gov <mailto:bloring at lbl.gov>>
>>>
>>> Hi Pradeep,
>>>
>>>
>>> vtkClientSocket (0x7fc9ae108cb0): Socket error in call
>>> to connect. Permission denied.
>>>
>>>
>>> Your connection is being blocked somewhere in between your
>>> compute node and workstation. there are various
>>> configuration setting on either/both client and server that
>>> could cause it. Fortunately we do not need to change any of
>>> these settings , many of which require root access and
>>> potentially open security vulnerabilities. Instead, you will
>>> use an ssh tunnel and a server config (pvsc) tailored to
>>> your situation to automate the process.
>>>
>>> I'm attaching a minimal pvsc that illustrates how one might
>>> configure a reverse connection to a server with graphics
>>> hardware. This pvsc is for illustration only, don't use in
>>> a production setting! There are number of liberties I've
>>> taken, for example I assume that X11 is already running, and
>>> I use "xhost +"(very very bad) to enable pvserver to access
>>> gpu's. Normally I would put all of the server side stuff in
>>> a shell script. I didn't do that here to keep things simple
>>> for you. I hope you can use this to understand how PV works.
>>>
>>>
>>> 1) I connect to the CentOS machine using "ssh -X
>>> machinename".
>>>
>>> Don't do that. With -X forwarding you won't be taking
>>> advantage of your cluster's graphics hardware.
>>>
>>> Hope this helps
>>> Burlen
>>>
>>>
>>> On 01/29/2013 06:41 AM, Utkarsh Ayachit wrote:
>>>
>>> Doesn't look like your client machine can connect to the
>>> server
>>> machine. From the client machine try:
>>>
>>> ping 83.shin.fluid.cse.nagoya-u.ac.jp
>>> <http://83.shin.fluid.cse.nagoya-u.ac.jp/>
>>> telnet 83.shin.fluid.cse.nagoya-u.ac.jp
>>> <http://83.shin.fluid.cse.nagoya-u.ac.jp/> 11111
>>>
>>>
>>>
>>> On Tue, Jan 29, 2013 at 4:58 AM, Pradeep Jha
>>> <pradeep at ccs.engg.nagoya-u.ac.jp
>>> <mailto:pradeep at ccs.engg.nagoya-u.ac.jp>> wrote:
>>>
>>> Hello,
>>>
>>> I have installed Paraview 3.98 on my Desktop (Mac
>>> OSX 10.8) and a remote
>>> machine running CentOS 5.4. The CentOS machine has
>>> rendering hardware so I
>>> havent installed PV with OSMesa support.
>>>
>>> I can login to the CentOS from my Mac using SSH and
>>> vice versa.
>>>
>>> Here is how I am trying to connect:
>>>
>>> 1) I connect to the CentOS machine using "ssh -X
>>> machinename". When I start
>>> the "pvserver" on the CentOS the output is:
>>> -------------------------------------------------------------------
>>> [pradeep at 83 ~]$pvserver
>>> Waiting for client...
>>> Connection URL:
>>> cs://83.shin.fluid.cse.nagoya-u.ac.jp:11111
>>> <http://83.shin.fluid.cse.nagoya-u.ac.jp:11111/>
>>> Accepting connection(s):
>>> 83.shin.fluid.cse.nagoya-u.ac.jp:11111
>>> <http://83.shin.fluid.cse.nagoya-u.ac.jp:11111/>
>>> -------------------------------------------------------------------
>>>
>>> 2) Then I add this information in the paraview I am
>>> running on my Mac as
>>> shown in the attached image file.
>>>
>>> 3) I click on connect.
>>>
>>> I get the following error:
>>> ------------------------------------------------------------------------
>>> ERROR: In
>>> /Users/pradeep/softwares/ParaView/VTK/Common/System/vtkSocket.cxx,
>>> line 481
>>> vtkClientSocket (0x7fc9ae108cb0): Socket error in
>>> call to connect.
>>> Permission denied.
>>> -----------------------------------------------------------------------
>>>
>>> I dont have any expertise in networking and so I
>>> dont know much about
>>> firewalls of my systems here nor do any my
>>> colleagues do.
>>>
>>> Thanks in advance,
>>> Pradeep
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by 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
>>>
>>> _______________________________________________
>>> Powered by 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
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> Powered by 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/20130131/ecd343b0/attachment-0001.htm>
More information about the ParaView
mailing list