[slurm-users] Can't start slurmdbd

Juan A. Cordero Varelaq bioinformatica-ibis at us.es
Tue Nov 21 01:37:41 MST 2017


I guess mariadb-devel was not installed by the time another person 
installed slurm. I have a bunch of slurm-* rpms I installed using "yum 
localinstall ...". Should I installed them in another way or remove slurm?

The file accounting_storage_mysql.so is bythe way absent on the machine.

Thanks
On 20/11/17 21:52, Lachlan Musicman wrote:
> Also - make sure you have MariaDB-devel when you make the RPMs - 
> that's the first bit.
> The second bit is you might have to find the 
> accounting_storage_mysql.so and place it in /usr/lib64/slurm.
>
> I think it might end up in 
> /path/to/rpmbuild/BUILD/sec/plugins/accounting/.libs/ or something 
> like that
>
> Cheers
> L.
>
> ------
> "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic 
> civics is the insistence that we cannot ignore the truth, nor should 
> we panic about it. It is a shared consciousness that our institutions 
> have failed and our ecosystem is collapsing, yet we are still here — 
> and we are creative agents who can shape our destinies. Apocalyptic 
> civics is the conviction that the only way out is through, and the 
> only way through is together. "
>
> /Greg Bloom/ @greggish 
> https://twitter.com/greggish/status/873177525903609857
>
> On 21 November 2017 at 06:35, Philip Kovacs <pkdevel at yahoo.com 
> <mailto:pkdevel at yahoo.com>> wrote:
>
>     Try adding this to your conf:
>
>     PluginDir=/usr/lib64/slurm
>
>
>     On Monday, November 20, 2017 6:48 AM, Juan A. Cordero Varelaq
>     <bioinformatica-ibis at us.es <mailto:bioinformatica-ibis at us.es>> wrote:
>
>
>     I did that but got the same errors.
>     slurmdbd.log contains by the way the following:
>
>         [2017-11-20T12:39:04.178] error: Couldn't find the specified
>         plugin name for accounting_storage/mysql looking at all files
>         [2017-11-20T12:39:04.179] error: cannot find
>         accounting_storage plugin for accounting_storage/mysql
>         [2017-11-20T12:39:04.179] error: cannot create
>         accounting_storage context for accounting_storage/mysql
>         [2017-11-20T12:39:04.179] fatal: Unable to initialize
>         accounting_storage/mysql accounting storage plugin
>
>     It seems it lacks the accounting_storage_mysql.so:
>
>         $ ls /usr/lib64/slurm/accounting_storage_*
>         /usr/lib64/slurm/accounting_storage_filetxt.so
>         /usr/lib64/slurm/accounting_storage_none.so
>         /usr/lib64/slurm/accounting_storage_slurmdbd.so
>
>     However, I did install the slurm-sql rpm package.
>     Any idea about what's failing?
>
>     Thanks
>     On 20/11/17 12:11, Lachlan Musicman wrote:
>>     On 20 November 2017 at 20:50, Juan A. Cordero Varelaq
>>     <bioinformatica-ibis at us.es <mailto:bioinformatica-ibis at us.es>> wrote:
>>
>>             $ systemctl start slurmdbd
>>             Job for slurmdbd.service failed because the control
>>         process exited with error code. See "systemctl status
>>         slurmdbd.service" and "journalctl -xe" for details.
>>             $ systemctl status slurmdbd.service
>>             ● slurmdbd.service - Slurm DBD accounting daemon
>>                Loaded: loaded (/etc/systemd/system/slurmdbd. service;
>>         enabled; vendor preset: disabled)
>>
>>                Active: failed (Result: exit-code) since lun
>>         2017-11-20 10:39:26 CET; 53s ago
>>               Process: 27592 ExecStart=/usr/sbin/slurmdbd
>>         $SLURMDBD_OPTIONS (code=exited, status=1/FAILURE)
>>
>>             nov 20 10:39:26 login_node systemd[1]: Starting Slurm DBD
>>         accounting daemon...
>>             nov 20 10:39:26 login_node systemd[1]: slurmdbd.service:
>>         control process exited, code=exited status=1
>>             nov 20 10:39:26 login_node systemd[1]: Failed to start
>>         Slurm DBD accounting daemon.
>>             nov 20 10:39:26 login_node systemd[1]: Unit
>>         slurmdbd.service entered failed state.
>>             nov 20 10:39:26 login_node systemd[1]: slurmdbd.service
>>         failed.
>>             $ journalctl -xe
>>             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
>>             nov 20 10:39:26 login_node systemd[1]: Starting Slurm DBD
>>         accounting daemon...
>>             -- Subject: Unit slurmdbd.service has begun start-up
>>             -- Defined-By: systemd
>>             -- Support: http://lists.freedesktop.org/m
>>         ailman/listinfo/systemd-devel
>>         <http://lists.freedesktop.org/mailman/listinfo/systemd-devel>
>>             --
>>             -- Unit slurmdbd.service has begun starting up.
>>             nov 20 10:39:26 login_node systemd[1]: slurmdbd.service:
>>         control process exited, code=exited status=1
>>             nov 20 10:39:26 login_node systemd[1]: Failed to start
>>         Slurm DBD accounting daemon.
>>             -- Subject: Unit slurmdbd.service has failed
>>             -- Defined-By: systemd
>>             -- Support: http://lists.freedesktop.org/m
>>         ailman/listinfo/systemd-devel
>>         <http://lists.freedesktop.org/mailman/listinfo/systemd-devel>
>>             --
>>             -- Unit slurmdbd.service has failed.
>>             --
>>             -- The result is failed.
>>             nov 20 10:39:26 login_node systemd[1]: Unit
>>         slurmdbd.service entered failed state.
>>             nov 20 10:39:26 login_node systemd[1]: slurmdbd.service
>>         failed.
>>             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
>>         thenticationAgent,
>>             nov 20 10:40:06 login_node gmetad[1519]: data_thread()
>>         for [HPCSIE] failed to contact node 192.168.2.10
>>             nov 20 10:40:06 login_node gmetad[1519]: data_thread()
>>         got no answer from any [HPCSIE] datasource
>>             nov 20 10:40:13 login_node dhcpd[2320]: DHCPREQUEST for
>>         192.168.2.19 from XX:XX:XX:XX:XX:XX via enp6s0f1
>>             nov 20 10:40:13 login_node dhcpd[2320]: DHCPACK on
>>         192.168.2.19 to XX:XX:XX:XX:XX:XX via enp6s0f1
>>             nov 20 10:40:39 login_node dhcpd[2320]: DHCPREQUEST for
>>         192.168.2.13 from XX:XX:XX:XX:XX:XX via enp6s0f1
>>             nov 20 10:40:39 login_node dhcpd[2320]: DHCPACK on
>>         192.168.2.13 to XX:XX:XX:XX:XX:XX via enp6s0f1
>>
>>         I've just found out the file `/var/run/slurmdbd.pid` does not
>>         even exist.
>>
>>
>>
>>     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?
>>
>>     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.
>>
>>     hostname -s
>>
>>     will give you the short name
>>
>>     Cheers
>>     L.
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20171121/2f45ab68/attachment-0001.html>


More information about the slurm-users mailing list