[Paraview] Connecting to Catalyst-Enabled Simulation Running on Remote Cluster

[Timo Oster]

Hi,

I have indeed run into the problem with "Could not receive tag. 1". In
my case I had to make sure that the client and server versions were
exactly the same. When connecting, the vtkSocketCommunicators on client
and server exchange a version hash that must match. This hash is
generated while building ParaView. The file that is generated can be
found in your build directory under
VTK/Parallel/Core/vtkSocketCommunicatorHash.h. Check that your client
and server have the same hash value in this file.

I am assuming that you have correctly set up an ssh tunnel between
client and server to enable the connection (ssh -L 11111:localhost:11111
user at server). The steps I take to run a in-situ case on a single remote
workstation are listed in my previous mail.

BTW I am using the "trunk" version of ParaView from the git repository,
which is close to version 4.3.1, and I'm running Linux on both client
and server (different distributions).

Regards,

Timo

On 05/19/2015 06:57 PM, u.utku.turuncoglu at be.itu.edu.tr wrote:
> Hi Timo,
> 
> Have you ever tried to test Catalyst examples in your case.
> 
> https://github.com/Kitware/ParaViewCatalystExampleCode
> 
> I am also trying to run Catalyst examples but i could not. In my case, i
> am able to install Paraview (4.3.1) from source under Mac OS 10.10 and the
> Catalys examples but when i try to run the examples i am getting error
> like,
> 
> ERROR: In
> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx,
> line 812
> vtkSocketCommunicator (0x7f86a52658e0): Could not receive tag. 1
> 
> or
> 
> ERROR: In
> /Users/turuncu/Qsync/progs/paraview-4.3.1/src/VTK/Common/System/vtkSocket.cxx,
> line 572
> vtkClientSocket (0x7fcefc939fe0): Socket error in call to send. Broken pipe.
> 
> So, if you don't mind could you share the details of your work environment
> (OS, Paraview version, etc.) and the steps to run the in-situ example. So,
> that could also help me to find the source of the problem.
> 
> Regards,
> 
> --ufuk
> 
>> Hi all,
>>
>> in an effort to enable live visualization of our simulation code, I have
>> written a Catalyst adaptor for it. The live visualization is working
>> great when the ParaView client runs on the same machine as the
>> simulation, even when the simulation runs in parallel using mpi.
>>
>> Now I want to do live visualization of a simulation running on a remote
>> cluster. I am able to get this to work for the simulation running on the
>> login node of the cluster:
>>
>> 1. Tunnel an ssh connection of port 11111 to the cluster:
>>     ssh -L 11111:localhost:11111 server
>> 2. In the shell that opens, start a paraview server (in the background
>> with '&')
>> 3. Run the simulation with mpirun (simulation runs only on login node)
>> 4. Start my local ParaView client and connect to localhost:11111 to
>> connect to the remote pvserver through the ssh tunnel
>> 5. In the client, connect to Catalyst (port 22222)
>> 6. A provider for the simulation is created and the live visualization
>> works
>>
>> Now I want to do the same for simulations started on the remote cluster
>> via the batch job system. In this scenario, the parallel processes of
>> the simulation will run on different (randomly chosen) nodes on the
>> cluster. How do I go about getting a connection from my local client to
>> the Catalyst instances running on those nodes?
>>
>> I imagine I will need to set up ssh tunnels from the nodes to the login
>> node where the pvserver is running. I've tried adding a ssh tunnel line
>> to the job script that is executed when the batch job starts. I've tried
>> forwarding and reverse-forwarding port 22222 (ssh -L and ssh -R) to no
>> avail. The best I get is "ERROR: In
>> /.../ParaView_git/VTK/Common/System/vtkSocket.cxx, line 206
>> vtkServerSocket (0x18e0930): Socket error in call to bind. Address
>> already in use."
>>
>> My knowledge in networking and ssh is limited, so any pointers to how I
>> would go about this are greatly appreciated.
>>
>> Regards,
>>
>> Timo
>> _______________________________________________
>> Powered by 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
>>
>> Search the list archives at: http://markmail.org/search/?q=ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview
>>
>