<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">If you check the source up on Github, that's more of a warning produced when you didn't specify a CPU count and it's going to calculate from the socket-core-thread numbers (src/common/read_config.c):<div class=""><br class=""></div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>/* Node boards are factored into sockets */</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>if ((n->cpus != n->sockets) &&</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span> (n->cpus != n->sockets * n->cores) &&</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span> (n->cpus != n->sockets * n->cores * n->threads)) {</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>error("NodeNames=%s CPUs=%d match no Sockets, Sockets*CoresPerSocket or Sockets*CoresPerSocket*ThreadsPerCore. Resetting CPUs.",</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span> n->nodenames, n->cpus);</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>n->cpus = n->sockets * n->cores * n->threads;</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>}</div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div><div class="">This behavior is present beginning in 18.x releases; in 17.x and earlier the inferred n->cpus was done quietly.</div><div class=""><br class=""></div><div class=""><br class=""><blockquote type="cite" class="">On Jun 16, 2020, at 04:12 , Ole Holm Nielsen <<a href="mailto:Ole.H.Nielsen@fysik.dtu.dk" class="">Ole.H.Nielsen@fysik.dtu.dk</a>> wrote:<br class=""><br class="">Today we upgraded the controller node from 19.05 to 20.02.3, and immediately all Slurm commands (on the controller node) give error messages for all partitions:<br class=""><br class=""># sinfo --version<br class="">sinfo: error: NodeNames=a[001-140] CPUs=1 match no Sockets, Sockets*CoresPerSocket or Sockets*CoresPerSocket*ThreadsPerCore. Resetting CPUs.<br class="">(lines deleted)<br class="">slurm 20.02.3<br class=""><br class="">In slurm.conf we have defined NodeName like:<br class=""><br class="">NodeName=a[001-140] Weight=10001 Boards=1 SocketsPerBoard=2 CoresPerSocket=4 ThreadsPerCore=1 ...<br class=""><br class="">According to the slurm.conf manual the CPUs should then be calculated automatically:<br class=""><br class="">"If CPUs is omitted, its default will be set equal to the product of Boards, Sockets, CoresPerSocket, and ThreadsPerCore."<br class=""><br class="">Has anyone else seen this error with Slurm 20.02?<br class=""><br class="">I wonder if there is a problem with specifying SocketsPerBoard in stead of Sockets? The slurm.conf manual doesn't seem to prefer one over the other.<br class=""><br class="">I've opened a bug <a href="https://bugs.schedmd.com/show_bug.cgi?id=9241" class="">https://bugs.schedmd.com/show_bug.cgi?id=9241</a><br class=""><br class="">Thanks,<br class="">Ole<br class=""><br class=""><br class=""></blockquote><br class=""></div></body></html>