We have the same setup and see the same message so we added the flag to ignore it. Must be an NFS thing.
On 9 Jan 2014 19:14, =?ISO-8859-1?Q?Per_L=F6nnborg?= <[email protected]> wrote: Lennart Karlsson skrev 2014-01-09 12:01: > > On 01/09/2014 10:51 AM, Per Lönnborg wrote: >> >> Hello, >> >> we get these "error: Node xxxx appears to have a different slurm.conf >> than the slurmctld" messages reported in slurmctld.log for some nodes >> in our cluster. >> >> I have seen this before but have forgotten what it means :) >> >> The whole message is: >> slurmctld: error: Node xxxxx appears to have a different slurm.conf >> than the slurmctld. This could cause issues with communication and >> functionality. Please review both files and make sure they are the >> same. If this is expected ignore, and set DebugFlags=NO_CONF_HASH in >> your slurm.conf. >> >> Which files is "Please review both files"? >> >> We have recently started running slurm 2.6.3, and have upgraded the >> slurmd binary on the nodes as well, but not at the same time. >> >> >> Thanks >> >> /Per > > Hello Per, > > The two files are: > > 1/ The slurm.conf file on the server running slurmctld > > 2/ The slurm.conf file on node xxxx > > SLURM wants/needs these two files to have the same contents. > > Regards, > -- Lennart Karlsson, UPPMAX, Uppsala University, Sweden > http://www.uppmax.uu.se > But we don't have a slurm.conf on the nodes...the nodes reads slurm.conf on the server (via NFS) /Per ________________________________ This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original.
