Hi Marcus, I did not restarted munge previously. So I restarted munge and follow by slurmd, but the issue still persists.
I ran the following test from piglet-17 to verify the munge installation, it looks good. $ munge -n | unmunge STATUS: Success (0) ENCODE_HOST: piglet-17.sg.corp.prestolabs.io (127.0.1.1) ENCODE_TIME: 2019-10-07 16:14:55 +0800 (1570436095) DECODE_TIME: 2019-10-07 16:14:55 +0800 (1570436095) TTL: 300 CIPHER: aes128 (4) MAC: sha1 (3) ZIP: none (0) UID: turing (1000) GID: turing (1000) LENGTH: 0 $ munge -n | ssh turing@10.15.2.18 unmunge turing@10.15.2.18's password: STATUS: Success (0) ENCODE_HOST: piglet-18.sg.corp.prestolabs.io (127.0.1.1) ENCODE_TIME: 2019-10-07 16:15:19 +0800 (1570436119) DECODE_TIME: 2019-10-07 16:15:21 +0800 (1570436121) TTL: 300 CIPHER: aes128 (4) MAC: sha1 (3) ZIP: none (0) UID: turing (1000) GID: turing (1000) LENGTH: 0 Best regards, Eddy Swan On Mon, Oct 7, 2019 at 4:09 PM Marcus Wagner <wag...@itc.rwth-aachen.de> wrote: > Hmm, that is strange. I asked because of the errors below: > > On 10/7/19 9:36 AM, Eddy Swan wrote: > > [2019-10-07T13:38:49.260] error: slurm_cred_create: getpwuid failed for > uid=1000 > [2019-10-07T13:38:49.260] error: slurm_cred_create error > > > and "id" uses the same call (ltrace excerpt): > > getpwuid(0x9e7e, 0x7f0850f18a00, 9, > 9) > = 0x7f0850f19260 > > Did you restart munge and afterwards restart the slurm daemons? > Though, the error with wrong munge keys are more like "zero bytes > transmitted". > > I'm a little bit confused. > > -- > Marcus Wagner, Dipl.-Inf. > > IT Center > Abteilung: Systeme und Betrieb > RWTH Aachen University > Seffenter Weg 23 > 52074 Aachen > Tel: +49 241 80-24383 > Fax: +49 241 80-624383wag...@itc.rwth-aachen.dewww.itc.rwth-aachen.de > >