[slurm-users] RHEL8 support - Missing Symbols in SelectType libraries
Christopher Benjamin Coffey
Chris.Coffey at nau.edu
Tue Oct 29 15:11:38 UTC 2019
Brian, I've actually just started attempting to build slurm 19 on centos 8 yesterday. As you say, there are packages missing now from repos like:
rpmbuild -ta slurm-19.05.3-2.tar.bz2 --define '%_with_lua 1' --define '%_with_x11 1'
warning: Macro expanded in comment on line 22: %_prefix path install path for commands, libraries, etc.
warning: Macro expanded in comment on line 29: %_with_lua path build Slurm lua bindings
warning: Macro expanded in comment on line 161: %define _unpackaged_files_terminate_build 0
error: Failed build dependencies:
pkgconfig(lua) >= 5.1.0 is needed by slurm-19.05.3-2.el8.x86_64
python is needed by slurm-19.05.3-2.el8.x86_64
python (they have python2, and python3 now)
I was thinking on putting work into getting the spec file up to snuff, or building from source without the spec file.
Brian, what route are you taking? Building rpms, or just building with configure, make/make install?
Northern Arizona University
On 10/28/19, 12:18 PM, "slurm-users on behalf of Brian Andrus" <slurm-users-bounces at lists.schedmd.com on behalf of toomuchit at gmail.com> wrote:
I spoke too soon.
While I can successfully build/run slurmctld, slurmd is failing because ALL of the SelectType libraries are missing symbols.
Example from select_cons_tres.so:
slurmd: error: plugin_load_from_file: dlopen(/usr/lib64/slurm/select_cons_tres.so): /usr/lib64/slurm/select_cons_tres.so:
undefined symbol: powercap_get_cluster_current_cap
slurmd: error: Couldn't load specified plugin name for select/cons_tres: Dlopen of plugin file failed
slurmd: fatal: Can't find plugin for select/cons_tres
# nm -D /usr/lib64/slurm/libslurmfull.so|grep powercap_
000000000010f7b8 T slurm_free_powercap_info_msg
0000000000060060 T slurm_print_powercap_info_msg
So, sure enough powercap_get_cluster_current_cap is not in there.
Methinks the linking needs examined.
On 10/28/2019 2:32 AM, Benjamin Redling wrote:
On 28/10/2019 08.26, Bjørn-Helge Mevik wrote:
Taras Shapovalov <taras.shapovalov at brightcomputing.com> <mailto:taras.shapovalov at brightcomputing.com> writes:
Do I understand correctly that Slurm19 is not compatible with rhel8? It is
not in the list https://slurm.schedmd.com/platforms.html <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fslurm.schedmd.com%2Fplatforms.html&data=02%7C01%7Cchris.coffey%40nau.edu%7C5e5e524dc429474835aa08d75bdb8e16%7C27d49e9f89e14aa099a3d35b57b2ba03%7C0%7C1%7C637078870850114049&sdata=CCH2ZXKwnOuYpyF%2FGqrRX28bS%2FBcwG4IqRAX%2FtaPZ9M%3D&reserved=0>
"RedHat Enterprise Linux 7 (RHEL7), CentOS 7, Scientific Linux 7 (and newer)"
Perhaps that includes RHEL8, and CentOS 8, not only Scientific Linux 8?
AFAIK there won't be a Scientific Linux 8 (by Fermilab):
So it seems if there aren't any other maintainers taking care of a
potential SL8 and "and newer" was written intentionally it has to be
RHEL or CentOS 8.
More information about the slurm-users