Hello!
I figured it out it, was a disk space issue. I thought I had checked this
already. Please disregard! Thank you!
Best,
Chris
--
Christopher Coffey
High-Performance Computing
Northern Arizona University
928-523-1167
On 2/4/22, 11:41 AM, "slurm-users on behalf of Christopher Benjami
Hello!
I'm trying to test an upgrade of our production slurm db on a test cluster.
Specifically I'm trying to verify a update from 20.11.7 to 21.08.4. I have a
dump of the production db, and imported as normal. Then firing up slurmdbd to
perform the conversion. I've verified everything I can th
On 03-02-2022 21:59, Ryan Novosielski wrote:
On Feb 3, 2022, at 2:55 PM, Ole Holm Nielsen wrote:
On 03-02-2022 16:37, Nathan Smith wrote:
Yes, we are running slurmdbd. We could arrange enough downtime to do an
incremental upgrade of major versions as Brian Andrus suggested, at least on
the s
On 04-02-2022 08:59, Bjørn-Helge Mevik wrote:
Ole Holm Nielsen writes:
As Brian Andrus said, you must upgrade Slurm by at most 2 major
versions, and that includes slurmd's as well! Don't do a "direct
upgrade" of slurmd by more than 2 versions!
That should only be an issue if you have runnin
Ole Holm Nielsen writes:
> As Brian Andrus said, you must upgrade Slurm by at most 2 major
> versions, and that includes slurmd's as well! Don't do a "direct
> upgrade" of slurmd by more than 2 versions!
That should only be an issue if you have running jobs during the
upgrade, shouldn't it? A
