Black png returned when using a vnc session

[durack1]

@danlipsa @doutriaux1 I just ran the demo script BlueMarble_huss_satellite_view.html and received the appropriate graphic on the active VNC screen. What was saved to the png is below, and is certainly not what I was expecting: This is certainly not the expected behavior. What additional information do you require to better replicate the issue:

In [1]: import cdat_info
In [2]: cdat_info.version()
Out[2]: ['', 'v2.8']

[sankhesh]

I'm going to try this with mesa tomorrow to see if that works too.

I was able to setup VirtualGL and TurboVNC on a vagrant Ubuntu 16.04 box with mesa following the instructions on the wiki page.

@doutriaux1 Were you able to set it up?

[doutriaux1]

@sankhesh trying on crunchy now

the follwing does not exists on RH6:

Run the virtualGL server config script from text console (or remote via

ssh)

sudo /opt/VirtualGL/bin/vglserver_config

[doutriaux1]

I get this:

doutriaux1@crunchy:[~]:[15975]> sudo /opt/VirtualGL/bin/vglserver_config
sudo: /opt/VirtualGL/bin/vglserver_config: command not found
doutriaux1@crunchy:[~]:[15976]> locate vglserver_config
/usr/bin/vglserver_config
doutriaux1@crunchy:[~]:[15977]> sudo /usr/bin/vglserver_config
sudo: /usr/bin/vglserver_config: command not found

[sankhesh]

@doutriaux1 It could be a permissions issue when trying to install VirtualGL. Do you have full permissions in /opt/ ? Ref: https://sourceforge.net/p/virtualgl/discussion/401860/thread/6f2e2505/

I am not sure why you have /usr/bin/vglserver_config. Could it be from a previous installation? The default install location for VirtualGL is in /opt. See https://cdn.rawgit.com/VirtualGL/virtualgl/2.5.2/doc/index.html#hd005001

[doutriaux1]

@sankhesh I sudoed it. Anyhow I'm trying now now with vgl 2.4 which my yum was able to find and install. More soon

[doutriaux1]

@sankhesh I get the server up and running theres is no glxgears in the bin directory but the turboserver starts but runnnig vglrun leads to this:

