I see two separate, unrelated problems here:
Problem 1:
Warning: untrusted X11 forwarding setup failed: xauth key data not
generated
What have you done to investigate this xauth problem further?
I know there have been discussions about this problem in the past on
this mailing list. Did you search to see if the previous discussions
contained a fix for this?
Problem 2:
./workbench.sh: line 4:
/state/partition1/ans190/v190/Framework/bin/Linux64/runwb2: No such
file or directory
Some thing is wrong with your job specification. You are referencing an
incorrect path somewhere.
Prentice
On 4/27/19 5:20 AM, Mahmood Naderan wrote:
>More constructively - maybe the list can help you get the X11
applications to run using Slurm.
>Could you give some details please?
For example, I an not run this GUI program with salloc
[mahmood@rocks7 ~]$ cat workbench.sh
#!/bin/bash
unset SLURM_GTIDS
/state/partition1/ans190/v190/Framework/bin/Linux64/runwb2
[mahmood@rocks7 ~]$ rocks run host compute-0-1 "ls
/state/partition1/ans190/v190/Framework/bin/Linux64/runwb2"
Warning: untrusted X11 forwarding setup failed: xauth key data not
generated
/state/partition1/ans190/v190/Framework/bin/Linux64/runwb2
[mahmood@rocks7 ~]$ salloc -w compute-0-1 -c 2 --mem=4G -p RUBY -A y4
./workbench.sh
salloc: Granted job allocation 938
./workbench.sh: line 4:
/state/partition1/ans190/v190/Framework/bin/Linux64/runwb2: No such
file or directory
salloc: Relinquishing job allocation 938
Regards,
Mahmood
On Wed, Apr 24, 2019 at 12:33 PM John Hearns <hear...@googlemail.com
<mailto:hear...@googlemail.com>> wrote:
I would suggest that if those applications really are not possible
with Slurm - then reserve a set of nodes for interactive use and
disable the Slurm daemon on them.
Direct users to those nodes.
More constructively - maybe the list can help you get the X11
applications to run using Slurm.
Could you give some details please?
