This bug was fixed in the package munge - 0.5.11-1ubuntu1.1
---
munge (0.5.11-1ubuntu1.1) trusty; urgency=medium
* Fix restrictive checks preventing munged from starting (LP: #1287624)
- d/p/0001-Ignore-group-writable-permissions-on-LogDir.patch:
Ignore group-writable
This bug was fixed in the package munge - 0.5.11-3ubuntu0.1
---
munge (0.5.11-3ubuntu0.1) xenial; urgency=medium
* Fix restrictive checks preventing munged from starting (LP: #1287624)
- d/p/0001-Ignore-group-writable-permissions-on-LogDir.patch:
Ignore group-writable
** 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
I have been trying to run mathematical software and write some mathematical
programs myself, and I was also trying to set up a LAMP server to host my
own website. I am wondering if the other software I installed on this
system required or may require those programs to function, and hence I have
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
Hi Chris,
At the moment slurm, munge, sview are all installed. So the problem I was
encountering seems to be resolved. So thank you. I say seems, only because
I do not know enough to check everything about them. At least I am able to
view the manual pages for those three commands.
I have some
Hi Chris,
Also please forgive my ignorance in this matter. I am also reading the
online pages on munge just right now.
On Thu, Jun 15, 2017 at 12:29 PM, Semih Özlem wrote:
> Hi Chris,
>
> At the moment slurm, munge, sview are all installed. So the problem I was
> encountering
Hello Sami, or anyone else affected,
Accepted munge into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/munge/0.5.11-3ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- [Impact]
- Munge daemon does not start in ubuntu 14.04 beta.
+ Steps to reproduce:
+ ===
+ on 16.04 LTS:
+ $ sudo apt-get install munge
- [Test Case]
- - Install package
- - Try "sudo service munge start"
- - See if service starts or if there is an
Uploaded for processing by the SRU team, thanks!
** Description changed:
+ [Impact]
+ Munge daemon does not start in ubuntu 14.04 beta.
+
+ [Test Case]
+ - Install package
+ - Try "sudo service munge start"
+ - See if service starts or if there is an error
+
+ [Regression Potential]
+ The
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
Can you explain what munge is and what the bug is briefly to someone who
has no idea why that message is coming up?
Thank you
On Tue, Jun 13, 2017 at 8:21 AM, Steve Beattie
wrote:
> And here is a debdiff for xenial. Until I can get these sponsored into
> the respective
And here is a debdiff for xenial. Until I can get these sponsored into
the respective proposed pockets for trusty and xenial, I have built
packages available in my ppa at
https://launchpad.net/~sbeattie/+archive/ubuntu/ppa for people to test.
Thanks again!
** Patch added:
Hi Chris, thanks for creating and identifying the patch. Attached is a
debdiff for trusty
** Patch added: "munge_0.5.11-1ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/munge/+bug/1287624/+attachment/4894935/+files/munge_0.5.11-1ubuntu1.1.debdiff
--
You received this bug
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
The attachment "0001-Ignore-group-writable-permissions-on-LogDir.patch"
seems to be a patch. If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by
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
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
Looks like using the --syslog options also works.
--
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 notifications about this bug go to:
This bug affects me as well on a Ubuntu 14.04.
What is the best workaround here? I see two possibilities:
* changing permission on /var/log to 0755 and ownership from root to syslog user
* adding OPTIONS=--force to /etc/default/munge?
which one is the best?
--
You received this bug
Sorry, I just tried changing the ownershipt of /var/log, and munge is
still complaining:
root@node-09-01-00:~# ls -ld /var/log
drwxr-xr-x 17 syslog root 4096 Sep 21 21:43 /var/log
root@node-09-01-00:~# service munge start
* Starting MUNGE munged
...fail!
munged: Error: Logfile is insecure:
Also doesn't work on the 14.04 release.
--
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 notifications about this bug go to:
It renders essential functionality of the package (or a dependent one)
broken.
** Changed in: munge (Ubuntu)
Importance: Undecided = High
** Changed in: munge (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: munge (Ubuntu)
Status: New = Confirmed
--
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:
27 matches
Mail list logo