[slurm-users] Munge decode failing on new node

[Carlos Fenoy]

I’d check ntp as your encoding time seems odd to me

On Wed, 15 Apr 2020 at 19:59, Dean Schulze <dean.w.schulze at gmail.com> wrote:

> I've installed two new nodes onto my slurm cluster.  One node works, but
> the other one complains about an invalid credential for munge.  I've
> verified that the munge.key is the same as on all other nodes with
>
> sudo cksum /etc/munge/munge.key
>
> I recopied a munge.key from a node that works.  I've verified that munge
> uid and gid are the same on the nodes.  The time is in sync on all nodes.
>
> Here is what is in the slurmd.log:
>
>  error: Unable to register: Unable to contact slurm controller (connect
> failure)
>  error: Munge decode failed: Invalid credential
>  ENCODED: Wed Dec 31 17:00:00 1969
>  DECODED: Wed Dec 31 17:00:00 1969
>  error: authentication: Invalid authentication credential
>  error: slurm_receive_msg_and_forward: Protocol authentication error
>  error: service_connection: slurm_receive_msg: Protocol authentication
> error
>  error: Unable to register: Unable to contact slurm controller (connect
> failure)
>
> I've checked in the munged.log and all it says is
>
> Invalid credential
>
> Thanks for your help
>
-- 
--
Carles Fenoy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20200415/5a8ff437/attachment.htm>