Thanks for the suggestion. In my test environment, I'm running :

root@bcm10-h01:~# mysql -V
mysql Ver 8.0.36-0ubuntu0.22.04.1 for Linux on x86_64 ((Ubuntu))

root@bcm10-h01:~# cat /etc/os-release | grep PRETTY
PRETTY_NAME="Ubuntu 22.04.4 LTS"

This closely matches my production environment.

My production environment is running in an Nvidia POD ecosystem and I'm using Base Command Manager (v10) to manage my cluster. It does seem that the version of Slurm in the BCM iso tends to lag behind by at least 12 months. All this is to say updating individual cluster components in the Base Command Environment isn't straightforward.

Best,

Lee

On Thu, Jan 8, 2026 at 2:30 AM Ole Holm Nielsen via slurm-users <slurm-users@lists.schedmd.com> wrote:

Hi Lee,

Just my 2 cents: Which database and OS versions do you run?

Furthermore, Slurm 23.02 is really old, so I'd recommend upgrading to
25.05 (or perhaps even 25.11). It just might be that your bug has been
resolved in later versions of Slurm or MySQL/MariaDB.

You can find detailed upgrade instructions in [1]. Be especially mindful
of the MySQL and slurmdbd upgrades, and perform a dry-run upgrade first on
a test node.

On 1/7/26 13:22, Lee via slurm-users wrote:
> I replicated this issue on a different cluster and determined that the
> root cause is that the time_eligible in the underlying MySQL database gets
> set to 0 when a running job is held. Let me demonstrate.
...
> I am using slurm 23.02.6. I have a strange issue. I periodically use
> sacct to dump job data. I then generate reports based on the resource
> allocation of our users.

IHTH,
Ole

[1]
https://wiki.fysik.dtu.dk/Niflheim_system/Slurm_installation/#upgrading-slurm
--
Ole Holm Nielsen
PhD, Senior HPC Officer
Department of Physics, Technical University of Denmark,

--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-leave@lists.schedmd.com