[slurm-users] "Low socket*core*thre" - solution?

[Werner Saar]

Hi Mahmood,

I think, the problem was:
the python script 
/opt/rocks/lib/python2.7/site-packages/rocks/commands/sync/slurm/__init__py,
which is called by the command rocks sync slurm
did not restart slurmd on the Head-Node.

After the restart of slurmctld, slurmd on the Head-node had the old 
configuration
and the Head-Node was drained.

I will fix this for the next release

Best regards
Werner




On 05/08/2018 06:02 PM, Mahmood Naderan wrote:
> I think yes!
> But I tried many commands and restarting the services before. At the
> moment I don't know why that happened but the last three commands by
> Werner fixed that. If the state is not persistent after a reboot, I
> have to dig more.
>
>
>
> Regards,
> Mahmood
>
>
>
>
> On Tue, May 8, 2018 at 3:00 AM, Chris Samuel <chris at csamuel.org> wrote:
>> On Tuesday, 8 May 2018 2:27:07 AM AEST Mahmood Naderan wrote:
>>
>>> So the trick was to UNDRAIN the node and not RESUME it.
>> That's strange, because UNDRAIN only does a subset of what RESUME does.
>>
>>     "UNDRAIN"  clears  the  node from  being  drained  (like  "RESUME"),
>>     but will not change the node's base state (e.g. "DOWN").
>>
>> Have you been restarting slurmd after changing the config file in the past?
>>
>> --
>>   Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC
>>
>>