Lucas,

You may need to make sure that iptables is not interfering with communications. 
 Also, make sure that the user that slurmdbd is using is created within mysql, 
and that the user has the ability to create databases and tables within mysql.  
 A good test is to attempt to log in to mysql with the configured username and 
password.  If that works correctly, then look at the port assignments and make 
sure that no one else has grabbed the sockets.

Hope this helps.

Good hunting,
kevin

From: Lucas St [mailto:[email protected]]
Sent: Friday, April 25, 2014 9:12 AM
To: slurm-dev
Subject: [slurm-dev] slurmdbd is not initializing

Hi Forum
Im trying to install slurm to make some test in my lab, but have not been 
possible.
I have a newly installed centos 6.5 with munge, mysql and slurm-14.0
Munge have been installed and I have the /etc/munge/munge.key file.
Other configurations have been applied (create slurm user, modifiy the 
slurm.conf and slurdbd.conf)

but,
When I try to execute the daemon, in this way
             /usr/local/sbin/slurmdbd &

the daemon finishes instantly with
             [1]+  Exit 1                  /usr/local/sbin/slurmdbd
this is the content of the slurmdbd.log file

[2014-04-25T14:54:27.848] error: Couldn't find the specified plugin name for 
auth/munge looking at all files
[2014-04-25T14:54:27.849] error: cannot find auth plugin for auth/munge
[2014-04-25T14:54:27.849] error: cannot create auth context for auth/munge
[2014-04-25T14:54:27.849] fatal: Unable to initialize auth/munge authentication 
plugin

I dont know why im getting this error, because the munge daemon is running
             service munge status
                           munged (pid 1702) is running...
             munge -n
                           
MUNGE:AwQDAAD6Z4axN/10OOBNmEUpT4hJ2WaiJhUquAV2Jh8Y...........

             munge -n | unmunge
                           STATUS:           Success (0)
                           ENCODE_HOST:      master (127.0.0.1)
                           ENCODE_TIME:      2014-04-25 15:08:34 (1398431314)
                           DECODE_TIME:      2014-04-25 15:08:34 (1398431314)
                           TTL:              300
                           CIPHER:           aes128 (4)
                           MAC:              sha1 (3)
                           ZIP:              none (0)
                           UID:              root (0)
                           GID:              root (0)
                           LENGTH:           0
Can somebody tell me what I have to do to solve this problem?
Thanks in advance

Reply via email to