"B" == Bryan Hill bhill@ucsd.edu writes:
B> The error about the differing slurm.conf shows up for all nodes B> whenever a config change occurs, but I'm assuming (maybe B> incorrectly) this is because the slurm.conf is on an NFS mount B> and the error can be ignored? >> >> often it can be ignored. But some changes obviously require the >> restart of slurmd on the nodes. It doesn't harm to do this even >> while jobs are running and it's done easily via the Slurm 'Node >> State Management' dialog in the GUI.
B> Great, thanks for the tip!
Actually, thinking about it, this is almost certainly a situation where a restart of slurmd is required, since gres.conf would have also changed and there is no way that slurmd would know about this change without a restart unless it does an automatic reread as a result of something like inotify which I highly doubt ...
>> Concerning the invalid argument: Can you please post the line in >> slurm.conf corresponding to node gpu-11?
B> NodeName=gpu-11 CoresPerSocket=12 Gres=gpu:titan:2 B> RealMemory=189773 Sockets=2 ThreadsPerCore=1