Hi,
On Fri, 2025-12-12 at 14:16:25 +0000, Slurm users wrote:
Hi Steffen,
that error is expected with a Slurm 24.11 client talking to a 22.05 controller
that's why I'm looking for some 23.11 which in theory would be inside the compatibility window...
If upgrading the cluster isn�t an option yet, the most practical workaround
is to run matching 22.05.x client tools on the Debian 13 submit node (e.g., build/package Slurm 22.05.8 from source for Trixie
This is where I'm constantly failing, for multiple reasons: the *.so libraries are installed 0555 instead of 0755 which they had been set before, perl versions aren't properly detected (perl/5.40.1 vs perl5/5.40) etc.
, or use a small Bookworm chroot/container with slurm-client)
This indeed might make sense but is too user-unfriendly, I'm afraid.
. In general, I�d expect you�ll need client commands that match the controller�s major version as long as slurmctld stays on 22.05.
For the theory part above, I found some 23.11.4 backport attempt but even that one throws an error "slurm_load_partitions: Unexpected message received" with server- side "Invalid Protocol Version 10240" (the 24.11 one was 10752, btw).
So this makes me believe that the server version must be >= the client one, despite windows usually being transparent from both sides - and I must find a way to build 22.05 slurm-client, slurm-wlm-basic-plugins and slurm-wlm-jwt-plugin packages for Trixie; or have to wait until the controller can be upgraded. (I hope to keep the DB; there's an intermediate 23.11.7-1 build that might still fit trixie for this. That's a different story though.)
Maybe I'd "just" build the binaries within Trixie? (I'm so used to packages, and packaging, but this is a single point of failure...) In theory that should work, and I don't need everything now...
Thanks, S