Hi, I've seen similar behaviour with Slurm 2.3 when client got a corrupted plugin (in my case due to filesystem error /usr/lib64/slurm/auth_munge.so was an empty file)
You may be able to see more details if you start slurmctld in verbose mode with -vvvv -- Nikita Burtsev On Thursday, August 29, 2013 at 1:02 PM, Chauvin Antoine wrote: > Hi, > > I had to reboot my Slurm's servers, and since I'm having a lot's of troubles ! > It seems that there is some communication issues betweens deamons and > servers. > > For the moment i don’t understand anything, but i only manage to make my > installation work with > slurmdbd in my main server > slurmctld in my backup server > > When i'm trying with slurmctld and slurmdbd in my main server they both seems > to be stuck and I can see in my logs: > > Aug 29 11:42:34 slurm1 kernel: slurmctld[2687]: segfault at 1000000042 ip > 0000000000499f99 sp 00007fffffadd650 error 4 in slurmctld[400000+188000] > > Does anyone got something like that ? > > I'm trying to get more information about what's wrong and how I can solve > this situation. > > Thanks > > Antoine >
