Nothing in the slurmdbd.log at all, but I don't have any debug logging
turned on either.




On Fri, Mar 8, 2013 at 2:41 PM, Danny Auble <[email protected]> wrote:

>  I would be interested if there were any errors logged in the slurmdbd log.
>
> On 03/08/13 02:29, Chris Read wrote:
>
> Managed to get it working by first restarting slurmdbd, then restarting
> slurmctld
>
>  Now changing QOS on the fly is working as expected.
>
>
>
> On Thu, Mar 7, 2013 at 5:32 PM, Chris Read 
> <[email protected]<http://lists.schedmd.com/cgi-bin/dada/mail.cgi/r/slurmdev/778145652532/>
> > wrote:
>
>> Greetings all...
>>
>>  Running Slurm 2.5.1, just given a user access to a specific QOS level,
>> but when they try use it they get:
>>
>>  Unable to allocate resources: Job has invalid qos
>>
>>  Both the user and the QOS have been around for a while, created when we
>> were running slurm 2.3.x
>>
>>  sacctmgr shows the user has the qos level when we run sacctmgr list
>> assoc
>>
>>  Users that were given that QOS level when we were running 2.3.x and
>> 2.4.x are running fine, it just appears that when we make the change with
>> 2.5.x it does not seem to stick.
>>
>>  Any ideas?
>>
>>  Chris
>>
>
>
>

Reply via email to