A colleague found this, and it resolved the issue for me.
https://bugs.schedmd.com/show_bug.cgi?id=14134
The /etc/hosts on the compute nodes did not have this extra line, but
the file on the login/slurmctld node did have it.
I removed the line and now e.g. srun -x11 -N 1 xclock works.
Allan
Yes, 'salloc --x11' followed by 'ssh -X' to the allocated node works.
'hostname' command gives me the short hostname. However /etc/localhost
contains 'localhost' not the short hostname. I will experiement with
that.
These nodes are all running Ubuntu 20.04 LTS by the way.
Allan
Tina Friedrich
I remember having problems in that it worked via SSH - did you check
that (i.e. if you 'ssh -X' to a node it works?) - but not via SLURM.
That seemed to be authorization, and the way the SLURM inbuild method
generated the magic cookies - it couldn't cope with the node hostname
being it's FQDN,
Hi Allan,
I don't remember exactly, and it's just something to check ... I had a
similar problem a long time ago and it was a typo in /etc/hosts or
/etc/resolv.conf (login node?).
Best,
Weijun
On 10/6/2022 3:58 PM, Allan Streib wrote:
[Some people who received this message don't often get
Davide DelVento writes:
> Perhaps just a very trivial question, but it doesn't look you
> mentioned it: does your X-forwarding work from the login node? Maybe
> the X-server on your client is the problem and trying xclock on the
> login node would clarify that
Sorry, yes running xterm, xclock, e
Perhaps just a very trivial question, but it doesn't look you
mentioned it: does your X-forwarding work from the login node? Maybe
the X-server on your client is the problem and trying xclock on the
login node would clarify that
On Wed, Oct 5, 2022 at 12:03 PM Allan Streib wrote:
>
> Hi everyone,
