Paraview 5.10.1 crashes on connecting to pvserver (Windows to linux)

Good morning,

A couple of months ago I upgraded from Paraview 5.9.X to 5.10.1 (all precomplied binaries) on both my Windows laptop and my linux PC. On the PC I downloaded the MPI and egl binaries to be able to visualise both interactively and in batch. I used to be able to connect to the pvserver by:

  1. starting the pvserver on localhoston the linux PC
  2. opening a putty session to my PC with port forwarding
  3. opening my Paraview client on the laptop
  4. connecting to cs://localhost:11111
    However, for some reason this does not work anymore.
    I always get these errors:
luuk@holykauw ~ $ ./ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/pvserver-real --force-offscreen-rendering
Waiting for client...
Connection URL: cs://holykauw:11111
Accepting connection(s): holykauw:11111
Client connected.
( 111.615s) [pvserver        ]vtkXOpenGLRenderWindow.:266    ERR| vtkXOpenGLRenderWindow (0x17c6fe0): Could not find a decent config
( 111.615s) [pvserver        ]vtkXOpenGLRenderWindow.:484    ERR| vtkXOpenGLRenderWindow (0x17c6fe0): Could not find a decent visual
Loguru caught a signal: SIGABRT
Stack trace:
17            0x401877 ./ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x401877]
16      0x7fd572ea5083 __libc_start_main + 243
15            0x40177b ./ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40177b]
14      0x7fd570a3ed32 vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) + 690
13      0x7fd56f92f975 vtkMultiProcessController::ProcessRMIs(int, int) + 597
12      0x7fd56f92f213 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 291
11      0x7fd57121474f vtkPVSessionServer::OnClientServerMessageRMI(void*, int) + 1167
10      0x7fd5712140da vtkPVSessionServer::GatherInformationInternal(unsigned int, char const*, unsigned int, vtkMultiProcessStream&) + 298
9       0x7fd57120e703 vtkPVSessionCore::GatherInformation(unsigned int, vtkPVInformation*, unsigned int) + 451
8       0x7fd57120e3a4 vtkPVSessionCore::GatherInformationInternal(vtkPVInformation*, unsigned int) + 36
7       0x7fd56867c529 vtkPVRenderingCapabilitiesInformation::CopyFromObject(vtkObject*) + 9
6       0x7fd56867c4f1 vtkPVRenderingCapabilitiesInformation::GetLocalCapabilities() + 305
5       0x7fd557aa1315 vtkOpenGLRenderWindow::SupportsOpenGL() + 1029
4       0x7fd557b3f6f2 vtkXOpenGLRenderWindow::WindowInitialize() + 18
3       0x7fd557b43345 vtkXOpenGLRenderWindow::CreateAWindow() + 1893
2       0x7fd572ea3859 abort + 299
1       0x7fd572ec400b gsignal + 203
0       0x7fd572ec4090 /lib/x86_64-linux-gnu/libc.so.6(+0x43090) [0x7fd572ec4090]
( 111.615s) [pvserver        ]                       :0     FATL| Signal: SIGABRT
Aborted (core dumped)

I’ve tried loading server configuration files following the documentation and tips on the forums and Paraview repo. I’ve also tried reinstalling everywhere, still the problem persists. Paraview is part of my daily working routine and I really hope there is a fix to my problem.
Does anyone have any idea?

Thanks in advance!

Hi @Luukv8x ,

Looks like you are using the X11/OpenGL version on your linux PC, is that what you intend to ?
Does your linux PC has a Xorg server running and a GPU ?

opening a putty session to my PC with port forwarding

Unless you have complex network setup, this is not needed at all, just connect from the client to the setup.

Best,

Dear Mathieu,

Thanks for your fast reply!

BlockQuote
Looks like you are using the X11/OpenGL version on your linux PC, is that what you intend to ?
Does your linux PC has a Xorg server running and a GPU ?

I am using an Xorg server yes, I use Xorg to work from home. My PC has a GPU:

luuk@holykauw ~ $ nvidia-smi
Mon Jun 20 12:42:03 2022       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.129.06   Driver Version: 470.129.06   CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0  On |                  N/A |
| 30%   36C    P8    13W / 320W |   1166MiB /  9984MiB |      3%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      1612      G   /usr/lib/xorg/Xorg                102MiB |
|    0   N/A  N/A      3053      G   /usr/lib/xorg/Xorg                509MiB |
|    0   N/A  N/A      3196      G   /usr/bin/gnome-shell               77MiB |
|    0   N/A  N/A     18873      G   ...veSuggestionsOnlyOnDemand      122MiB |
|    0   N/A  N/A     90282      G   ...b/thunderbird/thunderbird      162MiB |
|    0   N/A  N/A     90672      G   /usr/lib/firefox/firefox          173MiB |
+-----------------------------------------------------------------------------+

Blockquote
Unless you have complex network setup, this is not needed at all, just connect from the client to the setup.

I set up the port forwarding about a year ago to bypass the firewall. If I do not do that I get the “connection actively refused” error. Before that I was able to connect to the pvserver when I had the VPN on. This suddenly changed at some point, I don’t know why.

Kind regards,
Luuk

Ok, in that case port forwarding can make sense.

I am using an Xorg server yes, I use Xorg to work from home.

Make sure DISPLAY is set
Usually someting like:

DISPLAY=:0 pvserver

You can easily check with

glxinfo
DISPLAY=:0 glxinfo

Okay, I had to install mesa-utils to do that command. glxinfo prints out a lot of info. when I grep for “display” (there is no capitalised DISPLAY) it says

luuk@holykauw ~ $ glxinfo | grep display
name of display: :1
display: :1  screen: 0

Does this mean pvserver is looking for display 0 while I have only the 1? (my PC has only 1 screen)

Yes, try with DISPLAY=:1 pvserver

Sidenote: I just retried connecting after installing mesa-utils (which I think I remember uninstalling because it caused many crashes (also outside paraview with other software). Now it managed to connect with my old port-forwarding setup!

I will try your DISPLAY=:1 pvserver suggestion of course. I try to get back to you asap.

Thanks for your help in any case!

Okay, so it works without adjusting the DISPLAY variable but only if I start the server directly on the PC (i.e. not in the Xorg session), not when I start it from the Xorg :frowning:

EDIT:
when I do export DISPLAY=:1 and then start the pvserver I can also connect when starting the server from Xorg!
Problem solved, thanks @mwestphal !

1 Like