[slurm-users] [External] Re: actual time of start (or finish) of a job

[Davide DelVento]

Thanks for pointing that out. In this case it doesn't matter, but I
can see how in others it may

On Mon, Feb 20, 2023 at 9:44 AM Florian Zillner <fzillner at lenovo.com> wrote:
>
> Hi,
>
> note that times reported by sacct may differ from the net times. For example, imagine a test job like this:
> date
> sleep 1m
> date
>
> sacct reports:
> $ sacct -j 225145 -X -o jobid,start,end
> JobID                      Start                 End
> ------------ ------------------- -------------------
> 225145       2023-02-20T17:31:12 2023-02-20T17:32:30
>
> Whereas:
> cat *out.225145
> Mon Feb 20 17:31:29 CET 2023
> Mon Feb 20 17:32:29 CET 2023
>
> Sometimes these extra few seconds matter. So if you're looking for net runtimes, I'd suggest to ask the user to include a date command here and there in the submit script.
>
> Cheers,
> Florian
> ________________________________
> From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Davide DelVento <davide.quantum at gmail.com>
> Sent: Thursday, 16 February 2023 01:40
> To: Slurm User Community List <slurm-users at lists.schedmd.com>
> Subject: [External] Re: [slurm-users] actual time of start (or finish) of a job
>
> Thanks, that's exactly it.
> I naively assumed that the '-l" in sacct provided "everything" (given
> how long and unwieldy it is, but I noticed now that it isn't).
> Sorry for the noise!
>
> On Wed, Feb 15, 2023 at 5:32 PM Joseph Francisco Guzman
> <Joseph.F.Guzman at nau.edu> wrote:
> >
> > Hi Davide,
> >
> > I would use the Start and End fields with the sacct command. Something like this: "sacct -j jobid1,jobid2 -X -P -o jobid,start,end".
> >
> > Were you able to take a look at the sacct manual page outlines what all of the different fields mean? Here's a link to the web version: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fslurm.schedmd.com%2Fsacct.html&data=05%7C01%7Cfzillner%40lenovo.com%7C15763a6fc38f499923ff08db0fb6a408%7C5c7d0b28bdf8410caa934df372b16203%7C0%7C0%7C638121049348286424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=unxmMQ7DKiu5WGEiAZspSKoHssaaJy3zPvqVzOYDNZM%3D&reserved=0.
> >
> > Best,
> >
> > Joseph
> >
> > --------------------------------------------------------------
> > Joseph F. Guzman - ITS (Advanced Research Computing)
> >
> > Northern Arizona University
> >
> > Joseph.F.Guzman at nau.edu
> >
> > ________________________________
> > From: slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf of Davide DelVento <davide.quantum at gmail.com>
> > Sent: Wednesday, February 15, 2023 5:18 PM
> > To: slurm-users at schedmd.com <slurm-users at schedmd.com>
> > Subject: [slurm-users] actual time of start (or finish) of a job
> >
> > I have a user who needs to find the actual start (or finish) time of a
> > number of jobs.
> > With the elapsed field of sacct start or finish become equivalent for
> > his search.
> >
> > I see that information in /var/log/slurm/slurmctld.log so Slurm should
> > have it, however in sacct itself that information does not seem to
> > exist, and with all the queries we tried Google always thinks we are
> > looking for something else and never returns an actual answer.
> >
> > If this was a one-off I could do it for him, but he needs to script it
> > for his reasons and I don't want to run his script as root nor give
> > him access to the log files forever.
> >
> > Is there a way to find this information?
> >
> > Thanks
> >
>