The client and server processes both print out a message with the
handshake strings they compared with. Mind posting both of them?
Thanks
On Sun, Apr 26, 2015 at 8:54 AM, u.utku.turunco...@be.itu.edu.tr wrote:
Hi,
I am trying to connect Paraview server (pvserver) to test the Paraview
Hi,
I am trying to connect Paraview server (pvserver) to test the Paraview
Catalyst example codes from GitHub account. So, i installed Paraview from
source (under Centos 7.0) without any problem and then test code. The
problem is that i am getting following error messages when i try to run
the
Hi Utkarsh,
It is the same installed version that I use both for the client and the server.
As you correctly pointed out, MPI is enabled.
However, I somewhat narrowed down the scope of the problem. Apparently, if I
use X forwarding via ssh, everything works correctly. Only if I run the
Which vnc server are you using? Seems to me your VNC server is missing
some X extensions (or something like that). We do use VNC servers here
for running tests, so it's known to work.
On Mon, Apr 13, 2015 at 5:09 AM, Schlottke, Michael
m.schlot...@aia.rwth-aachen.de wrote:
Hi Utkarsh,
It is
Thanks for the hint, this seems to resolve my issue: I use
tightvnc-1.3.9-110.1.x86_64 on the machine where it does not work, but on a
different machine (with tightvnc-1.3.10-14.2.1.x86_64 installed) it works.
Might not be just the vnc server version but maybe a related package, but it
was
Are the client and server created using the similar build flags? One
guess would be that you don't have MPI enabled on the server, but you
do have it enabled on the client build. Is that correct?
Utkarsh
On Sat, Apr 11, 2015 at 12:45 PM, Schlottke, Michael
m.schlot...@aia.rwth-aachen.de wrote:
Hi,
I just installed PV 4.3.1 from source as I need to compile some custom plugins.
Using the GUI client in a standalone fashion is no problem and everything works
as expected. However, I’ve had difficulties when trying to connect to a
pvserver instance.
The server dies with the following
