Think of it this way: scontrol is to control the behavior of the cluster
now(ish). Once jobs are done, they can't really be controlled any more,
so you use sacct to look back at their history. That's a logical way of
thinking about it.
Architecturally, I assume it's because scontrol gets it's
Hi,
After reconfiguring slurm.conf to add script into the database, I have tried
with a "normal" user to get that information (from a owned finished job).
However, when I run "sacct - -B -j 92656", I get:
sacct: Jobs Eligible in the time window from Epoch 0 to Wed Jun 18 15:33:03 2025
sacc
De:
Guillaume COCHARD
Enviat: dimecres, 18 de juny de 2025 10:45
Per a: Gestió Servidors
A/c: slurm-users@lists.schedmd.com
Tema: Re: [slurm-users] Re: Job info
s pointed out
by Eric in his response.
Cheers,
Guillaume
*De: *"Gestió Servidors via slurm-users"
*À: *slurm-users@lists.schedmd.com
*Envoyé: *Mercredi 18 Juin 2025 10:22:15
*Objet: *[slurm-users] Re: Job information if job is completed
He
present que no teniu autorització per fer-ne cap ús.
Abans d'imprimir aquest missatge penseu en el medi ambient.
De: Guillaume COCHARD
Enviat: dimecres, 18 de juny de 2025 10:45
Per a: Gestió Servidors
A/c: slurm-users@lists.schedmd.com
Tema: Re: [slurm-users] Re: Job information if j
10:22:15
Objet: [slurm-users] Re: Job information if job is completed
Hello,
So if there is no way to get all information from a finished job (specially
submit script, not command line, but all content from submit script, like a
copy of it), maybe a solution would be run a “prolog” script in
Hello,
So if there is no way to get all information from a finished job (specially
submit script, not command line, but all content from submit script, like a
copy of it), maybe a solution would be run a "prolog" script in each job to run
a "cp" from the submit script. However, how could I copy
My understand from talking with the Slurm devs is that the reason why
the scontrol and sacct are different formats goes back to the origins of
those two commands in the misty past. Basically they were written by two
different devs looking at two different things in different ways as one
is quer
We developed a script "showjob" which will obtain all interesting
information from Slurm for jobs that are pending, running, or completed.
You may try this tool:
https://github.com/OleHolmNielsen/Slurm_tools/blob/master/jobs/showjob
Best regards,
Ole
On 6/17/25 13:42, Davide DelVento via slur
Yeah, that's an annoying thing which I have not understood why has been
designed that way. The information is there and it can be queried, just
with a different command and spitting it out in a different format. The
syntax is
sacct -j XXX
which gives you only some fields, or
sacct -o fields,you
Hi Gestió,
you can try `sacct -B -j YOUR_JOB_ID` to get the submit script, and
`sacct --env-vars -j YOUR_JOB_ID` for the environment.
You need to have set `AccountingStoreFlags:
job_comment,job_env,job_extra,job_script` in slurm.conf to store
respective data.
Otherwise it will not be availabl
11 matches
Mail list logo
