I am running pvserver on remote linux machine (paraview v5.8.0)
but when I try to connect on the windows PC with same version of paraview
Connection failed during handshake
I can get 3.98.1 and 4.1.0 to connect,
but then they crash out when I try to load the temp.foam file.
Waiting for client...
Connection URL: cs://giles-calc-machine:11111
Accepting connection(s): giles-calc-machine:11111
Client connected.
ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 530
vtkXOpenGLRenderWindow (0x17593f0): bad X server connection. DISPLAY=ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0x17593f0): bad X server connection. DISPLAY=Segmentation fault (core dumped)
I’m using exactly the same procedure that I use on my laptop (which works fine in pv3 and pv4), but for some reason it doesnt work from my workstation.
Normally I can only connect using pv3 or pv4, but in this case it does connect,
and the pv window comes up, but as soon as I try to load the .foam file it crashes out.
Ideally I would like to be using pv5.8.0, but the handshake doesnt work for that one.
(on any of my machines).
I will try your suggestion about the DISPLAY seeting - what do you use
I just tried setting display and I still get the same coredump, when loading a file.
No protocol specified
ERROR: In /home/utkarsh/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Rendering/OpenGL/vtkXOpenGLRenderWindow.cxx, line 322
vtkXOpenGLRenderWindow (0x14543f0): bad X server connection. DISPLAY=:0
ok. I connect windows laptop to Linux (ubuntu) workstation.
then start pvserver in ubuntu. then start paraview on windows laptop.
then I can connect (in paraview), and open files, and it works fine. all good.
But the doing same from my windows workstation doesnt work,
although I can connect (in paraview), and see the files in Linux workstation,
but as soon as try to open one of them, paraview crashes out with that error message, and coredump.
that doesnt make much difference. BUT I have just discovered that its only the larger cases that it crashes out on, so maybe its more of a graphics RAM issue. I dont know how much RAM is required for rendering larger meshes, although this case Im using now is only 200k cells and that is crashing out.
Matt,
I think your were right in the first place - it seems to be a lack of xserver thats the problem.
so we need to install the osmesa version in 5.11.0 then?