We use the elasticsearch plugin. This information is kept in there.
From: slurm-users on behalf of Gestió
Servidors
Sent: Thursday, April 30, 2020 3:39:33 AM
To: slurm-users@lists.schedmd.com
Subject: [slurm-users] How to get command from a finished job
Hello,
On 30-04-2020 15:34, Bjørn-Helge Mevik wrote:
Gestió Servidors writes:
For example, with "scontrol show jobid" I can know what command has
been submited, its workir, the stderr file and the stdout one. This
information, I think, cannot be obtained when the job is finished and
I run "sacct".
Gestió Servidors writes:
> For example, with "scontrol show jobid" I can know what command has
> been submited, its workir, the stderr file and the stdout one. This
> information, I think, cannot be obtained when the job is finished and
> I run "sacct".
The workdir is available with sacct, IIRC.
Hi there,
On 4/30/20 2:52 PM, Paul Edmon wrote:
> No, that data is purged from the scheduler after completion. So records of
> the job exist in your job completion log or in the sacct database. The
> script that it ran is not saved, though I believe there are several bug
> requests in to Sche
No, that data is purged from the scheduler after completion. So records
of the job exist in your job completion log or in the sacct database.
The script that it ran is not saved, though I believe there are several
bug requests in to SchedMD to add that feature. People have come up
with vario