Andy_Bauer
January 27, 2021, 4:52pm
1
Hi,
I’m testing out the 5.9 installers on an HPC system (without graphics cards and therefore without X11) and I’m submitting a job to run pvbatch and am getting behavior that’s confusing me. I’ve been trying different combinations of the --mesa, --backend and --force-offscreen-rendering flags and I keep getting these output errors:
( 1.587s) [pvbatch.0 ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 1.587s) [pvbatch.0 ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 1.587s) [pvbatch.0 ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 1.587s) [pvbatch.0 ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 1.602s) [pvbatch.0 ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
If I don’t render anything the Python script runs fine but if I use the following arguments –mesa --backend swr --force-offscreen-rendering and run with a script that tries to generate a screenshot I get the following output:
( 2.275s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.275s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.375s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.375s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.375s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.376s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.397s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.397s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.397s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.397s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.397s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.397s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.404s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.404s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.404s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.404s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.404s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.404s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.418s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.418s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.418s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.418s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.418s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.418s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.423s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.423s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.423s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.423s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.423s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 2.424s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.896s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.896s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.896s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.896s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.896s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.896s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.900s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.900s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 5.120s) [pvbatch ]vtkXOpenGLRenderWindow.:455 ERR| vtkXOpenGLRenderWindow (0x1719ccf0): bad X server connection. DISPLAY=
Loguru caught a signal: SIGABRT
Stack trace:
50 0x40206e /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/pvbatch-real() [0x40206e]
49 0x7fb142556505 __libc_start_main + 245
48 0x4028f3 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/pvbatch-real() [0x4028f3]
47 0x7fb13fee5b34 vtkPythonInterpreter::PyMain(int, char**) + 532
46 0x7fb13dd09173 Py_Main + 67
45 0x7fb13dd08d20 Py_RunMain + 1920
44 0x7fb13dce510f PyRun_SimpleFileExFlags + 223
43 0x7fb13dce4f52 PyRun_FileExFlags + 290
42 0x7fb13dca0b2b PyEval_EvalCode + 27
41 0x7fb13dca0afe PyEval_EvalCodeEx + 62
40 0x7fb13dca0a47 _PyEval_EvalCodeWithName + 2919
39 0x7fb13db75bc6 _PyEval_EvalFrameDefault + 23798
38 0x7fb13dba10e2 _PyFunction_Vectorcall + 146
37 0x7fb13dca0a47 _PyEval_EvalCodeWithName + 2919
36 0x7fb13db76d44 _PyEval_EvalFrameDefault + 28276
35 0x7fb13dba5455 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/libpython3.8.so.1.0(+0xa2455) [0x7fb13dba5455]
34 0x7fb13dba10e2 _PyFunction_Vectorcall + 146
33 0x7fb13dca0a47 _PyEval_EvalCodeWithName + 2919
32 0x7fb13db77902 _PyEval_EvalFrameDefault + 31282
31 0x7fb13dba3d43 PyCFunction_Call + 115
30 0x7fb0fcdff234 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/lib/python3.8/site-packages/paraview/modules/vtkRemotingViews.so(+0x18c234) [0x7fb0fcdff234]
29 0x7fb137ef5223 vtkSMSaveScreenshotProxy::WriteImage(char const*, unsigned int) + 1251
28 0x7fb137ef0b7a vtkSMSaveScreenshotProxy::CapturePreppedImages() + 282
27 0x7fb137eefa92 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/../lib/libvtkRemotingViews-pv5.9.so.1(+0x225a92) [0x7fb137eefa92]
26 0x7fb137f286dd vtkSMViewProxy::CaptureWindow(int, int) + 77
25 0x7fb137f27552 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/../lib/libvtkRemotingViews-pv5.9.so.1(+0x25d552) [0x7fb137f27552]
24 0x7fb137f27197 vtkSMViewProxy::CaptureWindowSingle(int, int) + 55
23 0x7fb137f26af2 vtkSMViewProxy::CaptureWindowInternal(int, int) + 754
22 0x7fb137ee658c vtkSMRenderViewProxy::RenderForImageCapture() + 76
21 0x7fb137f26573 vtkSMViewProxy::StillRender() + 307
20 0x7fb14094d2e5 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
19 0x7fb14094e2bb vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
18 0x7fb14094e482 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
17 0x7fb13fcb3ddd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
16 0x7fb13fcb3b3e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
15 0x7fb13fcb340d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
14 0x7fb13fcb2da9 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
13 0x7fb141314398 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 8312
12 0x7fb137e84b91 vtkPVRenderView::StillRender() + 97
11 0x7fb137e90b9a vtkPVRenderView::Render(bool, bool) + 2010
10 0x7fb137eaa055 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/../lib/libvtkRemotingViews-pv5.9.so.1(+0x1e0055) [0x7fb137eaa055]
9 0x7fb137e781fd vtkPVProcessWindow::PrepareForRendering() + 45
8 0x7fb128681620 vtkXOpenGLRenderWindow::Render() + 32
7 0x7fb1285e3231 vtkOpenGLRenderWindow::Render() + 81
6 0x7fb123e8af65 vtkRenderWindow::Render() + 741
5 0x7fb1286812d6 vtkXOpenGLRenderWindow::Start() + 86
4 0x7fb12867c0e2 vtkXOpenGLRenderWindow::WindowInitialize() + 18
3 0x7fb12867fd35 vtkXOpenGLRenderWindow::CreateAWindow() + 1893
2 0x7fb14256ba28 abort + 328
1 0x7fb14256a337 gsignal + 55
0 0x7fb14256a3b0 /lib64/libc.so.6(+0x363b0) [0x7fb14256a3b0]
( 5.120s) [pvbatch ] :0 FATL| Signal: SIGABRT
Any ideas what’s going on or recommended flags for pvbatch?
Andy_Bauer
January 28, 2021, 1:44pm
2
Reading the 5.9 release notes:
On linux, paraview_mesa launcher has now been removed. ParaView binaries now respect command-line arguments instead to indicate if Mesa3D libraries should be loaded for software rendering, instead of using OpenGL libraries available on your system. Pass --mesa with optional --backend [swr|llvm] to any of the ParaView executables to request Mesa3D-based rendering with appropriate backend.
It looks like the following should work (which I’m doing on the login node) but doesn’t:
acbauer@jim05> /app/DAAC/paraview/5.9.0_osmesa/bin/pvbatch --version
paraview version 5.9.0
acbauer@jim05> /app/DAAC/paraview/5.9.0_osmesa/bin/pvbatch --mesa --no-mpi /p/home/acbauer/PVTEST/makewav.py
( 3.888s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 3.888s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.298s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.298s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.298s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.298s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.317s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.317s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.317s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.317s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.317s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.317s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.323s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.323s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.323s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.323s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.323s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.323s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.336s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.336s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.336s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.336s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.336s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.336s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.341s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.341s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.341s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.341s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.341s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 4.341s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
in the script
( 7.494s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.494s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.494s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.494s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.494s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.494s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.499s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.499s) [pvbatch ] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
( 7.673s) [pvbatch ]vtkXOpenGLRenderWindow.:455 ERR| vtkXOpenGLRenderWindow (0x163e8bb0): bad X server connection. DISPLAY=
Loguru caught a signal: SIGABRT
Stack trace:
50 0x40206e /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/pvbatch-real() [0x40206e]
49 0x2b9a0077b555 __libc_start_main + 245
48 0x4028f3 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/pvbatch-real() [0x4028f3]
47 0x2b9a02f79b34 vtkPythonInterpreter::PyMain(int, char**) + 532
46 0x2b9a051b5173 Py_Main + 67
45 0x2b9a051b4d20 Py_RunMain + 1920
44 0x2b9a0519110f PyRun_SimpleFileExFlags + 223
43 0x2b9a05190f52 PyRun_FileExFlags + 290
42 0x2b9a0514cb2b PyEval_EvalCode + 27
41 0x2b9a0514cafe PyEval_EvalCodeEx + 62
40 0x2b9a0514ca47 _PyEval_EvalCodeWithName + 2919
39 0x2b9a05021bc6 _PyEval_EvalFrameDefault + 23798
38 0x2b9a0504d0e2 _PyFunction_Vectorcall + 146
37 0x2b9a0514ca47 _PyEval_EvalCodeWithName + 2919
36 0x2b9a05022d44 _PyEval_EvalFrameDefault + 28276
35 0x2b9a05051455 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/libpython3.8.so.1.0(+0xa2455) [0x2b9a05051455]
34 0x2b9a0504d0e2 _PyFunction_Vectorcall + 146
33 0x2b9a0514ca47 _PyEval_EvalCodeWithName + 2919
32 0x2b9a05023902 _PyEval_EvalFrameDefault + 31282
31 0x2b9a0504fd43 PyCFunction_Call + 115
30 0x2b9a45c4d234 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/lib/python3.8/site-packages/paraview/modules/vtkRemotingViews.so(+0x18c234) [0x2b9a45c4d234]
29 0x2b9a0b065223 vtkSMSaveScreenshotProxy::WriteImage(char const*, unsigned int) + 1251
28 0x2b9a0b060b7a vtkSMSaveScreenshotProxy::CapturePreppedImages() + 282
27 0x2b9a0b05fa92 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/../lib/libvtkRemotingViews-pv5.9.so.1(+0x225a92) [0x2b9a0b05fa92]
26 0x2b9a0b0986dd vtkSMViewProxy::CaptureWindow(int, int) + 77
25 0x2b9a0b097552 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/../lib/libvtkRemotingViews-pv5.9.so.1(+0x25d552) [0x2b9a0b097552]
24 0x2b9a0b097197 vtkSMViewProxy::CaptureWindowSingle(int, int) + 55
23 0x2b9a0b096af2 vtkSMViewProxy::CaptureWindowInternal(int, int) + 754
22 0x2b9a0b05658c vtkSMRenderViewProxy::RenderForImageCapture() + 76
21 0x2b9a0b096573 vtkSMViewProxy::StillRender() + 307
20 0x2b9a023fa2e5 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
19 0x2b9a023fb2bb vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
18 0x2b9a023fb482 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
17 0x2b9a0318eddd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
16 0x2b9a0318eb3e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
15 0x2b9a0318e40d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
14 0x2b9a0318dda9 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
13 0x2b9a00f1b398 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 8312
12 0x2b9a0aff4b91 vtkPVRenderView::StillRender() + 97
11 0x2b9a0b000b9a vtkPVRenderView::Render(bool, bool) + 2010
10 0x2b9a0b01a055 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/../lib/libvtkRemotingViews-pv5.9.so.1(+0x1e0055) [0x2b9a0b01a055]
9 0x2b9a0afe81fd vtkPVProcessWindow::PrepareForRendering() + 45
8 0x2b9a1a935620 vtkXOpenGLRenderWindow::Render() + 32
7 0x2b9a1a897231 vtkOpenGLRenderWindow::Render() + 81
6 0x2b9a1f058f65 vtkRenderWindow::Render() + 741
5 0x2b9a1a9352d6 vtkXOpenGLRenderWindow::Start() + 86
4 0x2b9a1a9300e2 vtkXOpenGLRenderWindow::WindowInitialize() + 18
3 0x2b9a1a933d35 vtkXOpenGLRenderWindow::CreateAWindow() + 1893
2 0x2b9a00790a78 abort + 328
1 0x2b9a0078f387 gsignal + 55
0 0x2b9a0078f400 /lib64/libc.so.6(+0x36400) [0x2b9a0078f400]
( 7.673s) [pvbatch ] :0 FATL| Signal: SIGABRT
error: exception occurred: Child aborted
Note that /app/DAAC/paraview/5.9.0_osmesa points to /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/
OSMesa binaries should indeed not be built with VisRTX enabled. Also, it’s annoying that VisRTX wants to print out these messages. It should be silent unless extra verbosity was requested.
cc: @cory.quammen @ben.boeckel
ben.boeckel
January 28, 2021, 3:01pm
4
Hmm. I don’t see where visrtx is enabled for anything other than linux_plain and windows (both variants). Other codepaths explicitly disable it, so something else is going on.
Edit to add: None of the OSMesa packages mention that visrtx is enabled in their configure output.
Andy_Bauer
January 28, 2021, 3:09pm
5
The output for uname -a is Linux jim01 3.10.0-1062.9.1.el7.x86_64 #1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux. The system is an SGI ICE X (formerly Topaz at ERDC but it’s been reconfigured now that it’s not under original support anymore).
Please let me know if you need any more system info or anything else in case that helps track down the issue.
mwestphal
January 29, 2021, 8:53am
6
I have the same warnings on the standard version of ParaView 5.9.0 and my 1080Ti on linux.
It should indeed be silenced.
wascott
January 29, 2021, 4:35pm
7
Same warnings here. Mine is a standard Red Hat system, using RGS to login in.
Reported here: https://gitlab.kitware.com/paraview/paraview/-/issues/20459 .
Note I am getting around it by piping into a reverse grep, which does hide it.
https://gitlab.kitware.com/paraview/paraview/-/issues/20462 is worse, I can’t hide this one from users.
vbolea
February 15, 2021, 3:47pm
8
@Andy_Bauer you can silence those messages by skipping the initialization of both OSPRAY and VISRTX setting these two env vars:
- VTK_DISABLE_OSPRAY
- VTK_DISABLE_VISRTX
wascott
February 15, 2021, 8:01pm
9
@vbolea @Andy_Bauer There are two bugs here. Lets take them one at a time.
Warning print for bug 20495 “VisRTXBackend.cxx error prints” CAN be stopped by using the Disable VisRTD flag you mention. But, you shouldn’t need to set environmental vars to stop warning prints. I believe this has not been fixed yet. When fixed, it will be ported to 5.9.1.
Error print for bug 20462 " vtkOSPRayMaterialLibrar error prints" has been found and fixed. It does not stop when setting the Disable Ospray/ Disable VisRTX environment variables. It is caused by a mismatch of the client having OSPray enabled in the build, and the server not having OSPRay enabled in the build. This also needs to be ported to 5.9.1.
Andy_Bauer
February 16, 2021, 1:05pm
10
@vbolea setting those flags works to get rid of the warnings but I still can’t use the offscreen options with the installers from the download page without getting a segfault. At least not on our HPC machines that don’t have graphics cards and X11 installed. I only tried the --mesa flag with pvpython though.
acbauer@jim01> ./pvpython --mesa
Python 3.8.6 (default, Jan 23 2021, 18:21:19)
[GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from paraview.simple import *
>>> w = Wavelet()
>>> Show()
<paraview.servermanager.UniformGridRepresentation object at 0x2aea1b745850>
>>> Render()
Loguru caught a signal: SIGSEGV
Stack trace:
37 0x40206b /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/pvpython-real() [0x40206b]
36 0x2ae9d0e97555 __libc_start_main + 245
35 0x4028f3 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/pvpython-real() [0x4028f3]
34 0x2ae9d3695b34 vtkPythonInterpreter::PyMain(int, char**) + 532
33 0x2ae9d58d1173 Py_Main + 67
32 0x2ae9d58d0eac Py_RunMain + 2316
31 0x2ae9d58adb6e PyRun_AnyFileExFlags + 62
30 0x2ae9d58ad823 PyRun_InteractiveLoopFlags + 531
29 0x2ae9d58ab3c6 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/libpython3.8.so.1.0(+0x1e03c6) [0x2ae9d58ab3c6]
28 0x2ae9d5868b2b PyEval_EvalCode + 27
27 0x2ae9d5868afe PyEval_EvalCodeEx + 62
26 0x2ae9d5868a47 _PyEval_EvalCodeWithName + 2919
25 0x2ae9d573de8d _PyEval_EvalFrameDefault + 24509
24 0x2ae9d5736caf /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/libpython3.8.so.1.0(+0x6bcaf) [0x2ae9d5736caf]
23 0x2ae9d573ed44 _PyEval_EvalFrameDefault + 28276
22 0x2ae9d576d455 /p/home/apps/DAAC/paraview/5.9.0_osmesa_mpich_kitware/bin/../lib/libpython3.8.so.1.0(+0xa2455) [0x2ae9d576d455]
21 0x2ae9d57690e2 _PyFunction_Vectorcall + 146
20 0x2ae9d5868a47 _PyEval_EvalCodeWithName + 2919
19 0x2ae9d573f902 _PyEval_EvalFrameDefault + 31282
18 0x2ae9d576bd43 PyCFunction_Call + 115
17 0x2aea1679eb04 /app/DAAC/paraview/5.9.0_osmesa_mpich_kitware/lib/python3.8/site-packages/paraview/modules/vtkRemotingViews.so(+0x19fb04) [0x2aea1679eb04]
16 0x2ae9db7b2573 vtkSMViewProxy::StillRender() + 307
15 0x2ae9d2b162e5 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
14 0x2ae9d2b172bb vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
13 0x2ae9d2b17482 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
12 0x2ae9d38aaddd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
11 0x2ae9d38aab3e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
10 0x2ae9d38aa40d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
9 0x2ae9d38a9da9 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
8 0x2ae9d1637398 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 8312
7 0x2ae9db710b91 vtkPVRenderView::StillRender() + 97
6 0x2ae9db71cb9a vtkPVRenderView::Render(bool, bool) + 2010
5 0x2ae9eb051620 vtkXOpenGLRenderWindow::Render() + 32
4 0x2ae9eafb3231 vtkOpenGLRenderWindow::Render() + 81
3 0x2ae9ef774d29 vtkRenderWindow::Render() + 169
2 0x2ae9eb2e7b8c vtkXRenderWindowInteractor::Initialize() + 204
1 0x2ae9eb52bb4b XSync + 27
0 0x2ae9d0eab400 /lib64/libc.so.6(+0x36400) [0x2ae9d0eab400]
( 22.060s) [paraview ] :0 FATL| Signal: SIGSEGV
error: exception occurred: Segmentation fault
acbauer@jim01>