Can you ssh in as root and the su to the AD user to make sure that the node
is integrated correctly?

If you cannot su to an AD user on the node then Slurm will not be able to
resolve the UID either as they use the same methods.

On Wed, 13 Feb 2019, 12:35 Yugendra Guvvala, <yguvv...@cambridgecomputer.com>
wrote:

> No, we can’t ssh to compute nodes. And this is by design that no one
> should be able to ssh to compute nodes other than root.
>
> I figure that munge is not configured for AD. We have configured our login
> image for AD and slurm and mung configurations are on head node. Not sure
> how to integrate these.
>
> Thanks,
> Yugi
>
> On Feb 13, 2019, at 7:27 AM, Antony Cleave <antony.cle...@gmail.com>
> wrote:
>
> can you ssh to the compute node that job was trying to run on as as the AD
> user in question?
>
> I've  seen similar issues on AD integrated systems where some nodes boot
> from a different image that have not yet been joined to the domain.
>
> Antony
>
> On Wed, 13 Feb 2019 at 04:58, Yugendra Guvvala <
> yguvv...@cambridgecomputer.com> wrote:
>
>> Hi,
>>
>> We are bringing a new cluster online. We installed SLURM through Bright
>> Cluster Manager how ever we are running into a issue here.
>>
>> We are able to run jobs as root user and users created using bright
>> cluster (cmsh commands). How ever we use AD authentication for all our
>> users and when we try to submit jobs to slurm using AD users we are getting
>> following error message.
>>
>>
>> srun: fatal: Invalid user id: 10952
>> srun: fatal: Invalid user id: 10952
>> srun: error: cnode001: task 0: Exited with exit code 1
>>
>> Attached is the slurm.con file for reference. Please let us know if you
>> have any insight into this.
>>
>>
>>
>> Thanks,
>> Yugi
>>
>> *Yugendra Guvvala | HPC Technologist ** |** Cambridge Computer ** |** 
>> "Artists
>> in Data Storage" *
>> *Direct:* 781-250-3273  | *Cell*: 806-773-4464  |
>> yguvv...@cambridgecomputer.com  | www.cambridgecomputer.com
>>
>>
>> _______________________________________________________________________________________________
>>
>>

Reply via email to