The DB itself is on the same machine as the CTLD, so it should be blocking.
I will amp up the debug and see what I find.
-Paul Edmon-
On 3/20/2014 4:26 PM, Danny Auble wrote:
Paul I would check your slurmdbd log about not being able to talk to
your slurmctld on the cluster.
What you describe should work just fine.
It sounds like the modification didn't make it over. If you have
iptables blocking things make sure the ports to your slurmctld are
open from the slurmdbd host.
On success you will see "debug" level messages in your slurmctld log
about the associations being added/removed...
slurmctld: debug: updating assoc 4
slurmctld: debug: updating assoc 2
Danny
On 03/20/14 12:40, Paul Edmon wrote:
So lets say I have a user named guy in account group_1. I want to
move him to group_2 and remove him from group_1. If I do the following:
sacctmgr add user name=guy account=group_2
sacctmgr delete user name=guy account=group_1
It updates the association in the DB. However, when I then submit a
job it complains saying that the user is not properly associated namely:
_job_create: invalid account or partition for user 56483, account
'group_1', and partition 'interact'
That uid would be the users id. It looks like the CTLD or something
holds on to a cache that has not been updated. I did a scontrol
reconfigure but that didn't help. Only a full slurm restart fixed it.
So is this a known feature? Is there a way to force it to update its
cache with out a full restart? I would hate to have to restart after
every time I did this.
-Paul Edmon-
