** Patch added: "0002-Sharness-Fix-dup-of-failing-check-when-run-by-root.patch"
https://bugs.launchpad.net/ubuntu/+source/munge/+bug/1915457/+attachment/5464022/+files/0002-Sharness-Fix-dup-of-failing-check-when-run-by-root.patch
--
You received this bug notification because you are a member
** Patch added: "0001-Sharness-Add-munged_kill_daemon-and-munged_cleanup.patch"
https://bugs.launchpad.net/ubuntu/+source/munge/+bug/1915457/+attachment/5464021/+files/0001-Sharness-Add-munged_kill_daemon-and-munged_cleanup.patch
--
You received this bug notification because you are a member
** Patch added: "0003-Sharness-Fix-EACCES-failure-succeeding-for-root.patch"
https://bugs.launchpad.net/ubuntu/+source/munge/+bug/1915457/+attachment/5464023/+files/0003-Sharness-Fix-EACCES-failure-succeeding-for-root.patch
--
You received this bug notification because you are a member of
Patches 1-3 are for the sharness test suite and are only needed if
you're running 'make check'. Patch 4 fixes the actual bug. Stack applies
cleanly against 0.5.14. Tested on s390x.
** Patch added: "0004-HKDF-Fix-big-endian-bug-caused-by-size_t-ptr-cast.patch"
Closing this out since it was a support request.
** Changed in: munge (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785169
Title:
je ne peux pas faire des
It's expecting "/" to be owned by root, and yours doesn't appear to be.
You can fix this in one of two ways:
1. Change the ownership of "/" to root (chown root /), or
2. Run munged with the --force option to work-around this problem. With
systemd, you can do this by appending "--force" to the
What is the output from this command?
systemctl status -l munge | grep Error:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785169
Title:
je ne peux pas faire des mises à jour probleme munge
To
The error is shown here:
août 03 06:32:06 127.0.0.1kamal munged[31923]: munged: Error: Logfile is
in..."
It's warning about the logfile (/var/log/munge/munged.log) being
insecure in some manner. The full message is cut off by the ellipse. Use
'systemctl status -l munge' to get the full message.
** Tags removed: verification-needed
** Tags added: verification-done-trusty verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287624
Title:
Munged does not start
To manage
Semih, you can query dependencies and reverse-dependencies with the apt-
cache command:
apt-cache showpkg - displays info about the given package
apt-cache depends - lists each dependency of the given package
apt-cache rdepends - lists each reverse-dependency of the given package
See the
Semih, I'm not sure why slurm/sview/munge would have been installed on
your system. If you're not using them, they're safe to remove.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287624
Title:
I can confirm 0.5.11-1ubuntu1.1 from trusty-proposed and
0.5.11-3ubuntu0.1 from xenial-proposed both resolve this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287624
Title:
Munged does not
Semih, munge is an authentication service oftentimes used in an HPC
cluster environment. It was likely installed as a dependency when you
installed slurm. You're seeing these messages because you submitted Bug
1696002 which was marked as a duplicate of this bug.
--
You received this bug
I can confirm the updated munge packages from your ppa work for both
trusty and xenial. Thanks, Steve!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287624
Title:
Munged does not start
To manage
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
Not related to Debian bug #761651.
DpkgTerminalLog output shows "munged: Error: Logfile is insecure: ...".
This is a duplicate of Bug 1287624 caused by the change in permissions
of /var/log back in 14.04.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Until 0.5.11 is patched, the following steps will work around this
problem.
For 14.04 and 14.10:
1. Add the following line to /etc/default/munge:
OPTIONS="--syslog"
2. sudo /usr/sbin/create-munge-key
3. sudo service munge start
For 15.04, 15.10, and 16.04:
1. sudo systemctl edit
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug is no longer a duplicate of bug 1603205
package munge 0.5.11-3 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
** This bug has been
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1287624 ***
https://bugs.launchpad.net/bugs/1287624
** This bug has been marked a duplicate of bug 1287624
Munged does not start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi. I'm the developer of MUNGE. I keep seeing new bug reports for this
bug appear here in the tracker. The most recent one was yesterday (Bug
1680503).
This particular issue has been reported against Ubuntu 14.04 (this bug
report), Ubuntu 14.10 (Bug 1391175), Ubuntu 15.04 (Bug 1448620), and
This appears to be the same problem described in #1287624.
lekimtek: Until MUNGE gets fixed in 16.04, you can override this error
by starting munged with either the "--force" or "--syslog" command-line
option. Instructions for doing so are given here:
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Instead of using "--force" or "--syslog", I have a patch that fixes this
here:
https://github.com/dun/munge/commit/ec4a2c679d43db5e194434bdc7489e1a92599aa5
This patch is part of the munge-0.5.12 release (in Yakkety), but it also
applies cleanly against 0.5.11 (in Trusty-Xenial) and 0.5.10 (in
I believe Gennaro (Debian maintainer for munge) fixed this in 0.5.8-8.
Can you go with 0.5.8-8 for Hardy?
-Chris
On Fri, 2009-06-05 at 07:58pm -, ward wrote:
This bug is still present in Jaunty.
I've tested markh's patch on hardy, and it works perfectly. Can we have
that fix go in,
37 matches
Mail list logo
