Cannot start Munge: Logfile is insecure: invalid ownership of "/"

[GoogleCodeExporter]

Hi

I was using Munge for my minicluster consisting of one head and 8 nodes. It was working fine with 3 nodes. then the other ones arrived and I have set them up.

Now i wanted to check if SLURM is working properly on all nodes. but somehow I cannot start MUNGE

 * Starting MUNGE munged                                                                                           [fail] 
munged: Error: Logfile is insecure: invalid ownership of "/"

when i change the log file chown to root it tells me it should be owned by uid=120, ok so changed it back with chown munge munge.log

I don't know what happened so that munge won't run, nothing munge relative has been changes.

log file is empty

Thanks in advance

Original issue reported on code.google.com by radtke.mathias@googlemail.com on 14 Apr 2014 at 9:11

[GoogleCodeExporter]

here some additional infos from the last munge.log

2014-04-10 23:53:48 Notice:    Running on "octopus" (192.168.0.1)
2014-04-10 23:53:48 Warning:   Pidfile is insecure: invalid ownership of "/run/munge"
2014-04-10 23:53:48 Warning:   Ignoring PRNG seed "/var/lib/munge/munge.seed": not owned by uid=0
2014-04-10 23:53:48 Warning:   PRNG seed dir is insecure: invalid ownership of "/var/lib/munge"
2014-04-10 23:53:48 Info:      Removed insecure PRNG seed "/var/lib/munge/munge.seed"
2014-04-10 23:53:48 Info:      PRNG seeded with 1024 bytes from "/dev/urandom"
2014-04-10 23:53:48 Warning:   Keyfile is insecure: "/etc/munge/munge.key" should be owned by uid=0
2014-04-10 23:53:48 Warning:   Keyfile is insecure: invalid ownership of "/etc/munge"
2014-04-10 23:53:48 Info:      Updating supplementary group mapping every 3600 seconds
2014-04-10 23:53:48 Info:      Enabled supplementary group mtime check of "/etc/group"
2014-04-10 23:53:48 Warning:   Socket is insecure: invalid ownership of "/run/munge"
2014-04-10 23:53:48 Notice:    Starting munge-0.5.10 daemon (pid 8561)
2014-04-10 23:53:48 Info:      Created 2 work threads
2014-04-10 23:53:48 Info:      Found 2 users with supplementary groups in 0.007 seconds
2014-04-11 07:45:39 Notice:    Exiting on signal=15
2014-04-11 07:45:39 Info:      Wrote 1024 bytes to PRNG seed "/var/lib/munge/munge.seed"
2014-04-11 07:45:39 Notice:    Stopping munge-0.5.10 daemon (pid 8561)

Original comment by radtke.mathias@googlemail.com on 14 Apr 2014 at 9:13

[GoogleCodeExporter]

FIXED

Don't know what the hell happened but various programs setted themselves as owner of "/"

did a chown root / on all nodes and now munge and slurm are running fine.

please close the issue

Original comment by radtke.mathias@googlemail.com on 14 Apr 2014 at 12:52

[GoogleCodeExporter]

When munged is started, it performs a series of checks on its directories (/etc/munge, /var/lib/munge, /var/log/munge, /var/run/munge) and all of their parent directories all the way up to the root directory. These directories must exist, they must be owned by either root or the effective uid, and they cannot allow write by group or other.

It looks like you were initially running munged as uid 120 which is fine as long as the above directories are owned by that uid. When you later ran munged as uid 0, it warned of files and directories being owned by someone else. But it looks like your initial problem was with the root directory getting owned by someone other than root.

Original comment by chris.m.dunlap on 14 Apr 2014 at 10:18

• Changed state: Done
• Added labels: Type-Support
• Removed labels: Type-Defect