The benefits are pretty limited if you don’t have the server upgraded anyway,
unless you’re just saying it’s easier to install a current client.
--
#BlackLivesMatter
|| \\UTGERS, |---*O*---
||_// the State | Ryan Novosielski - novo
On 6/17/24 7:24 am, Bjørn-Helge Mevik via slurm-users wrote:
Also, server must be newer than client.
This is the major issue for the OP - the version rule is:
slurmdbd >= slurmctld >= slurmd and clients
and no more than the permitted skew in versions.
Plus, of course, you have to deal with
On 6/17/24 17:56, stth via slurm-users wrote:
Hello,
I wanted help with a problem I have. I just updated my operation system
and the slurmdbd and slurmctld is not working anymore. I get this Errors:
slurmdbd: fatal: Database schema is too old for this version of Slurm to
upgrade.
slurmctld:
When you updated your operating system, you likely updated the version of slurm
you were using too (assuming slurm had been installed from system repos instead
of built source code). Slurm only supports db and state files that are within
2 major versions older than itself.
The fix is to uninst
Hello,
I wanted help with a problem I have. I just updated my operation system and
the slurmdbd and slurmctld is not working anymore. I get this Errors:
slurmdbd: fatal: Database schema is too old for this version of Slurm to
upgrade.
slurmctld: fatal: Can not recover last_tres state, incompatibl
> Could you post that snippet?
function slurm_job_submit ( job_desc, part_list, submit_uid )
if job_desc.features then
if not string.find(job_desc.features,"el9") then
job_desc.features = job_desc.features .. '¢os79'
end
else
job_desc.features = "centos79"
end
return slur
Could you post that snippet?
> On Jun 14, 2024, at 14:33, Laura Hild via slurm-users
> wrote:
>
> I wrote a job_submit.lua also. It would append "¢os79" to the feature
> string unless the features already contained "el9," or if empty, set the
> features string to "centos79" without the ampe
This functionality in slurmd was added in August 2023, so not in the version
we’re currently running:
https://github.com/SchedMD/slurm/commit/0daa1fda97c125c0b1c48cbdcdeaf1382ed71c4f
Perhaps something for the future. Currently looking like the job_submit.lua is
the best candidate.
Paul Edmon via slurm-users writes:
> https://slurm.schedmd.com/upgrades.html#compatibility_window
>
> Looks like no. You have to be with in 2 major releases.
Also, server must be newer than client.
--
B/H
signature.asc
Description: PGP signature
--
slurm-users mailing list -- slurm-users@l
https://slurm.schedmd.com/upgrades.html#compatibility_window
Looks like no. You have to be with in 2 major releases.
-Paul Edmon-
On 6/17/24 5:40 AM, ivgeokig via slurm-users wrote:
Hello!
I have a question. I have the server 19.05.3. No chance to upgrade
it. Have I any chance to conn
Recent compiler-hardening efforts broke slurms way of loading plugins.
As a workaround, link slurm with -Wl,-z,lazy
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
Thanks, this fixed issue for me.
Regards,
Rafał
The online configurator for JobAcctGatherType set to anything that none,
generates config file with a such entry:
#JobAcctGatherTypejobacct_gather/cgroup=
or
#JobAcctGatherTypejobacct_gather/linux=
Regards,
Rafał
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe sen
Hello!
I have a question. I have the server 19.05.3. No chance to upgrade it.
Have I any chance to connect new client 22.05.11?
Here is log from server:
[2024-06-14T15:20:40.345] debug: Unsupported RPC version 9728 msg type 0(0)
[2024-06-14T15:20:40.345] error: g_slurm_au
13 matches
Mail list logo
