We are planning to upgrade to a newer version of bright which comes with Slurm 16.05.8. We are currently running on slurm 14.11.11 so hopefully the newer version will address this issue as someone mentioned. (I check the configs the users match on both). The one thing that bright support asked me to ask if the upgrade from 14.11.11 to 16.05.8 will break anything like the QoS since apparently the database doesn't get touched during the upgrade.
On Jan 23, 2017, at 5:07 PM, Lachlan Musicman <[email protected]<mailto:[email protected]>> wrote: Do your entries for SlurmUser match in slurm.conf and slurmdbd.conf? (I don't know the cause of your problem, but that's what I'd look at next). Also, does the AccountingStorageUser in slurm.conf match the user in slurmdbd.conf? cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 24 January 2017 at 08:52, Katsnelson, Joe <[email protected]<mailto:[email protected]>> wrote: So I’m associating the user with an account in this case called isg and after I restart slurm they can submit jobs. Below is how the user looks even before I restart slurm sacctmgr show assoc format=account%20,user,cluster,partition where user=testuser Account User Cluster Partition -------------------- ---------- ---------- ---------- isg testuser slurm_clu+ one thing that I did notice when I add the user I see this error in the slurmctld log [2017-01-23T16:47:34.351] error: Update Association request from non-super user uid=450 UID 450 happens to be the slurm user But when I make the changes I’m logged in as root. From: Lachlan Musicman <[email protected]<mailto:[email protected]>> Reply-To: slurm-dev <[email protected]<mailto:[email protected]>> Date: Monday, January 23, 2017 at 4:43 PM To: slurm-dev <[email protected]<mailto:[email protected]>> Subject: [slurm-dev] Re: New User Creation Issue Interesting. To the best of my knowledge, if you are using Accounting, all users actually need to be in an association - ie having a user account is insufficient. An Association is a tuple consisting of: cluster, user, account and (optional) partition. Is that the problem? cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 24 January 2017 at 08:32, Katsnelson, Joe <[email protected]<mailto:[email protected]>> wrote: Hi, I’m having an issue creating new users on our cluster. After running the below commands slurm has to be restarted in order for that user to be able to run sbatch. Otherwise they get an error ( sbatch test-job.sh sbatch: error: Batch job submission failed: Invalid account or account/partition combination specified) sacctmgr create user name=testuser account=isg sacctmgr modify user testuser set qos+=full ------------------------------------------------------------ This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. ================================= ------------------------------------------------------------ This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. ================================= ------------------------------------------------------------ This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. =================================
