Re: [Paraview] Remote rendering through reverse SSH breaks with a GLX error

[Utkarsh Ayachit]

Thanks for the update, Robert.

Utkarsh

On Fri, Nov 3, 2017 at 4:22 PM, Robert Sawko  wrote:
> Utkarsh,
>
> Again, thanks again for the comment and sorry for missing the email. I am
> checking my filter rules as this didn't get through to my inbox.
>
> Your insight was quite right: it's all down to drivers. I've been working on
> PV with EGL since then and I can get it all work under Ubuntu POWER8 NVIDIA
> driver but not under RHEL. There seems to be a packaging problem in RHEL where
> presumably an older or flawed version of EGL is shipped. I've been promised a
> fix soon so I am waiting for this.
>
> I've got access to two clusters with K80s and P100s and my intention is to run
> EGL enabled PV on both of them. X-less config is ideal as I could make any 
> node
> act as a PV server. I'll keep you posted.
>
> Robert
> --
> P-hacking again...
> https://www.youtube.com/watch?v=42QuXLucH3Q
> Sorry, but I think p-values are important.
___
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

Re: [Paraview] Remote rendering through reverse SSH breaks with a GLX error

[Robert Sawko]

Utkarsh,

Again, thanks again for the comment and sorry for missing the email. I am
checking my filter rules as this didn't get through to my inbox.

Your insight was quite right: it's all down to drivers. I've been working on
PV with EGL since then and I can get it all work under Ubuntu POWER8 NVIDIA
driver but not under RHEL. There seems to be a packaging problem in RHEL where
presumably an older or flawed version of EGL is shipped. I've been promised a
fix soon so I am waiting for this.

I've got access to two clusters with K80s and P100s and my intention is to run
EGL enabled PV on both of them. X-less config is ideal as I could make any node
act as a PV server. I'll keep you posted.

Robert
-- 
P-hacking again...
https://www.youtube.com/watch?v=42QuXLucH3Q
Sorry, but I think p-values are important.
___
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

Re: [Paraview] Remote rendering through reverse SSH breaks with a GLX error

[Utkarsh Ayachit]

Robert,

A few suggestions:

1. let's see what GL you're getting. If you run the following, what it
the output?
   
   pgc104% DISPLAY=:0.0 glxinfo

2. What GPU do you have and which drivers? If it's NVidia with new
enough drivers that support EGL, an EGL-enabled build may be a good
way to circumvent x-server issues.

Utkarsh

On Thu, Sep 28, 2017 at 11:43 AM, Robert Sawko  wrote:
> Dear Paraviewers,
>
> I am trying to run Paraview in a client-server mode on a remote compute node
> using a reverse SSH through the login node.
>
> I have successfully worked out my port forwarding skulduggery and was able to
> connect to a host which does NOT run X server. Inside my local client. I do 
> get
> an error
>
> "Display is not accessible on the server side. Remote rendering
> will be disabled"
>
> This is to be expected on the node without X.
>
> On the node with X running my client gets connected but then breaks with:
>
> Waiting for client...
> Connection URL: cs://pgc104:6
> Accepting connection(s): pgc104:6
> Client connected.
> Xlib:  extension "GLX" missing on display ":0.0".
> Xlib:  extension "GLX" missing on display ":0.0".
> ...
> (core dumped)
>
>
> Finally on the login node client-server works fine and rendering (I guess)
> is done on the remote side as I don't get any errors. We have made sure that
> xorg.conf on login and X-enabled compute node are the same.
>
>
> My connection procedure:
>
> local% ssh -L 6:localhost:6 login_node
> login% bsub -R "select[hname=pgc104]" -Is /bin/bash
> pgc104% ssh -N -R 6:localhost:6 login &
> pgc104% DISPLAY=:0.0 pvserver -sp=6 --use-offscreen-rendering
> local% paraview->connect to localhost:6
>
> Same thing works on pgc304 which doesn't run X. Please let us know if you have
> any suggestions.
>
> Best wishes,
> Robert
> --
> Ironically, it was Christopher Columbus who was wrong
> http://en.wikipedia.org/wiki/Myth_of_the_Flat_Earth
> ___
> 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
___
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

[Paraview] Remote rendering through reverse SSH breaks with a GLX error

[Robert Sawko]

Dear Paraviewers,

I am trying to run Paraview in a client-server mode on a remote compute node
using a reverse SSH through the login node.

I have successfully worked out my port forwarding skulduggery and was able to
connect to a host which does NOT run X server. Inside my local client. I do get
an error

"Display is not accessible on the server side. Remote rendering
will be disabled"

This is to be expected on the node without X.

On the node with X running my client gets connected but then breaks with:

Waiting for client...
Connection URL: cs://pgc104:6
Accepting connection(s): pgc104:6
Client connected.
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
...
(core dumped)


Finally on the login node client-server works fine and rendering (I guess)
is done on the remote side as I don't get any errors. We have made sure that
xorg.conf on login and X-enabled compute node are the same.


My connection procedure:

local% ssh -L 6:localhost:6 login_node
login% bsub -R "select[hname=pgc104]" -Is /bin/bash
pgc104% ssh -N -R 6:localhost:6 login &
pgc104% DISPLAY=:0.0 pvserver -sp=6 --use-offscreen-rendering
local% paraview->connect to localhost:6

Same thing works on pgc304 which doesn't run X. Please let us know if you have
any suggestions.

Best wishes,
Robert
-- 
Ironically, it was Christopher Columbus who was wrong
http://en.wikipedia.org/wiki/Myth_of_the_Flat_Earth
___
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