doutriaux1@crunchy:[~]:[15502]> export DISPLAY=crunchy.llnl.gov:3
doutriaux1@crunchy:[~]:[15503]> vglrun python
[VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to
[VGL]    128.15.245.181, the IP address of your SSH client.
Python 2.7.13 | packaged by conda-forge | (default, May  2 2017, 12:48:11) 
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
CDMS system error: No such file or directory
CDMS I/O error: Opening file /usr/local/anaconda2/envs/2.10/share/uvcdat/sample_data/clt.nc
Traceback (most recent call last):
  File "/export/doutriaux1/.pythonrc", line 32, in <module>
    f=cdms2.open(fnm)
  File "/usr/local/anaconda2/envs/2.10/lib/python2.7/site-packages/cdms2/dataset.py", line 357, in openDataset
    return CdmsFile(path, mode, mpiBarrier=CdMpi)
  File "/usr/local/anaconda2/envs/2.10/lib/python2.7/site-packages/cdms2/dataset.py", line 1090, in __init__
    raise CDMSError('Cannot open file %s (%s)' % (path, err))
cdms2.error.CDMSError: Cannot open file /usr/local/anaconda2/envs/2.10/share/uvcdat/sample_data/clt.nc (No error)
>>> import vcs
>>> x=vcs.init()
>>> x.plot([1,2,3,4,3,2,1,2,3,4])
No protocol specified
[VGL] ERROR: Could not open display :0.

[doutriaux1]

Also the follwing hangs and never renders anything

doutriaux1@crunchy:[~]:[15503]> vglrun xeyes
[VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to
[VGL]    128.15.245.181, the IP address of your SSH client.

[doutriaux1]

@sankhesh do I need to connect to crunchy via ssh or via another vnc client the instructions are not clear about this.

[sankhesh]

@sankhesh do I need to connect to crunchy via ssh or via another vnc client the instructions are not clear about this.

I don't think it matters how you're connected to the server. As long as you have a VNC server session running, you should have a valid X environment.

[sankhesh]

Also the follwing hangs and never renders anything

doutriaux1@crunchy:[~]:[15503]> vglrun xeyes [VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to [VGL] 128.15.245.181, the IP address of your SSH client.

I think it might be rendering something in the VNC display. Try connecting via VNC to see if you see the xeyes window.

[sankhesh]

I'm not sure why the DISPLAY environment variable is not supplied to python. Perhaps try setting it within python using os.environ

[doutriaux1]

@sankhesh it's a total failure on crunchy. Please try. Instructions might need update. Here's what I did.

• started vglserver on crunchy
• download turnbvnc client on mac
• connect to crunchy from mac via trubovnc
• if I run vglrun python I get the bad display :0 error
• If I run the regular python it seg fault on opening of display...

Please try from crunchy

@danlipsa can you please try on crunchy as well?

Thanks.

[doutriaux1]

@sankhesh whilerunning vglrun python the os.environ["DISPLAY"] return correctly crunchy:3. But I do get bad display error...

[doutriaux1]

Also tried via regular ssh to crunchy

[sankhesh]

@doutriaux1 I think your setup should work. Try connecting via a VNC client and run xeyes to see if a window shows up.

[doutriaux1]

@sankhesh both vglrun xeyes and xeyes

work fine in my turbovnc client

but

doutriaux1@crunchy:[~]:[15936]> vglrun glxgears
[VGL] NOTICE: Automatically setting VGL_CLIENT environment variable to
[VGL]    128.15.245.181, the IP address of your SSH client.
No protocol specified
[VGL] ERROR: Could not open display :0.
doutriaux1@crunchy:[~]:[15937]> glxgears 
Error: couldn't get an RGB, Double-buffered visual

[danlipsa]

@doutriaux1 I get the same message if I run vglrun from an ssh connected to the server. You have to run vglrun only from turbovnc connected to your server.

[danlipsa]

@doutriaux1 This is my message:

~]$ vglrun glxgears
[VGL] NOTICE: Automatically setting the DISPLAY environment variable to
[VGL]    10.9.0.8:0.0, based on the IP address of your SSH client.
Error: couldn't open display 10.9.0.8:0.0
[~]$ 

[sankhesh]

@sankhesh both vglrun xeyes and xeyes

work fine in my turbovnc client

Awesome 👍 👏 It means you have the setup working.

but

[VGL] ERROR: Could not open display :0.

Could you please share the output of the following two commands (when connected via TurboVNC client):

  /opt/VirtualGL/bin/glxinfo -display :3.0

and

  vglrun -sp /opt/VirtualGL/bin/glxspheres

[doutriaux1]

@danlipsa I am getting this while connected via turbovnc

[doutriaux1]

@sankhesh do you have an account on crunchy? I would like for you to try it. Because It's definitely not working for me from my mac.

[sankhesh]

@doutriaux1 I don't. How do I get one?

[durack1]

@hoang1 can you help out here?

[doutriaux1]

@durack1 @sankhesh is taken care of. No worries.

[sankhesh]

@doutriaux1 Could you please try the setup on a local desktop (Ubuntu or Red Hat)?

[doutriaux1]

@sankhesh both my linux boxes are dead right now... I'll see if I can try the setup from a vm/docker

[doutriaux1]

@sankhesh I'm going to look into this as well: https://github.com/yantis/docker-virtualgl

[doutriaux1]

https://github.com/CDAT/cdat/wiki/Remote-server-setup-for-VNC @scottwittenburg please review and let me know if it helps.

[scottwittenburg]

Btw the link @danlipsa provided from the paraviewweb documention (high above), is broken now, but that documentation has moved here:

https://kitware.github.io/paraviewweb/docs/virtualgl_turbovnc_howto.html