<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>I did that but got the same errors.</p>
    <p>slurmdbd.log contains by the way the following:</p>
    <blockquote>
      <p><tt>[2017-11-20T12:39:04.178] error: Couldn't find the
          specified plugin name for accounting_storage/mysql looking at
          all files</tt><tt><br>
        </tt><tt>[2017-11-20T12:39:04.179] error: cannot find
          accounting_storage plugin for accounting_storage/mysql</tt><tt><br>
        </tt><tt>[2017-11-20T12:39:04.179] error: cannot create
          accounting_storage context for accounting_storage/mysql</tt><tt><br>
        </tt><tt>[2017-11-20T12:39:04.179] fatal: Unable to initialize
          accounting_storage/mysql accounting storage plugin</tt><br>
      </p>
    </blockquote>
    <p>It seems it lacks the accounting_storage_mysql.so:</p>
    <blockquote>
      <p><tt>$ ls /usr/lib64/slurm/accounting_storage_*</tt><tt><br>
        </tt><tt>/usr/lib64/slurm/accounting_storage_filetxt.so 
          /usr/lib64/slurm/accounting_storage_none.so 
          /usr/lib64/slurm/accounting_storage_slurmdbd.so</tt></p>
    </blockquote>
    <p>However, I did install the slurm-sql rpm package.</p>
    <p>Any idea about what's failing?</p>
    <p><br>
    </p>
    <p>Thanks<br>
    </p>
    <div class="moz-cite-prefix">On 20/11/17 12:11, Lachlan Musicman
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAGBeqiO+3b2O-0kW8EY0vSvgoboL=eumbBt-P+Mq+v18KBBCpA@mail.gmail.com"
      type="cite">
      <div dir="ltr">On 20 November 2017 at 20:50, Juan A. Cordero
        Varelaq <span dir="ltr"><<a moz-do-not-send="true"
            href="mailto:bioinformatica-ibis@us.es" target="_blank">bioinformatica-ibis@us.es</a>></span>
        wrote:<br>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">    $
              systemctl start slurmdbd<br>
                  Job for slurmdbd.service failed because the control
              process exited with error code. See "systemctl status
              slurmdbd.service" and "journalctl -xe" for details.<br>
                  $ systemctl status slurmdbd.service<br>
                  ● slurmdbd.service - Slurm DBD accounting daemon<br>
                     Loaded: loaded (/etc/systemd/system/slurmdbd.<wbr>service;
              enabled; vendor preset: disabled)<br>
                     Active: failed (Result: exit-code) since lun
              2017-11-20 10:39:26 CET; 53s ago<br>
                    Process: 27592 ExecStart=/usr/sbin/slurmdbd
              $SLURMDBD_OPTIONS (code=exited, status=1/FAILURE)<br>
              <br>
                  nov 20 10:39:26 login_node systemd[1]: Starting Slurm
              DBD accounting daemon...<br>
                  nov 20 10:39:26 login_node systemd[1]:
              slurmdbd.service: control process exited, code=exited
              status=1<br>
                  nov 20 10:39:26 login_node systemd[1]: Failed to start
              Slurm DBD accounting daemon.<br>
                  nov 20 10:39:26 login_node systemd[1]: Unit
              slurmdbd.service entered failed state.<br>
                  nov 20 10:39:26 login_node systemd[1]:
              slurmdbd.service failed.<br>
                  $ journalctl -xe<br>
                  nov 20 10:39:26 login_node polkitd[1078]: Registered
              Authentication Agent for unix-process:27586:119889015
              (system bus name :1.871 [/usr/bin/pkttyagent --notify-fd 5
              --fallback], object path /or<br>
                  nov 20 10:39:26 login_node systemd[1]: Starting Slurm
              DBD accounting daemon...<br>
                  -- Subject: Unit slurmdbd.service has begun start-up<br>
                  -- Defined-By: systemd<br>
                  -- Support: <a moz-do-not-send="true"
                href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel"
                rel="noreferrer" target="_blank">http://lists.freedesktop.org/m<wbr>ailman/listinfo/systemd-devel</a><br>
                  --<br>
                  -- Unit slurmdbd.service has begun starting up.<br>
                  nov 20 10:39:26 login_node systemd[1]:
              slurmdbd.service: control process exited, code=exited
              status=1<br>
                  nov 20 10:39:26 login_node systemd[1]: Failed to start
              Slurm DBD accounting daemon.<br>
                  -- Subject: Unit slurmdbd.service has failed<br>
                  -- Defined-By: systemd<br>
                  -- Support: <a moz-do-not-send="true"
                href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel"
                rel="noreferrer" target="_blank">http://lists.freedesktop.org/m<wbr>ailman/listinfo/systemd-devel</a><br>
                  --<br>
                  -- Unit slurmdbd.service has failed.<br>
                  --<br>
                  -- The result is failed.<br>
                  nov 20 10:39:26 login_node systemd[1]: Unit
              slurmdbd.service entered failed state.<br>
                  nov 20 10:39:26 login_node systemd[1]:
              slurmdbd.service failed.<br>
                  nov 20 10:39:26 login_node polkitd[1078]: Unregistered
              Authentication Agent for unix-process:27586:119889015
              (system bus name :1.871, object path
              /org/freedesktop/PolicyKit1/Au<wbr>thenticationAgent,<br>
                  nov 20 10:40:06 login_node gmetad[1519]: data_thread()
              for [HPCSIE] failed to contact node 192.168.2.10<br>
                  nov 20 10:40:06 login_node gmetad[1519]: data_thread()
              got no answer from any [HPCSIE] datasource<br>
                  nov 20 10:40:13 login_node dhcpd[2320]: DHCPREQUEST
              for 192.168.2.19 from XX:XX:XX:XX:XX:XX via enp6s0f1<br>
                  nov 20 10:40:13 login_node dhcpd[2320]: DHCPACK on
              192.168.2.19 to XX:XX:XX:XX:XX:XX via enp6s0f1<br>
                  nov 20 10:40:39 login_node dhcpd[2320]: DHCPREQUEST
              for 192.168.2.13 from XX:XX:XX:XX:XX:XX via enp6s0f1<br>
                  nov 20 10:40:39 login_node dhcpd[2320]: DHCPACK on
              192.168.2.13 to XX:XX:XX:XX:XX:XX via enp6s0f1<br>
              <br>
              I've just found out the file `/var/run/slurmdbd.pid` does
              not even exist.<br>
            </blockquote>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>The pid file is the "process id" - it's only there if
              the process is running. So when slurmdbd is not running,
              it wont be there. Supposedly. Sometimes I do "touch
              /var/run/slurmdbd.pid" and try again?</div>
            <div><br>
            </div>
            <div>I've also found that using the host's short name is
              preferable to localhost. Make sure the host's short name
              is in /etc/hosts too.</div>
            <div><br>
            </div>
            <div>hostname -s <br>
            </div>
            <div><br>
            </div>
            <div>will give you the short name</div>
            <div><br>
            </div>
            <div>Cheers</div>
            <div>L.<br>
            </div>
            <div> </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>