munge fails to install because of failing systemd unit

Bug #1621578 reported by Karl-Philipp Richter
This bug report is a duplicate of:  Bug #1287624: Munged does not start. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
munge (Ubuntu)
New
Undecided
Unassigned

Bug Description

`systemctl status munge.service` doesn't give any further information.

This might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/munge/+bug/1594363 which can be verified after the author changed the title to be in English (as requested in a comment on that report).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: munge 0.5.11-3
Uname: Linux 4.7.2-040702-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 8 20:13:59 2016
InstallationDate: Installed on 2015-12-12 (271 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: munge
UpgradeStatus: Upgraded to xenial on 2016-03-14 (178 days ago)

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
Chris Dunlap (cdunlap) wrote :

Check the output of `journalctl -xe`.

If you see a line with something like

  munged: Error: Logfile is insecure: group-writable permissions set on "/var/log"

then this is another duplicate of #1287624.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.