[slurm-users] Odd sacct behavior?
desantis at usf.edu
Wed May 2 13:08:21 MDT 2018
-----BEGIN PGP SIGNED MESSAGE-----
I'm just wondering if anyone is able to reproduce the behavior I'm
seeing with `sacct`, or if anyone has experienced it previously.
In a nutshell, I usually can query jobs from specified nodes, similar
to the following:
`sacct -o $OPTIONLIST -N nodename -S START -E END -s r`
Up until today, it has never failed and the results are what I expect.
However, I noticed that when I attempted to query a job from ~10 days
ago using the formula above, I get zero output and the following
message in the slurmdbd log:
error: Problem getting jobs for cluster $CLUSTERNAME
Looking through my history, it seems that I've always queried jobs in
an exact fashion, but usually the jobs I'm looking at are less than a
week old, and output is returned.
If I exclude a nodename or nodelist, and keep the start and end times,
I get results, and no error is returned:
`sacct -o $OPTIONLIST -S START -E END -s r`
I was able to query the DB itself and was able to retrieve information,
so it doesn't appear to be an issue with purged records. I also
restarted MySQL and the slurmdbd and didn't see any improvement.
I'm using slurm 16.05.10-2 and slurmdbd 16.05.10-2.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
More information about the slurm-users