Comment 23 for bug 1287624

Revision history for this message
Semih Ozlem (semozl) wrote : Re: [Bug 1287624] Please test proposed package

I will try again, but I am also working on something else as well. Also my
machine's memory is full, so I may have to do some backing up and trying to
free some memory.

On Thu, Jun 15, 2017 at 9:32 PM, Semih Özlem <email address hidden> wrote:

> Hi Chris,
>
> I tried. The programs munge, slurm and sview were installed but munge was
> still giving errors, so I removed the programs.
>
> Semih
>
> On Thu, Jun 15, 2017 at 12:41 AM, Chris J Arges <
> <email address hidden>> wrote:
>
>> Hello Sami, or anyone else affected,
>>
>> Accepted munge into trusty-proposed. The package will build now and be
>> available at
>> https://launchpad.net/ubuntu/+source/munge/0.5.11-1ubuntu1.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!
>>
>> --
>> 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
>>
>
>