That's good to hear. I had the same issue a few years ago, also with Slurm 19,
and that was the advice the Slurm support staff gave me.
I do recommend upgrading your Slurm though. sreport is much faster in later
Slurm versions.
Sean
From: mshubham
Sent: Thu
Hi Sean,
After changing those values yesterday, it worked today after the data got
rebuild, i can see the sreport working now.
Thank you all so much for your help in solving this issue.
On October 20, 2021 at 6:38 PM mshubham wrote:
> Hi Sean,
> Yes, i have changed those values to that time.
Hi Sean,
Yes, i have changed those values to that time. After restarting slurmdbd,
timestamp changed again to today's date but sreport still not showing data for a
year.
On October 19, 2021 at 10:55 AM Sean Crosby wrote:
> Did you change those values to a timestamp before May 2020 like I sugges
Did you change those values to a timestamp before May 2020 like I suggested? If
you do that, then Slurm will regenerate the data needed for sreport to work
properly.
Sean
From: mshubham
Sent: Tuesday, 19 October 2021 16:20
To: slurm-users@lists.schedmd.com ; Sea
Dear All,
By checking the value of last ran table, hourly rollup shows today's date.
+---+--++-
| hourly_rollup | daily_rollup | monthly_rollup|
+---+--++-
|1634617800 | 1634581800
sreport keeps a track of when it has done the last rollup calculations in the
database.
Open MySQL for your Slurm accounting database, do
select * from slurm_acct_db.clustername_last_ran_table;
where slurm_acct_db is your accounting database name (slurm_acct_db is
default), and clustername is
