Page 1 of 1

SLURM elapsed time vs. WebMO Job Manager Time

Posted: Wed Jul 21, 2021 5:14 pm
by skirkby
The Time column in the Job Manager is incorrectly reporting the time for multi-day calculations when using SLURM. When the SLURM reported time is days-hours:minutes:seconds and WebMO reports the time as days:minutes:seconds, for example 1-12:34:46 for 1 day, 12 hours, 34 minutes and 46 seconds is reporting as 1:34:36

Re: SLURM elapsed time vs. WebMO Job Manager Time

Posted: Wed Jul 21, 2021 5:31 pm
by schmidt
Thank you for this report. It would be helpful if you could post a screenshot (or better, text snippet) of a bit of SLURM output to use for testing. It obviously takes some time to get a multi-day job running for full testing purposes.

Re: SLURM elapsed time vs. WebMO Job Manager Time

Posted: Mon Nov 28, 2022 3:33 pm
by ssivy
Hello, we are having a similar issue since we update WebMO to version 22.0.009e. When a job is running, the "Time" column in the WebMO job queue page displays 29:00:00, but displays the elapsed time correctly when the job ends. Here is a screenshot.
Screenshot 2022-11-27 at 8.23.18 PM.png
Screenshot 2022-11-27 at 8.23.18 PM.png (271.35 KiB) Viewed 9734 times

Re: SLURM elapsed time vs. WebMO Job Manager Time

Posted: Mon Nov 28, 2022 3:44 pm
by schmidt
Yikes! I just realized that 22.0.009e (enterprise only!) has some left over debugging code that was used to address the earlier issue! I will resolve this later today in a point release (010e) for enterprise only.

Re: SLURM elapsed time vs. WebMO Job Manager Time

Posted: Tue Nov 29, 2022 5:53 pm
by ssivy
Thanks. I'll look for it and schedule a time to install the update after the kids in GenChem are done with it for the semester.

Re: SLURM elapsed time vs. WebMO Job Manager Time

Posted: Fri Dec 02, 2022 3:37 pm
by schmidt
If you want to change it in situ, it is a one line change in processcontrol_pbs.cgi, around line ~140. You can easily see where a value is erroneous hard coded for testing! (Note that you may need to wait until the WebMO queue empties for the daemon to restart and the change to "stick".)