[slurm-users] Slurm 20.02 Dry-Run DB upgrade - Question on the cloned DB

Brian Andrus toomuchit at gmail.com
Mon Feb 7 17:06:50 UTC 2022

Odd. I would bet you haven't fully isolated that node that you put the 
db clone on.

If you shut down slurmdbd on the cloned db node does sshare still show 
dummy user from the head node?

A few things you could check:
You needed to make those changes for the slurm.conf and slurmdbd.conf 
after shutting down slurmd.

You should not have anything listed as backuphost for anything on the 
cloned db node.

It should only have 'localhost' for the SlurmtctldHost and 
AccountingStorageHost (slurm.conf) and DbdHost (slurmdbd.conf)

Brian Andrus

On 2/7/2022 8:51 AM, Moshe Mergy wrote:
> Yes Brian,
> sshare performed on the head node or on ANY other nodes, shows the 
> dummy user created on the node with the cloned DB
> I wanted to test the (cloned) DB upgrade in advance, and the real 
> DB upgrade a few weeks later (after the users deadlines)
> Moshe
> ------------------------------------------------------------------------
> *From:* slurm-users <slurm-users-bounces at lists.schedmd.com> on behalf 
> of Brian Andrus
> *Subject:* Re: [slurm-users] Slurm 20.02 Dry-Run DB upgrade - Question 
> on the cloned DB
> So if you run sshare on the head node, it shows your dummy user?
> At any rate, just do a db dump (also known as a backup) and you can 
> restore that if you have an issue of any sort.
> Brian Andrus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20220207/25c30ba8/attachment.htm>

More information about the slurm-users mailing list