[Paraview] ParaViewWeb Visualizer black screen

Tue Oct 10 10:24:32 EDT 2017

Thanks Louise for your feedback and glad you figure it out.

Seb

On Tue, Oct 10, 2017 at 8:21 AM, <louise.davies at stfc.ac.uk> wrote:

> Hi Seb,
>
>
>
> Thanks for your help. I was indeed having the same behaviour no matter
> whether I ran Visualizer by the command line. The problem was that my
> server had a screensaver that when activated made it so that ParaViewWeb
> could only display a black screen. So for future reference: if anyone else
> has problems with a pure black screen but no errors – check to see if you
> have a screensaver blacking out the screen!
>
>
>
> Kind Regards,
>
>
>
> Louise
>
>
>
> *From:* Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
> *Sent:* 02 October 2017 17:09
> *To:* Davies, Louise (STFC,RAL,SC) <louise.davies at stfc.ac.uk>;
> paraview at paraview.org
>
> *Subject:* Re: [Paraview] ParaViewWeb Visualizer black screen
>
>
>
> Hi Louise,
>
>
>
> You are right, there is indeed more changes which might not be strait
> forward for you to fix. Even if in reality, it is only a bunch of import
> path to fix.
>
>
>
> Just out of curiosity, did you try to run the command line that the
> launcher is running by hand and see if you have the same behavior as well
> as maybe other error output?
>
>
>
> Otherwise, you right the screen size should be more than enough.
>
>
>
> Seb
>
>
>
> PS: I've added back the mailing list so others could benefit from our
> discussion.
>
>
>
> On Mon, Oct 2, 2017 at 10:02 AM, <louise.davies at stfc.ac.uk> wrote:
>
> Hi Seb,
>
>
>
> The screen size is 1920 x 1080, which seems like it should be sufficiently
> large enough. It does seem as though that’s the problematic line from the
> logs though…
>
>
>
> I’m currently running 5.4.0 and not the nightly/master so testing out
> pvbatch over pvpython is difficult. I tried getting the nightly version
> working but it seems as though there are more changes involved than just
> that – half the paths I reference are wrong (probably due to stuff changing
> paths upstream, e.g. launcher.py is in a different location now) and it
> seems more trouble than it’s worth to test it.
>
>
>
> Louise
>
>
>
> *From:* Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
> *Sent:* 02 October 2017 14:47
> *To:* Davies, Louise (STFC,RAL,SC) <louise.davies at stfc.ac.uk>
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] ParaViewWeb Visualizer black screen
>
>
>
> Hi Louise,
>
>
>
> I'm wondering how big is the display on the remote server? Even if no
> screen is connected, you do need to define a display size which in your
> case may be tiny by default?
>
>
>
> Otherwise, if you use the nightly binaries or paraview/master, you can
> tweak your launcher config to use pvbatch instead of pvpython which
> leverage a true offscreen rendering which will be then independent of the
> screen resolution. But you will need to set the following environment
> variable. PV_ALLOW_BATCH_INTERACTION=1
>
>
>
> It might also be something else, but the message "window did not resize"
> looked suspicious.
>
>
>
> Seb
>
>
>
>
>
> On Mon, Oct 2, 2017 at 6:41 AM, <louise.davies at stfc.ac.uk> wrote:
>
> Hello,
>
>
>
> I have been trying to set up a ParaViewWeb server on my CentOS 6 machine
> to run Visualizer. I have gotten to a point where the UI loads correctly
> but remote rendering only displays a black screen. Not even the axes in the
> bottom left are displayed. However, if I switch to local rendering mode it
> works as normal. There are no errors at all in the Apache logs and the
> session log starts fine but after the twisted server startup and the lines
> filled with plus signs, I get the lines:
>
>
>
> 2017-10-02 11:14:48+0100 [_GenericHTTPChannelProtocol,0,127.0.0.1] Client
> has reconnected, cancelling reaper
>
> 2017-10-02 11:14:48+0100 [_GenericHTTPChannelProtocol,0,127.0.0.1]
> on_connect: connection count = 1
>
> 2017-10-02 11:14:48+0100 [-] Property BeginValueCapture has no GetData()
> method, skipping
>
> 2017-10-02 11:14:48+0100 [-] Property CaptureValuesFloat has no GetData()
> method, skipping
>
> 2017-10-02 11:14:48+0100 [-] Property CaptureZBuffer has no GetData()
> method, skipping
>
> 2017-10-02 11:14:48+0100 [-] Property EndValueCapture has no GetData()
> method, skipping
>
> 2017-10-02 11:14:48+0100 [-] Property Send to OpenVR has no GetData()
> method, skipping
>
> 2017-10-02 11:14:48+0100 [-] Property StartCaptureLuminance has no
> GetData() method, skipping
>
> 2017-10-02 11:14:48+0100 [-] Property StopCaptureLuminance has no
> GetData() method, skipping
>
> Warning: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-
> linux-shared-release_superbuild/build/superbuild/
> paraview/src/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx, line 1093
>
> vtkXOpenGLRenderWindow (0x3e184d0): warning window did not resize in the
> allotted time
>
>
>
> Since it works with local rendering and not remote rendering I feel as
> though it must be a problem with OpenGL, but running glxinfo shows that the
> user running the launcher has access to direct rendering.
>
>
>
> Any suggestions on what could possibly be going wrong would be greatly
> appreciated.
>
>
>
> Kind Regards,
>
>
>
> Louise
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/
> opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20171010/c7a87649/attachment.html>