CFD Online Discussion Forums

CFD Online Discussion Forums (https://www.cfd-online.com/Forums/)
-   ParaView (https://www.cfd-online.com/Forums/paraview/)
-   -   [OpenFOAM] pvserver and client connect, error: Connection refused (https://www.cfd-online.com/Forums/paraview/216760-pvserver-client-connect-error-connection-refused.html)

jmenendez April 18, 2019 14:34

pvserver and client connect, error: Connection refused
 
Hi all,

I am trying to configure client-server for Paraview and I get the following error (client):

The steps I follow for the configuration are:

1. I connect with SSH to the server, there I run pvserver:

Code:

~/OpenFOAM/ubuntu-5.0/run/pvserver
Waiting for client...
Connection URL: cs://ip-XXX-XXX-XXX-XXX:11111
Accepting connection(s): ip-XXX-XXX-XXX-XXX:11111

2. After that on my computer (client) I run Paraview with cs://localhost:11111 but it does not connect, with error (client)

Code:

ERROR: In /home/alpha/OpenFOAM/ThirdParty-v1812/ParaView-v5.6.0/VTK/Common/System/vtkSocket.cxx, line 476
 vtkClientSocket (0x55b9c5188e60): Socket error in call to connect. Connection refused.

I do not know what I'm doing wrong and why it does not connect. It is the first time I configure paraview for remote viewing

Thank you

wyldckat April 21, 2019 16:19

Quick answer:
  1. As far as I know, you must use the exact same version of ParaView on each side.
  2. It is possible that that the server is using a firewall.
  3. This will only work if the two machines are in the same network.

jmenendez April 22, 2019 09:42

Quote:

Originally Posted by wyldckat (Post 731411)
Quick answer:
  1. As far as I know, you must use the exact same version of ParaView on each side.
  2. It is possible that that the server is using a firewall.
  3. This will only work if the two machines are in the same network.


Thank you very much for your time and help.

I used the same version of Paraview; even I downloaded the latest version with wget inside the server and I ran exactly the same program for the local computer. In addition to this the error that Paraview would give when it was for another version does not match the current one.

The server is an instance of AWS and is configured to let traffic through the corresponding ports, so I have no idea what I'm doing wrong.

I've thought that maybe the precompiled versions of Paraview do not have enough enabled by default.

Could someone using AWS instances please indicate their basic client / server configuration (without specific data, of course) in order to compare them?

Thank you all.

wyldckat April 22, 2019 21:17

Quick answer: If AWS is involved, I suggest that you ask about this here: https://discourse.paraview.org/c/paraview-support - it's the somewhat official support forum for ParaView and there should be more people there that use ParaView with other software.

And please indicate the exact version+build you downloaded, because this could be a bug with that specific version+build...


All times are GMT -4. The time now is 21:58.