I've used sacct to check project job usage at times, but I've found something I don't understand.
$ sacct -X -a --format account,user,cputimeraw,start,end,state -j 10058107 Account User CPUTimeRAW Start End State ---------- --------- ---------- ------------------- ------------------- ---------- mscfops skouson 12048 2015-09-15T12:33:17 2015-09-15T12:45:50 COMPLETED This job completed several days ago, so I expected that it wouldn't show up if I limited the time scope to after the job had completed. For some reason, this job and a few others that ran days or weeks ago show up when I tried to limit the time period to this morning. $ sacct -T -X -a --format account,user,cputimeraw,start,end,state -S 2015-10-01T00:05:00 -E 2015-10-01T07:33:00 -j 10058107 Account User CPUTimeRAW Start End State ---------- --------- ---------- ------------------- ------------------- ---------- mscfops skouson 430080 2015-10-01T00:05:00 2015-10-01T07:33:00 RUNNING Any ideas what's different about these jobs that makes them show up in this time period too? I'd think the state would still be "COMPLETED" since it completed days ago. Why does it think it's still running? BTW I'm still running SLURM 14.11.5 ----- Gary Skouson
