For my cluster (on slurm-wlm 21.08.5), all my jobs have "account": null and "user": null in sacct --json.
I think this is causing the job history tab of Slurm Commander to be empty; it says it is List of jobs from all user associated accounts, but since the cluster doesn't seem to have accounts or cluster-level users set up, I guess it can't find the old jobs when it goes looking for them.
I can use sacct to list old jobs, and scom is able to populate the "Job Queue" tab with queued, running, and recently finished jobs, but a while after jobs finish they age out of the "Job Queue" tab and don't appear in the "Job History" tab.
Can you make Slurm Commander deal with there not being any accounts (or any cluster-level users), and still populate the "Job History" tab?
I got our admin to create a default account for jobs to be in, and that fixed the empty "Job History" tab. So I think a lack of any defined accounts is indeed the way to reproduce this.
For my cluster (on
slurm-wlm 21.08.5
), all my jobs have"account": null
and"user": null
insacct --json
.I think this is causing the job history tab of Slurm Commander to be empty; it says it is
List of jobs from all user associated accounts
, but since the cluster doesn't seem to have accounts or cluster-level users set up, I guess it can't find the old jobs when it goes looking for them.I can use
sacct
to list old jobs, andscom
is able to populate the "Job Queue" tab with queued, running, and recently finished jobs, but a while after jobs finish they age out of the "Job Queue" tab and don't appear in the "Job History" tab.Can you make Slurm Commander deal with there not being any accounts (or any cluster-level users), and still populate the "Job History" tab?