All,
I have a relatively successful cloud implementation of SLUM in Azure.
I am experiencing an issue with the ResumeProgram not running.
Thing work great but after a bit, it just plain stops calling the script. I
have enabled debug on slurmctld and I see the jobs being assigned nodes
that are
Hi Ole,
in fact, the user does not become deleted but gets a "deleted" flag in
the database.
The advantage is, if you recreate the user, he gets the same internal id.
@Mahmood
if you REALLY want to get rid of that user, you might need to manipulate
the SQL Database. I emphasize though, not
sacctmgr delete user XXX
I would also like to mention my Slurm account and user updating tools:
https://github.com/OleHolmNielsen/Slurm_tools/tree/master/slurmaccounts
/Ole
On 10/10/19 1:41 PM, Mahmood Naderan wrote:
Hi
I had created multiple test users, and then removed them.
However, I see
Hi
I had created multiple test users, and then removed them.
However, I see they are still present in slurm database. How can I remove
them?
# sacctmgr list association format=account,user
Account User
-- --
root
root root
local
local
Matthew BETTINGER writes:
> Just curious if this option or oom setting (which we use) can leave
> the nodes in CG "completing" state.
I don't think so. As far as I know, jobs go into completing state when
Slurm is cancelling them or when they exit on their own, and stays in
that state until
