[Paraview] [EXTERNAL] Re: Port number

Scott, W Alan wascott at sandia.gov
Wed Jul 31 20:28:54 EDT 2013


After a bit of experimentation, it turns out that ParaView local client, remote pvserver - once it makes the connection - does not tie up the 11111 port with recent versions of ParaView.  However, as you are waiting for the connection (or if the connection fails and you keep the client open), the ParaView port (11111) will be tied up and others won't be able to start a remote connection.

With a little help from my friends (Ummm ... thanks as always, Utkarsh), the trick is as follows.  We are trying to execute a command line, reverse connected remote server on a different port than 11111.  We will connect to port 11110.

To tell if port 11110 is busy, use netstat:

Not busy:
>  netstat -l -n --protocol=inet | egrep 11110

Busy:
>  netstat -l -n --protocol=inet | egrep 11110
tcp        0      0 0.0.0.0:11111               0.0.0.0:*                   LISTEN


Now, let's make the connection:

Client side:
> paraview -url=csrc://localhost:11110

Server side (with appropriate MPI submittal and other support):
> pvserver --use-offscreen-rendering -rc -ch=your-client-computer:11110

Connects!

Alan



From: Angelini, Richard C (Rick) CIV USARMY ARL (US) [mailto:richard.c.angelini.civ at mail.mil]
Sent: Wednesday, July 31, 2013 11:11 AM
To: Scott, W Alan; DeMarle, David Edward (External Contacts)
Cc: paraview at paraview.org
Subject: RE: [Paraview] [EXTERNAL] Re: Port number

I set them randomly in my host PVSC file:

        <Option name="PV_SERVER_PORT" label="Local port number" save="false">
          <Range type="int" min="1025" max="65535" step="1" default="random"/>
        </Option>
        <Option name="SERVER_PORT" label="Remote port number" save="false">
          <Range type="int" min="1025" max="65535" step="1" default="random"/>
        </Option>

________________________________
Rick Angelini

USArmy Research Laboratory
CISD/HPC Architectures Team
Building 120 Cube 315
Phone:  410-278-6266
________________________________
From: paraview-bounces at paraview.org [paraview-bounces at paraview.org] on behalf of Scott, W Alan [wascott at sandia.gov]
Sent: Wednesday, July 31, 2013 12:58 PM
To: DeMarle, David Edward (External Contacts)
Cc: paraview at paraview.org
Subject: Re: [Paraview] [EXTERNAL] Re: Port number
Thanks David!

Unfortunately, I am trying to automate the process, thus need to set the client side port number by command line or environment variable.  The user won't even know the port number I am using.  Further, it may/will change every run.

Any idea how to set the client side port number through command line?

Alan

From: David E DeMarle [mailto:dave.demarle at kitware.com]
Sent: Tuesday, July 30, 2013 8:55 PM
To: Scott, W Alan
Cc: paraview at paraview.org
Subject: [EXTERNAL] Re: [Paraview] Port number

In the Edit Server Configuration dialog with a Client / Server (reverse connection) server type, enter the desired port number. The client will then wait on that port for the server to connect back to it.

Afterward start up pvserver with arguments of "-rc -sp=port#" to make it connect to the waiting client on the specified port number.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Tue, Jul 30, 2013 at 7:47 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
Is there a way to tell ParaView what port to use on the client side, as well as the server side, for reverse connect remote pvserver paraview?

Thanks,

Alan




_______________________________________________
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/20130801/62b86c4f/attachment-0001.htm>


More information about the ParaView mailing list