<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Thank you. I sync /etc/slurm.conf from slurmctld node then then re-run slurmdbd as root, which seems to solve the problem. Before that, "sacctmgr list clusters" complained missing /etc/slurm.conf .<div class=""><br class=""></div><div class="">Best,</div><div class=""><br class=""></div><div class="">Jianwen</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 11, 2019, at 12:33, Chris Samuel <<a href="mailto:chris@csamuel.org" class="">chris@csamuel.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 10/1/19 6:15 pm, Jianwen Wei wrote:<br class=""><br class=""><blockquote type="cite" class="">I am using SLURM 17.11 on CentOS 7. I find that QoS settings, say GrpNodes for an account, in sacctmgr requires restarting slurmcltd to take effect.<br class=""></blockquote><br class="">This sounds like a configuration issue, and usually it's because slurmdbd cannot connect back to the control daemon on the IP address and port it has registered with it.<br class=""><br class="">If you do "sacctmgr list clusters" and then from the system running slurmdbd try and connect with nc or telnet to the listed ControlHost on the listed ControlPort you may find it doesn't work.<br class=""><br class="">Sometimes this is firewall related and sometimes this is because slurmctld tells slurmdbd about an IP address that isn't reachable rather than one that is.<br class=""><br class="">Hope this helps!<br class=""><br class="">All the best,<br class="">Chris<br class="">-- <br class=""> Chris Samuel : <a href="http://www.csamuel.org/" class="">http://www.csamuel.org/</a> : Melbourne, VIC<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>