Comment 20 for bug 1287624

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 questions: I gather that munge has something to do with HPCC
high performance computing clusters. I am working with a laptop, and have
not been using a computing cluster, at least to my knowledge. In that case
why would slurm or munge or sview be installed on my system and what other
programs depend on it? Is a multi core machine capable of emulating an
HPCC, or would it use resources of an HPCC by connecting over internet?

I am also wondering if there are some tests I could run to check whether
all those three commands are functioning as they should?

The other question I have is to do with this, I am working on my own on
learning about open source software and ubuntu, reading things written
online, and I would like to continue to do so, and might be interested in
getting to know other people and even trying to involve other people.
However I am not working under any company. I am a graduate student. I am
interested in finding employment as well as continuing being involved with
open source, linux, possibly ubuntu. Who should I contact or get in touch
with? Do you work for ubuntu? How did you start? How can I get involved?

Semih

On Thu, Jun 15, 2017 at 12:40 AM, Chris J Arges <email address hidden>
wrote:

> 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
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
> enable and use -proposed. Your feedback will aid us getting this update
> out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, and change the tag
> from verification-needed to verification-done. If it does not fix the
> bug for you, please add a comment stating that, and change the tag to
> verification-failed. In either case, details of your testing will help
> us make a better decision.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance!
>
> ** Changed in: munge (Ubuntu Xenial)
> Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed
>
> ** Changed in: munge (Ubuntu Trusty)
> Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1696002).
> https://bugs.launchpad.net/bugs/1287624
>
> Title:
> Munged does not start
>
> Status in munge package in Ubuntu:
> Fix Released
> Status in munge source package in Trusty:
> Fix Committed
> Status in munge source package in Xenial:
> Fix Committed
>
> Bug description:
> Steps to reproduce:
> ===================
> on 16.04 LTS:
> $ sudo apt-get install munge
>
> (without the fix, the install fails because it attempts to start the
> service in the package's postinst.)
>
> on 14.04 LTS
> $ sudo apt-get install munge
> $ sudo /usr/sbin/create-munge-key
> $ sudo service restart munge
>
> (the service restart will fail if unfixed)
>
> Regression Potential
> ====================
> Patch is from the upstream author of munge, regressions introduced by
> the patch itself would have been seen there. Test packages were confirmed
> to address the issue.
>
> Original bug report
> ===================
> Munge daemon does not start in ubuntu 14.04 beta.
>
> sudo service munge start
> * Starting MUNGE munged
> [fail]
> munged: Error: Logfile is insecure: group-writable permissions set on
> "/var/log"
>
> /var/log permissions are (I have not changed them in any way):
> drwxrwxr-x 13 root syslog 4,0K maali 4 06:40 log
>
> However, I can start munge manually by running "sudo munged -f", which
> runs the daemon despite warnings.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 14.04
> Package: munge 0.5.11-1ubuntu1
> ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
> Uname: Linux 3.13.0-8-generic x86_64
> ApportVersion: 2.13.2-0ubuntu5
> Architecture: amd64
> Date: Tue Mar 4 11:30:24 2014
> InstallationDate: Installed on 2014-02-26 (5 days ago)
> InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64
> (20140219)
> SourcePackage: munge
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/munge/+bug/
> 1287624/+subscriptions
>