Ok.
You may want to check your slurmdbd host(s) and ensure the users are
known there. If it does not know who a user is, it will not allow access
to the data.
If you are running sssd, clear the cache and such too.
Brian Andrus
On 7/1/2021 1:12 AM, taleinterve...@sjtu.edu.cn wrote:
I can make sure the test job is running (of course in the default time
window) when doing sacct query, and here is the new test record which
describe it more clearly:
[2021-07-01T16:02:42+0800][hpczty@cas013] ~/downloads> sbatch testjob.sh
Submitted batch job 6955371
[2021-07-01T16:02:48+0800][hpczty@cas013] ~/downloads> squeue
JOBID PARTITION NAME USER ST TIME NODES
NODELIST(REASON)
6955371 debug test hpczty R 0:02 1 cas011
[2021-07-01T16:02:50+0800][hpczty@cas013] ~/downloads> sacct
JobID JobName Partition Account AllocCPUS State
ExitCode
------------ ---------- ---------- ---------- ---------- ----------
--------
[2021-07-01T16:02:52+0800][hpczty@cas013] ~/downloads> sacct --state=R
--starttime=2021-07-01T16:00:00 --endtime=now
JobID JobName Partition Account AllocCPUS State
ExitCode
------------ ---------- ---------- ---------- ---------- ----------
--------
[2021-07-01T16:03:25+0800][hpczty@cas013] ~/downloads> squeue
JOBID PARTITION NAME USER ST TIME NODES
NODELIST(REASON)
6955371 debug test hpczty R 0:43 1 cas011
*发件人:*Brian Andrus <toomuc...@gmail.com>
*发送时间:*2021年6月30日22:29
*收件人:*taleinterve...@sjtu.edu.cn
*主题:*Re: [slurm-users] Is there bug in PrivateData=jobs option of
slurmdbd?
I suspect your job fell out of the default time window for sacct.
Add a time window that you know includes when the job ran and you will
likely see it.
Brian Andrus
On 6/30/2021 3:53 AM, taleinterve...@sjtu.edu.cn
<mailto:taleinterve...@sjtu.edu.cn>wrote:
Hello,
We find a strange behavior about sacct and PrivateData option of
slurmdbd. Our original configuration is setting “PrivateData =
accounts,jobs,usage,users,reservations”in slurm.conf and not
setting “PrivateData”in slurmdbd.conf. At this point, common user
can see all others job information with sacct. Now we add option
“PrivateData =jobs”to slurmdbd.conf, then common users even can’t
see their own jobs using sacct.
According.to https://slurm.schedmd.com/slurmdbd.conf.html
<https://slurm.schedmd.com/slurmdbd.conf.html> , setting “jobs”in
PrivateData should only prevent user from viewing others’job. Why
it also hide jobs submit by user itself from sacct query?
The test records as below:
============ before add option “PrivateData =jobs”to slurmdbd.conf
==================
[2021-06-30T18:18:07+0800][hpczty@login3] ~/downloads> sbatch
testjob.sh
Submitted batch job 6944660
[2021-06-30T18:18:11+0800][hpczty@login3] ~/downloads> squeue
JOBID PARTITION NAME USER ST TIME
NODES NODELIST(REASON)
6944660 debug test hpczty PD 0:00 1 (None)
[2021-06-30T18:18:16+0800][hpczty@login3] ~/downloads> sacct
JobID JobName Partition Account AllocCPUS State
ExitCode
------------ ---------- ---------- ---------- ----------
---------- --------
6944660 test debug acct-hpc 1 RUNNING 0:0
6944660.bat+ batch acct-hpc 1
RUNNING 0:0
6944660.ext+ extern acct-hpc 1 RUNNING 0:0
============ after add option “PrivateData =jobs”to slurmdbd.conf
==================
[2021-06-30T18:21:27+0800][hpczty@login3] ~/downloads> sbatch
testjob.sh
Submitted batch job 6944665
[2021-06-30T18:21:30+0800][hpczty@login3] ~/downloads> squeue
JOBID PARTITION NAME USER ST TIME
NODES NODELIST(REASON)
6944665 debug test hpczty PD 0:00 1 (None)
[2021-06-30T18:21:32+0800][hpczty@login3] ~/downloads> sacct
JobID JobName Partition Account AllocCPUS State
ExitCode
------------ ---------- ---------- ---------- ----------
---------- --------
(no jobs shown)
Thanks
