Dear Josef,
thanks a lot again for your help. Unfortunately I cannot solve this problem.
According to the Slurm documentation (https://slurm.schedmd.com/quickstart_admin.html#upgrade) I have to upgrade only slurmdbd at the very beginning and the cluster should be able to work even with slurmdbd-23.11.0-1 and slurmctld-23.02.3-1 and slurmd-23.02.3-1.
The slurmdbd-23.11.0-1 package should provide the following files:
$ rpm -ql slurm-slurmdbd-23.11.0-1-no-frontend.el8.x86_64.rpm /usr/lib/.build-id /usr/lib/.build-id/01 /usr/lib/.build-id/01/da333fd28f1765164e46d00569ca55e55eb066 /usr/lib/.build-id/e7/4ab5829ee8f5b959cd71d47077cb09fb40fb54 /usr/lib/systemd/system/slurmdbd.service /usr/lib64/slurm/accounting_storage_mysql.so /usr/sbin/slurmdbd
I check on my cluster and all this files are present and coming from slurmdbd-23.11.0-1 as you can see from example for this two files:
$ rpm -q --whatprovides /usr/lib/systemd/system/slurmdbd.service slurm-slurmdbd-23.11.0-1.el8.x86_64 $ rpm -q --whatprovides /usr/lib64/slurm/accounting_storage_mysql.so slurm-slurmdbd-23.11.0-1.el8.x86_64
All the other libraries where the symbol 'slurm_conf' is mentioned are from the other packages: slurm-23.02.3-1.el8.x86_64.rpm, slurm-slurmctld-23.02.3-1.el8.x86_64.rpm, slurm-slurmd-23.02.3-1.el8.x86_64.rpm.
How can I solve this problem now?
Many thanks in advance, Miriam
I think installing/upgrading "slurm" rpm will replace this shared lib.
Indeed, as always, test it first at not-so-critical system, use vm snapshots to be able to travel back in time ... as once you'll upgrade DB schema (if part of upgrade) you AFAIK can not go back.
josef
On 28. 02. 24 15:51, Miriam Olmi via slurm-users wrote:
I installed the new version of slurm 23.11.0-1 by rpm. How can I fix this?
-- slurm-users mailing list -- slurm-users@lists.schedmd.com To unsubscribe send an email to slurm-users-leave@lists.schedmd.com