[Paraview] Paraview-3.12.0 Client-Server

Burlen Loring bloring at lbl.gov
Mon Feb 20 13:01:35 EST 2012


although, I guess that's not really consistent with your 3.10 install 
working... all the same you may find that the attached scripts help. 
Sorry for not reading your post closer the first time.

Burlen

On 02/20/2012 09:41 AM, Burlen Loring wrote:
> Hi Rakesh,
>
> It sounds as though the compute node cannot see your workstation 
> across the network. This is a common situation.
>
> for debugging the issue see if you could follow these steps:
> http://paraview.org/Wiki/Reverse_connection_and_port_forwarding#A_Forward_Connection_Over_an_ssh_Tunnel
>
> If that works you probably would like to automate the process using a 
> ParaView client side pvsc script to establish a reverse ssh tunnel to 
> the cluster's login node, which is presumably visible from the compute 
> nodes, and then tell the pv server to connect to this tunnel in a 
> server side startup script, which submits a batch job using a batch 
> script. I'm attaching an example from NERSC's Cray called franklin, 
> take a look and see if it helps.
>
> Burlen
>
> On 02/20/2012 08:53 AM, Rakesh Hammond wrote:
>> Hi,
>> I am trying to get ParaView-3.12.0 working on our visualisation 
>> cluster.  However I am getting errors such as the following
>> "Socket error in call to conect : Connection refused"
>> As a bit of a background, I have ParaView-3.10.1 working in 
>> client-server mode on the same cluster. On the server, we have 
>> IntelMPI-4.0.1 and Slurm as the scheduler.
>> I tried debugging the problem by printing stuff out in vtkSocket.cxx 
>> file - I always get the message which says "Connected" from slurm out 
>> file.  The ParaView-3.12.0 client then just hangs.
>> I did get it to work by using a machinefile (ie outside slurm) and it 
>> worked in client-server to my work station.
>> I am not really sure what is the cause of this - my suspicion is that 
>> this either to do with IntelMPI-4.0.1 and ParaView-3.12.0 or with 
>> Slurm-2.1.4 (which is what is available on the cluster).
>> Can some one please give me some hints how I can debug this further?
>> Any pointers are greately appreciated.
>> Given my level of desperation, I tried with Paraview-3.14.0-RC2 and 
>> things have really changed here - for example, what happend to the 
>> PV_CLIENT_HOST variable? Is this no longer set?
>> I also note that when you set up a profile to connect to the server 
>> in reverse-connection mode, it no longer allows you to specifiy host 
>> name - is this intentional?
>> Regards,
>> Rakesh
>>
>>
>> _______________________________________________
>> Powered bywww.kitware.com
>>
>> Visit other Kitware open-source projects athttp://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/20120220/1222c80f/attachment.htm>


More information about the ParaView mailing list