Using the Windows powershell, I am able to connect to the remote server with the command ssh my_user_name@remote_machine_hostname
However, when I try to connect to the server from within paraview, I get the following error:
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\Common\System\vtkSocket.cxx, line 447
vtkClientSocket (000002D02FE78820): Socket error in call to connect. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\Common\System\vtkClientSocket.cxx, line 51
vtkClientSocket (000002D02FE78820): Failed to connect to server remote_machine_hostname:11111
Warning: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\Remoting\Core\vtkTCPNetworkAccessManager.cxx, line 396
vtkTCPNetworkAccessManager (000002D0299C58B0): Connect failed. Retrying for 38.95 more seconds.
Could you help me understand what I am doing wrong?
No, I am not able to connect to the server by running it manually on the remote machine.
Here follows a description of the attempt I have made:
I logged in to the remote machine, and started the pvserver. The remote machine is a supercomputing cluster, and the pvserver there was configured by the administrators of the machine
The output after starting the pvserver was the following:
Waiting for client...
Connection URL: cs://<host_name>:11111
Accepting connection(s): <host_name>:11111
(I have replaced the real host name with <host_name>)
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\Common\System\vtkSocket.cxx, line 447
vtkClientSocket (000001D46F11EA10): Socket error in call to connect. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\Common\System\vtkClientSocket.cxx, line 51
vtkClientSocket (000001D46F11EA10): Failed to connect to server <host_name>:11111
Warning: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\Remoting\Core\vtkTCPNetworkAccessManager.cxx, line 396
vtkTCPNetworkAccessManager (000001CF32AFB610): Connect failed. Retrying for 38.952 more seconds.
Does this information make sense to you, or do you need more information to help me?
I usually access the cluster with putty, but I can also access it through the command prompt in Windows 11. When using the command prompt, I access the cluster with the following command:
ssh <user_name>@<host_name>
(I have substituted the real user and host name with <user_name> and <host_name> respectively)
In the “Edit Server Configuration” window in Paraview, I have used “Client / Server” as Server Type and 11111 as port.
I hope this was the answer to your question, if I have misunderstood, please clarify.
I then click on File > connect, and I chose the server corresponding to the above-mentioned configuration. After clicking “connect”, a terminal window appears asking me the password for the remote machine. I write the password, and I get the message “access granted. Press return to begin session”. I press return, and the paraView window goes into “Not Responding” mode. After that, “nothing” happens.
Do you have any suggestions of what I can do to find out what I am doing wrong?
First an update: I managed to connect to the server using CommandStartup. I am not really sure what I did differently from previous attempts.
Concerning doing the connection manually, I am confused. My understanding is that the tags Terminal, PortForwarding, and Arguments are “sub-tags” of the SSHCommand tag. However, the SSHCommand tag does not make sense if the server is to be started manually. Therefore, I don’t know how to modify the server configuration to make it work for a manual startup of the server.
Do you have an example of how a manual connection using ssh tunneling is done?
Although I managed to connect with a command startup, I think it could be useful to also understand how a manual connection is done.