[Paraview] [EXTERNAL] Client/Server connection problems

Fabian, Nathan ndfabia at sandia.gov
Fri Jan 10 18:57:17 EST 2014


That sounded promising, but it doesn't appear to have worked.  I deleted
everything under .config/ParaView and .config/Kitware on both machines,
still getting the same error.

On 1/10/14 4:45 PM, "Scott, W Alan" <wascott at sandia.gov> wrote:

>Delete your configuration files.  Corrupt configuration files sometimes
>cause this.  Surprisingly, on one client of mine, the first connect
>works, the configuration file gets written, and you never get another
>successful connect using that configuration file.
>
>I haven't chased this down yes, hoping it goes away with the new version.
> But...
>
>If this is the problem, please let me know.  You may have an easier setup
>that we can use to get to the root cause of the problem.
>
>Alan
>
>-----Original Message-----
>From: paraview-bounces at paraview.org
>[mailto:paraview-bounces at paraview.org] On Behalf Of Fabian, Nathan
>Sent: Friday, January 10, 2014 3:59 PM
>To: paraview at paraview.org
>Subject: [EXTERNAL] [Paraview] Client/Server connection problems
>
>Hi,
>
>I've been trying to figure this one out for a few days and I'm finally
>giving in for help.
>
>I've got a code base on my server that should be a duplicate of the one
>on my desktop, built differently.  In one case I did pulls from master at
>the same time.  I've more recently just tried pulling directly from my
>desktop and building clean on both.  I've also tried disabling MPI on the
>desktop side and connecting without MPI on the server side.
>
>Still I'm getting the following message when trying to reverse connect:
>
>
>ERROR: In
>/projects/coprocessing/ParaView/ParaViewCore/ClientServerCore/Core/vtkTCPN
>e
>tworkAccessManager.cxx, line 330
>vtkTCPNetworkAccessManager (0x135a3150): Failed to connect to
>xyz.sandia.gov:11111. Client-Server Handshake failed. Please verify that
>the client and server versions are compatible with each other, and that
>'connect-id', if any, matches.
>
>
>And then each attempt to connect gives this on the desktop:
>
>
>
>Accepting connection(s): xyz.sandia.gov:11111
>
>
>Evidence that some sort of communication has worked.  This has worked with
>master builds in the past.  I'm not sure what I changed, but there's
>plenty I have that may have influenced this.
>
>Any suggestions on where to start looking?
>
>Thanks,
>Nathan.
>
>_______________________________________________
>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
>
>Follow this link to subscribe/unsubscribe:
>http://www.paraview.org/mailman/listinfo/paraview



More information about the ParaView mailing list