[Paraview] [EXTERNAL] pvserver MPI issue

Quentin d'Avout quentin at arrivo-loop.com
Fri Oct 13 18:39:33 EDT 2017


Thanks Scott.

Didn’t do the trick tho.

Other ideas?



*From:* Scott, W Alan [mailto:wascott at sandia.gov]
*Sent:* Friday, October 13, 2017 2:15 PM
*To:* Quentin d'Avout <quentin at arrivo-loop.com>; paraview at paraview.org
*Subject:* Re: [EXTERNAL] [Paraview] pvserver MPI issue



Not saying I’m right here, but it looks like multiple versions of ParaView
are tying up the socket.  Do a ps -ef on paraview, client side, and kill
them.  Do the same on the server side.  Then, try again.



Alan



*From: *ParaView <paraview-bounces at paraview.org> on behalf of Quentin
d'Avout <quentin at arrivo-loop.com>
*Date: *Friday, October 13, 2017 at 3:10 PM
*To: *"paraview at paraview.org" <paraview at paraview.org>
*Subject: *[EXTERNAL] [Paraview] pvserver MPI issue



Hi All,



my issue is when I hit:



mpirun -np 32 pvserver # with or without --mpi option



I get :"vtkServerSocket (0x23fb3e0): Socket error in call to bind. Address
already in use."

and: "vtkTCPNetworkAccessManager (0x1879510): Failed to set up server
socket."



as if my paraView was compiled with the mpi capability off. But it is on
(D3 filter available, "about" windows also says so).



pvserver in serial works just fine.

Could have been the ufw firewall blocking connections, but it is disabled.

Ubuntu 17.04.



Thanks in advance for your help.

Quentin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171013/b7bf946b/attachment.html>


More information about the ParaView mailing list