I have an external SLURM v16 just for providing a DBD/MySQL. I have a SLURM v15 already connected to this DBD. The v14 is our PRD system. The v15 is our TST system. We are using the TST system for upgrade testing for the PRD system. When starting the slurmctl on v14 it starts but has no access to the DBD.
On the v14 slurmctld.log [2016-09-06T10:42:53.008] error: If munged is up, restart with --num-threads=10 [2016-09-06T10:42:53.008] error: Munge encode failed: Failed to access “PASSWORD": No such file or directory [2016-09-06T10:42:53.008] error: Creating authentication credential: Socket communication error [2016-09-06T10:42:53.009] error: slurmdbd: Sending DbdInit msg: Access/permission denied On the v16 slurmdbd.log [2016-09-06T10:44:59.079] error: Unpacking authentication credential: cannot unpack authentication type [2016-09-06T10:44:59.079] error: CONN:8 Failed to unpack DBD_INIT message [2016-09-06T10:44:59.079] error: CONN:8 Security violation, DBD_INIT [2016-09-06T10:44:59.079] error: Processing last message from connection 8(192.168.212.102) uid(-2) My suspicions are that the v14 to v16 API and the munge-plugin are too far apart. Can anyone validate this, or provide a fix? I want to know if I need to table this until we upgrade PRD to v15 which is still a couple months of testing away. -Chad ________________________________ *** The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copies of it. If you have any questions concerning this message, please contact the sender. ***
