# pvserver nvidia docker - connection issue
**URL:** https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007
**Category:** ParaView Support
**Created:** [January 21, 2025, 5:32am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007 "2025-01-21T05:32:07Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 21, 2025, 5:32am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/1 "2025-01-21T05:32:07Z")
I am trying to troubleshoot the following error and appreciate suggestion on where to start
I have ensure the OS on both client/server end are the same (Ubuntu 22.04)
I have ensure that both paraview and pvserver are from the same version 5.11.0
Thank you in advanced.
```auto
Status: Downloaded newer image for nvcr.io/nvidia-hpcvis/paraview:egl-py3-5.11.0
level=info msg="Setting CUDA_MODULE_LOADING=LAZY. Please see https://docs.nvidia.com for more information."
( 0.031s) [pvserver]SurfaceLICPluginAutoloa:25 WARN| SurfaceLIC is now built-in ParaView. There is no need to load this plugin.
-----------------------------------------------------
By loading the 'pvNVIDIAIndeX' plugin you have accepted the EULA shipped with it.
If that is not acceptable, please restart the application without loading
the 'pvNVIDIAIndeX' plugin.
-----------------------------------------------------
Waiting for client...
Connection URL: cs://1857fc7c1e13:11111
Accepting connection(s): 1857fc7c1e13:11111
Client connected.
Exiting...
( 558.143s) [pvserver]vtkSocketCommunicator.c:783 ERR| vtkSocketCommunicator (0x5636a966f050): Could not receive tag. 1
( 558.143s) [pvserver]vtkTCPNetworkAccessMana:295 ERR| vtkTCPNetworkAccessManager (0x5636a9483650): Some error in socket processing.
```
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 21, 2025, 5:56am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/2 "2025-01-21T05:56:58Z")
> [@Nicholas\_Yue](#):
>
> `Downloaded newer image for nvcr.io/nvidia-hpcvis/paraview:egl-py3-5.11.0`
Where is this ParaView coming from ? Is that a docker image ? Do you use the same image client side ?
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 21, 2025, 6:03am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/3 "2025-01-21T06:03:46Z")
ParaView came from [here](https://www.paraview.org/files/v5.11/ParaView-5.11.0-MPI-Linux-Python3.9-x86_64.tar.gz)
I use nvidia docker on the server side because the machine has a Nvidia GPU
I use a standard ParaView on the client side as it is just a normal Ubuntu 22.04 box
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 21, 2025, 6:07am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/4 "2025-01-21T06:07:41Z")
> [@Nicholas\_Yue](#):
>
> I use nvidia docker on the server side because the machine has a Nvidia GPU
Does this image ships a ParaView binary or do you use official ParaView binary there too ?
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 21, 2025, 6:10am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/5 "2025-01-21T06:10:02Z")
The docker I obtain from nvidia only has pvserver, for paraview, I use the official binaries
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 21, 2025, 6:16am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/6 "2025-01-21T06:16:12Z")
I have now repeated the test with both the pvserver (egl build) and the paraview using official binaries and same version to help isolate the problem.
The pvserver accepted the client connection (after a very long pause) but the pvserver is having issue with obtaining EGL
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 21, 2025, 10:15am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/7 "2025-01-21T10:15:12Z")
Please check this is working:
> [@Recover OpenGL Informations from pvpython](https://discourse.paraview.org/t/recover-opengl-informations-from-pvpython/1536/4):
>
> [https://gitlab.kitware.com/paraview/paraview/merge\_requests/3320](https://gitlab.kitware.com/paraview/paraview/merge_requests/3320)
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 22, 2025, 12:09am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/8 "2025-01-22T00:09:11Z")
It is not working
```auto
ubuntu@vm-c-bethelsight-trial-gpu:~/systems/ParaView/ParaView-5.13.1-egl-MPI-Linux-Python3.10-x86_64/bin$ ./pvpython
Python 3.10.13 (main, Sep 27 2024, 19:28:01) [GCC 10.2.1 20210130 (Red Hat 10.2.1-11)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from paraview.simple import *
GetOpenGLInformation()
>>> libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
( 24.606s) [paraview] vtkEGLRenderWindow.cxx:340 WARN| vtkEGLRenderWindow (0x4937700): EGL device index: 0 could not be initialized. Trying other devices...
>>> >>>
```
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 22, 2025, 3:23pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/9 "2025-01-22T15:23:46Z")
Please check `eglinfo` is working as expected.
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 22, 2025, 4:00pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/10 "2025-01-22T16:00:19Z")
Although nvida-smi returns RTX A5000, eglinfo seems to be unaware of a GPU present
In particular, eglinfo cannot find a GPU device
```auto
Device platform:
eglinfo: eglInitialize failed
```
I have attached both output files:
[nvidia-smi.log](https://discourse.paraview.org/uploads/short-url/hbb8Cbmnj8fYBxFjLBHZa9PFkIN.log) (1.7 KB)
[eglinfo.log](https://discourse.paraview.org/uploads/short-url/leb457PyM0szpMDToRTJuSQtXZ7.log) (6.5 KB)
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [January 23, 2025, 12:00am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/11 "2025-01-23T00:00:11Z")
I think it is an issue with the nvidia driver on the host.
Can you try to install a 535.x version instead?
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 23, 2025, 12:36am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/12 "2025-01-23T00:36:33Z")
I have downgraded the driver to 535, still having EGL errors
```auto
0x43 48 0 16 16 16 0 16 0 4 1 0x48344258-- y y y win
0x44 48 0 16 16 16 0 24 0 4 1 0x48344258-- y y y win
0x45 48 0 16 16 16 0 24 8 4 1 0x48344258-- y y y win
0x46 48 0 16 16 16 0 32 0 4 1 0x48344258-- y y y win
Wayland platform:
eglinfo: eglInitialize failed
X11 platform:
eglinfo: eglInitialize failed
Device platform:
eglinfo: eglInitialize failed
```
```auto
Thu Jan 23 00:35:48 2025
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.216.03 Driver Version: 535.216.03 CUDA Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| 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 RTX A5000 Off | 00000000:00:10.0 Off | Off |
| 30% 35C P0 75W / 230W | 0MiB / 24564MiB | 0% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=======================================================================================|
| No running processes found |
+---------------------------------------------------------------------------------------+
```
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 23, 2025, 8:40am UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/13 "2025-01-23T08:40:18Z")
> [@Nicholas\_Yue](#):
>
> eglinfo cannot find a GPU device
Then I’m afraid this is not a ParaView issue
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [January 23, 2025, 3:52pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/14 "2025-01-23T15:52:07Z")
This is strange indeed, do you set the ENV variable to `NVIDIA_DRIVER_CAPABILITIES=all`?
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 23, 2025, 4:06pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/15 "2025-01-23T16:06:03Z")
Setting the environment makes no difference.
@jourdain is there some OS version, kernel version combination that is important for pvserver to operate successfully ?
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [January 23, 2025, 10:31pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/16 "2025-01-23T22:31:14Z")
Not really, you just need to make sure the system can get an EGL device. And that is provided by your nvidia driver and OS.
We have some notes [here](https://kitware.github.io/trame/guide/deployment/docker.html#egl-caution) on similar issue. But that is about it. I know that NVidia is looking into the driver issue but I don’t have a timeline as they need to figure out the origin of the problem which could be linux distribution related.
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 23, 2025, 10:53pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/17 "2025-01-23T22:53:32Z")
Thank you @jourdain , the note is very useful. I will give the docker route a try and report back.
Thank you both @jourdain and @mwestphal for the patience.
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 23, 2025, 11:02pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/18 "2025-01-23T23:02:12Z")
Still getting the eglinfo error.
I will work with the Cloud GPU provider to see if they have other possibilities I could explore.
```auto
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
EGL client extensions string:
EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query
EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses
EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_device
EGL_EXT_platform_wayland EGL_KHR_platform_wayland
EGL_EXT_platform_x11 EGL_KHR_platform_x11 EGL_EXT_platform_xcb
EGL_MESA_platform_gbm EGL_KHR_platform_gbm
EGL_MESA_platform_surfaceless
GBM platform:
eglinfo: eglInitialize failed
Wayland platform:
error: XDG_RUNTIME_DIR not set in the environment.
error: XDG_RUNTIME_DIR not set in the environment.
eglinfo: eglInitialize failed
X11 platform:
eglinfo: eglInitialize failed
Device platform:
eglinfo: eglInitialize failed
```
---
### Author:  [@Nicholas\_Yue](https://discourse.paraview.org/u/Nicholas_Yue)
#### Post date: [January 24, 2025, 8:47pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/19 "2025-01-24T20:47:20Z")
This has been resolved. There is an additional nvidia gl package `libnvidia-gl-535-server` that needs to be installed for the EGL part to work.
Thank you once again to @mwestphal and @jourdain for your help and patience.
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [January 26, 2025, 5:57pm UTC](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007/20 "2025-01-26T17:57:16Z")
Out of curiosity, do you manage to get things working with newer nvidia drivers?
[Next page](https://discourse.paraview.org/t/pvserver-nvidia-docker-connection-issue/16007.md?page=2)