Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 624962 - sys-auth/munge-0.5.12 munged cannot be started
Summary: sys-auth/munge-0.5.12 munged cannot be started
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Cluster Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-14 09:19 UTC by Michelangelo Scopelliti
Modified: 2018-11-10 13:25 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
corrected init script (munged,1.12 KB, text/plain)
2018-09-17 06:43 UTC, Maurice Volaski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michelangelo Scopelliti 2017-07-14 09:19:08 UTC
As a consequence of bug #602596 fix, current munge daemon is not able to start. See comment #9 and comment #10.

Message:

# /etc/init.d/munged start
 * Starting munged ...
 * /etc/munge/munge.key: correcting mode
 * /etc/munge/munge.key: correcting owner
munged: Error: Keyfile is insecure: "/etc/munge/munge.key" should be owned by UID 103
 * start-stop-daemon: failed to start `/usr/sbin/munged'                  [ !! ]
 * ERROR: munged failed to start


In my opinion it's a problem; what am I missing?
Comment 1 Jonas Stein gentoo-dev 2017-07-22 12:25:00 UTC
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

The maintainer will look at this soon, you can collect more information on our support channels in the meantime [1-4]

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/
Comment 2 silver_ghost 2018-05-30 12:26:12 UTC
I have the same problem with sys-auth/munge-0.5.10-r2.

# /etc/init.d/munged start
 * Starting munged ...
munged: Error: Keyfile is insecure: "/etc/munge/munge.key" should be owned by uid=110
 * start-stop-daemon: failed to start `/usr/sbin/munged'                                                                                                           [ !! ]
 * ERROR: munged failed to start

This line in function start changes ownership every time:

checkpath -f -m 640 -o root:munge "${KEYFILE}"
Comment 3 Maurice Volaski 2018-09-17 06:43:08 UTC
Created attachment 547068 [details]
corrected init script
Comment 4 Larry the Git Cow gentoo-dev 2018-11-10 13:25:41 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=00465fcf6c74c73407d7247a915354fd7c0d8cf6

commit 00465fcf6c74c73407d7247a915354fd7c0d8cf6
Author:     Justin Lecher <jlec@gentoo.org>
AuthorDate: 2018-11-10 12:04:54 +0000
Commit:     Justin Lecher <jlec@gentoo.org>
CommitDate: 2018-11-10 13:25:36 +0000

    sys-auth/munge: Fix munge.key permission problems
    
    Closes: https://bugs.gentoo.org/624962
    Signed-off-by: Justin Lecher <jlec@gentoo.org>
    Package-Manager: Portage-2.3.51, Repoman-2.3.11

 sys-auth/munge/files/munged.initd     |  4 +-
 sys-auth/munge/munge-0.5.13-r1.ebuild | 69 +++++++++++++++++++++++++++++++++++
 2 files changed, 71 insertions(+), 2 deletions(-)