search

Kitware / web-project-templates

This repository try to gather various web project templates based on vue, vtk.js, paraviewweb...
26 stars 10 forks source link

Error when starting paraview server on windows server #54

Closed RQsky closed 2 years ago

RQsky commented 2 years ago

image

The mainstream argument is the problem of environment variables or the problem of the graphics card driver. My environment variables are as shown below, which is the same as the configuration of another Windows server (TITAN graphics card), but the other one does not report an error. image

The server that reported the error uses NVIDIA A40 graphics card and drives v31. I went back to v30.0.14.7111 and it didn't solve the problem.

So I want to ask you how to deal with this problem, I'm at a loss.

jourdain commented 2 years ago

If I'm not mistaken the A40 is headless and does not implement OpenGL rendering. If that is the case, it might support EGL and if it does you will to have to download the EGL build of ParaView for linux.

RQsky commented 2 years ago

But the server is installed with Windows operating system, paraview for Linux should not be available. Can I add any parameters when starting the model so that the server uses the CPU to render the model. What should I do?

jourdain commented 2 years ago

None of our Windows binaries for ParaView are headless as it is a very uncommon. You have 2 options. 1) You can build ParaView yourself with OSMesa (CPU) or EGL (GPU). 2) Use docker to run ParaView within a linux. That option might even allow you to still use your GPU.

RQsky commented 2 years ago

Hello, I use docker to create a container based on the ubuntu image, and then install ParaView with OSMesa. I start pvw-server.py and everything works fine. However, when the front-end requests to establish a connection, the server reports an error exception occurred: subprocess killed. I'm going crazy and have no idea what do you think about this. In fact, everything was normal, but I manually killed a process that was occupying port 1234, and then docker was killed by me, and I have been having this problem since then. Using a new container doesn't help either.

jourdain commented 2 years ago

Without further details it is hard to help. But if you want a personalized support to go to the bottom of your issue, we can help.

RQsky commented 2 years ago

Thank you very much for your continued help. The problem is solved. The reason is that windows docker desktop has resource restrictions on containers. So rendering a 187MB ply file will cause the subprocess to crash and exit, and rendering fails. When I unblock docker restrictions, everything is OK.

jourdain commented 2 years ago

Great, thanks for reporting back and providing the reason of the issue you were running into, that can definitely help other running into the same limitation.