utkarsh.ayac...@kitware.commailto:utkarsh.ayac...@kitware.com
Cc: paraview@paraview.orgmailto:paraview@paraview.org
paraview@paraview.orgmailto:paraview@paraview.org
Subject: RE: [Paraview] [EXTERNAL] Client/Server connection problems
You compiled it in?
'-DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL
: Nathan Fabian ndfa...@sandia.govmailto:ndfa...@sandia.gov,
paraview@paraview.orgmailto:paraview@paraview.org
paraview@paraview.orgmailto:paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems
Nathan,
First, let me clarify what is checked, since what Alan said
You compiled it in?
'-DPARAVIEW_ALWAYS_SECURE_CONNECTION:BOOL=ON '
From: Fabian, Nathan
Sent: Tuesday, January 14, 2014 5:41 PM
To: Fabian, Nathan; Utkarsh Ayachit; Scott, W Alan
Cc: paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems
Okay, I figured
...@sandia.govmailto:ndfa...@sandia.gov,
paraview@paraview.orgmailto:paraview@paraview.org
paraview@paraview.orgmailto:paraview@paraview.org
Subject: Re: [Paraview] [EXTERNAL] Client/Server connection problems
Nathan,
First, let me clarify what is checked, since what Alan said isn't entirely
correct.
What
Nathan,
First, let me clarify what is checked, since what Alan said isn't
entirely correct.
What comprises the handshake?
The handshake is a string of the following form:
paraview.MajorNumber.MinorNumber
If a connect-id is specified then the handshake becomes:
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,
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 wasc...@sandia.gov wrote:
Delete your configuration files. Corrupt configuration files
Then no, that isn't the issue.
One more thing to try - and I don't completely know how to do it. (i.e., ask
Kitware). I believe that they now look at not just ParaView version numbers,
but also git checkin tags or whatever it is called. If the two trees are
basically the same, and ANYONE