[gridengine users] users Digest, Vol 113, Issue 2

Korzennik, Sylvain skorzennik at cfa.harvard.edu
Mon May 4 13:06:46 UTC 2020


We have no problem having jobs w/ X11 enabled, BUT users must use qlogin,
not qsub or qrsh (the way we have configured it).

We have switched from SGE to UGE, but I'm sure the 'issue'  is the same,
you need to have the '[qlogin|rlogin|rsh]_command" and "_deamon" set
accordingly, and if you use ssh, you need to have X-tunnelling enabled
(lssh -X) - it's not just simply a matter of setting up DISPLAY or
adjusting ~/.Xauthority. Here is our config:
qconf -sconf
[...]
qlogin_command               /cm/shared/apps/uge/var/cm/qlogin_wrapper
qlogin_daemon                /usr/sbin/sshd -i
rlogin_command               builtin
rlogin_daemon                builtin
rsh_command                  builtin
rsh_daemon                   builtin

with the following qlogin_wraper

#!/bin/sh
HOST=$1
PORT=$2
/usr/bin/ssh -X -o LogLevel=ERROR -p $PORT $HOST

We also have a dedicated interactive queue on a subset of compute nodes, w/
qtype set to INTERACTIVE and appropriate limits.

Our only gotcha w/ using ssh is that sshd is not properly propagating the
accounting information (hence some limits cannot be enforced and neither
qstat nor qacct returns meaningful values for these jobs). There is a SGE
patch to sshd one can try to enable accounting. Univa has provided us w/
their own patch (that I must confess CV-19 has delayed the testing).

You can't use builtin for qlogin_command since it does
not support X-tunneling (when DISPLAY is something like localhost:10.0),
I'm told that it supports the old X authorization mechanism (via xhost +)
that has been deprecated in most modern X implementations (for
obvious security reasons, so I can't confirm).

    Stay sane, safe and healthy, 6+ft away! Cheers,
      Sylvain
--



On Mon, May 4, 2020 at 8:00 AM <users-request at gridengine.org> wrote:

> Send users mailing list submissions to
>         users at gridengine.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://gridengine.org/mailman/listinfo/users
> or, via email, send a message with subject or body 'help' to
>         users-request at gridengine.org
>
> You can reach the person managing the list at
>         users-owner at gridengine.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of users digest..."
>
>
> Today's Topics:
>
>    1. Re: How to export an X11 back to the client? (William Hay)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 4 May 2020 11:31:49 +0100
> From: William Hay <w.hay at ucl.ac.uk>
> To: Mun Johl <Mun.Johl at wdc.com>
> Cc: SGE Mailing List <users at gridengine.org>
> Subject: Re: [gridengine users] How to export an X11 back to the
>         client?
> Message-ID: <20200504103149.GD4387 at hylic>
> Content-Type: text/plain; charset="utf-8"
>
> On Fri, May 01, 2020 at 06:44:08PM +0000, Mun Johl wrote:
> >    Hi,
> >
> >
> >
> >    I am using SGE on RHEL6.  I am trying to launch a qsub job (a TCL
> script)
> >    via grid that will result in a GUI application being opened on the
> >    caller?s display (which is a VNC session).
> Using qsub for this makes this more difficult than it needs to be since
> qsub jobs run largely disconnected from the submit host.  I wouldn't
> have thought you would want a delay with something interactive like
> this.  As Reuti suggested you could set up ssh tight integration (with X
> forwarding enabled in ssh) and then use qrsh -now n <command> to launch
> your app.
>
>
>
>
> >    What I?m seeing is that if I set DISPLAY to the actual VNC display
> (e.g.
> >    host1:4) in the wrapper script that invokes qsub, the GUI application
> Have you checked that host1 resolves to on the machine where you submit
> the job and the machine where it runs.  If you are getting a failure to
> connect it might be because you need to use the FQDN.
>
> >    complains that it cannot make a connection.  On a side note, I noticed
> In general X11 servers don't allow random clients to talk to
> the display.  The app may be (mis-)reporting a failure to authorise as a
> failure to connect.  This has little to do with grid engine per se just a
> side effect of running the app on a different machine from the X-Server.
> You may need to perform some manipulations with xauth to enable it.
>
> Do the grid engine servers share home directories with the machine where
> you are running qsub (eg via NFS or a cluster file system)?
> Authorisation tokens are usually stored in/read from  ~/.Xauthority.
>
> William
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: not available
> URL: <
> http://gridengine.org/pipermail/users/attachments/20200504/ab91ee13/attachment-0001.sig
> >
>
> ------------------------------
>
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users
>
>
> End of users Digest, Vol 113, Issue 2
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gridengine.org/pipermail/users/attachments/20200504/f6b677bb/attachment.html>


More information about the users mailing list