<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi and thanks for all your answers and sorry for the delay in my
      answer. Yesterday I have installed in the controller machine the
      Slurm-18.08.3 to check if with this last release the Seff command
      is working fine. The behavior has improve but I still receive a
      error message:</p>
    <p><br>
    </p>
    <p># /usr/local/slurm-18.08.3/bin/seff 1694112<br>
      <b>Use of uninitialized value $lmem in numeric lt (<) at
        /usr/local/slurm-18.08.3/bin/seff line 130, <DATA> line
        624.</b><br>
      Job ID: 1694112<br>
      Cluster: XXXXX<br>
      User/Group: XXXXX<br>
      State: COMPLETED (exit code 0)<br>
      Nodes: 1<br>
      Cores per node: 2<br>
      CPU Utilized: 01:39:33<br>
      CPU Efficiency: 4266.43% of 00:02:20 core-walltime<br>
      Job Wall-clock time: 00:01:10<br>
      Memory Utilized: 0.00 MB (estimated maximum)<br>
      Memory Efficiency: 0.00% of 3.91 GB (3.91 GB/node)<br>
      [root@hydra ~]# <br>
    </p>
    <p><br>
    </p>
    <p>And due to this problem,  any job shows me as memory utilized the
      value of 0.00 MB.<br>
    </p>
    <p><br>
    </p>
    <p>With slurm-17.11.1 is working fine:</p>
    <p><br>
    </p>
    <p># /usr/local/slurm-17.11.0/bin/seff 1694112<br>
      Job ID: 1694112<br>
      Cluster: XXXXX<br>
      User/Group: XXXXX<br>
      State: COMPLETED (exit code 0)<br>
      Nodes: 1<br>
      Cores per node: 2<br>
      CPU Utilized: 01:39:33<br>
      CPU Efficiency: 4266.43% of 00:02:20 core-walltime<br>
      Job Wall-clock time: 00:01:10<br>
      Memory Utilized: 2.44 GB<br>
      Memory Efficiency: 62.57% of 3.91 GB<br>
      [root@hydra bin]# <br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">Miguel A. Sánchez Gómez
System Administrator
Research Programme on Biomedical Informatics - GRIB (IMIM-UPF)

Barcelona Biomedical Research Park (office 4.80)
Doctor Aiguader 88 | 08003 Barcelona (Spain)
Phone: +34/ 93 316 0522 | Fax: +34/ 93 3160 550
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:miguelangel.sanchez@upf.edu">miguelangel.sanchez@upf.edu</a>
</pre>
    <div class="moz-cite-prefix">On 11/06/2018 06:30 PM, Mike Cammilleri
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:DM5PR06MB25403DC62C61265165197BCCFBCB0@DM5PR06MB2540.namprd06.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
      <div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
        dir="ltr">
        <p style="margin-top:0;margin-bottom:0">Thanks for this. We'll
          try the workaround script. It is not mission-critical but our
          users have gotten accustomed to seeing these metrics at the
          end of each run and its nice to have. We are currently doing
          this in a test VM environment, so by the time we actually do
          the upgrade to the cluster perhaps the fix will be available
          then.</p>
        <p style="margin-top:0;margin-bottom:0"><br>
        </p>
        <div id="Signature">
          <div id="divtagdefaultwrapper" dir="ltr" style="font-size:
            12pt; color: rgb(0, 0, 0); font-family: Calibri, Helvetica,
            sans-serif, EmojiFont, "Apple Color Emoji",
            "Segoe UI Emoji", NotoColorEmoji, "Segoe UI
            Symbol", "Android Emoji", EmojiSymbols;">
            <p style="margin-top:0; margin-bottom:0">Mike Cammilleri</p>
            <p style="margin-top:0; margin-bottom:0">Systems
              Administrator</p>
            <p style="margin-top:0; margin-bottom:0">Department of
              Statistics | <span style="font-size:12pt">UW-Madison</span></p>
            <p style="margin-top:0; margin-bottom:0"><span
                style="font-size:12pt">1300 University Ave | Room 1280<br>
                608-263-6673 | <a class="moz-txt-link-abbreviated" href="mailto:mikec@stat.wisc.edu">mikec@stat.wisc.edu</a></span></p>
          </div>
        </div>
        <br>
        <br>
        <div style="color: rgb(0, 0, 0);">
          <hr style="display:inline-block;width:98%" tabindex="-1">
          <div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
              face="Calibri, sans-serif" color="#000000"><b>From:</b>
              slurm-users <a class="moz-txt-link-rfc2396E" href="mailto:slurm-users-bounces@lists.schedmd.com"><slurm-users-bounces@lists.schedmd.com></a>
              on behalf of Chris Samuel <a class="moz-txt-link-rfc2396E" href="mailto:chris@csamuel.org"><chris@csamuel.org></a><br>
              <b>Sent:</b> Tuesday, November 6, 2018 5:03 AM<br>
              <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:slurm-users@lists.schedmd.com">slurm-users@lists.schedmd.com</a><br>
              <b>Subject:</b> Re: [slurm-users] Seff error with
              Slurm-18.08.1</font>
            <div> </div>
          </div>
          <div class="BodyFragment"><font size="2"><span
                style="font-size:11pt;">
                <div class="PlainText">On 6/11/18 7:49 pm, Baker D.J.
                  wrote:<br>
                  <br>
                  > The good new is that I am assured by SchedMD that
                  the bug has been fixed <br>
                  > in v18.08.3.<br>
                  <br>
                  Looks like it's fixed in this commmit.<br>
                  <br>
                  commit 3d85c8f9240542d9e6dfb727244e75e449430aac<br>
                  Author: Danny Auble <a class="moz-txt-link-rfc2396E" href="mailto:da@schedmd.com"><da@schedmd.com></a><br>
                  Date:   Wed Oct 24 14:10:12 2018 -0600<br>
                  <br>
                       Handle symbol resolution errors in the 18.08
                  slurmdbd.<br>
                  <br>
                       Caused by b1ff43429f6426c when moving the
                  slurmdbd agent internals.<br>
                  <br>
                       Bug 5882.<br>
                  <br>
                  <br>
                  > Having said that we will probably live with this
                  issue <br>
                  > rather than disrupt users with another upgrade so
                  soon .<br>
                  <br>
                  An upgrade to 18.08.3 from 18.08.1 shouldn't be
                  disruptive though, <br>
                  should it?  We just flip a symlink and the users see
                  the new binaries, <br>
                  libraries, etc immediately, we can then restart
                  daemons as and when we <br>
                  need to (in the right order of course, slurmdbd,
                  slurmctld and then <br>
                  slurmd's).<br>
                  <br>
                  All the best,<br>
                  Chris<br>
                  -- <br>
                    Chris Samuel  :  <a href="http://www.csamuel.org/"
                    moz-do-not-send="true">http://www.csamuel.org/</a> 
                  :  Melbourne, VIC<br>
                  <br>
                </div>
              </span></font></div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>