Copied to gutsy-updates.
** Changed in: logcheck (Ubuntu Gutsy)
Status: Fix Committed => Fix Released
--
logcheck fails when auth.log.1.gz missing
https://bugs.launchpad.net/bugs/149641
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
Verification done after following the test case:
a- after following the steps 1 to 3 from the test case: a "No such file or
directory" error is thrown.
b- after following the steps 4 to 5 from the test case: no error is thrown,
according to this the bug is fixed, thanks.
** Tags added: verifica
** Description changed:
Binary package hint: logcheck
Problem
===
Stock logcheck 1.2.61 under Mythbuntu (Gutsy) fails with a misleading error
message when /var/log/auth.log.1.gz does not exist.
Failure email (misleading):
- cut here -
Subject: Logcheck: 2007-10-05
This looks good for me as an SRU. It is a regression, and logcheck is
sensitive infrastructure which should not just break.
Upload sponsored and accepted into gutsy-proposed. Please update the
description to include the test case, as described on the recently
updated https://wiki.ubuntu.com/Stable
Guys, just to remember that logcheck is part of main, and is completely
broken, this goes against ubuntu policies, this update is a must...
--
logcheck fails when auth.log.1.gz missing
https://bugs.launchpad.net/bugs/149641
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: logcheck (Ubuntu Gutsy)
Status: In Progress => Fix Committed
** Changed in: logcheck (Ubuntu Gutsy)
Assignee: dAniel hAhler (blueyed) => (unassigned)
** Changed in: logcheck (Ubuntu Gutsy)
Status: Fix Committed => Confirmed
--
logcheck fails when auth.log.1.gz
** Changed in: logcheck (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: logcheck (Ubuntu Gutsy)
Assignee: (unassigned) => dAniel hAhler (blueyed)
Status: New => In Progress
--
logcheck fails when auth.log.1.gz missing
https://bugs.launchpad.net/bugs/149641
You re
Although it's fixed for hardy, I'm setting this back to "Fix committed",
so the bug shows up for ubuntu-sru.. :/
** Changed in: logcheck (Ubuntu)
Status: Fix Released => Fix Committed
--
logcheck fails when auth.log.1.gz missing
https://bugs.launchpad.net/bugs/149641
You received this bug
dAniel hAhler wrote:
> I've tried several times already to have someone confirm the nomination for
> Gutsy.
What is required for that? Is that something we can do?
--
logcheck fails when auth.log.1.gz missing
https://bugs.launchpad.net/bugs/149641
You received this bug notification because you
I've tried several times already to have someone confirm the nomination for
Gutsy.
There's a patch which fixes this. You can get a version with the patch applied
from my PPA
(http://launchpadlibrarian.net/10148072/logcheck_1.2.61ubuntu0.1~ppa1_all.deb).
The bug is not present in Ubuntu Dapper (l
I just did a fresh install of Gutsy and logcheck is completely broken. How
could it be worse if the patch was applied?
Reading this bug report, it is not clear what needs to be done from an end-user
point of view between the patch coming from Debian and the comments from Ariel.
I vote for the fix
How big a deal is it to fix for Gutsy? On one hand, someone using
logcheck is arguably more likely to check for bugs and/or just figure it
out. OTOH, some might give up, and it's something that doesn't Just
Work. :-(
Unless the LoE is large, I'd vote to fix it for Gutsy.
--
logcheck fails when
This bug should be fixed in Hardy.
I'm not sure if this is important enough for a Gutsy-SRU. Please let me
know: the patch is available above.
** Changed in: logcheck (Ubuntu)
Status: Confirmed => Fix Released
--
logcheck fails when auth.log.1.gz missing
https://bugs.launchpad.net/bugs/1
Apologies, but I have to correct/improve myself on the previous comment.
I have a feeling I was running an older version of logcheck.
If I run logcheck from cron with full path (certainly the ubuntu
version) like this:
sudo -u logcheck /usr/sbin/logcheck -op
(given that I add /usr
Note that fixing this bug is a necessary, but not a sufficient condition
to make logcheck work on gutsy.
After fixing this manually, I still get one more failure later from logtail:
File /var/log/syslog.offset cannot be created. Check your permissions:
Permission denied
To solve this prob
I can (not surprisingly) confirm this bug on Ubuntu Gutsy as well.
A quick work around is to run:
# touch /var/log/auth.log.1.gz
Thanks for your bug-report, I would not had a clue otherwise, really
misleading. Especially because because logcheck always worked before my
clean install...
--
logc
** Changed in: logcheck (Debian)
Status: Unknown => Fix Released
--
logcheck fails when auth.log.1.gz missing
https://bugs.launchpad.net/bugs/149641
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
Updated changelog, because bug 153447 appears to be a duplicate. The
dependency fix seems sensible though.
** Attachment added: "debdiff for gutsy-proposed"
http://launchpadlibrarian.net/10066643/logcheck_1.2.61ubuntu0.1.dsc.diff
** Attachment removed: "debdiff for gutsy-proposed"
http://laun
This debdiffs picks the fix for this bug and bug 153447 from version 1.2.62 in
Debian unstable.
These bugs should get fixed in Hardy by syncing.
** Changed in: logcheck (Ubuntu)
Assignee: dAniel hAhler (blueyed) => (unassigned)
Status: In Progress => Confirmed
** Attachment added: "d
** Bug watch added: Debian Bug tracker #441388
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441388
** Also affects: logcheck (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441388
Importance: Unknown
Status: Unknown
** Changed in: logcheck (Ubuntu)
Assignee:
Yeah, I checked that. That was not the problem for me. My problem is
as outlined above in "Steps to Reproduce." If "/var/log/auth.log.1.gz"
does not exist, logcheck fails with a misleading message. If
"/var/log/auth.log.1.gz" does exist, logcheck works. See above for
"Possible Solution."
--
See this thread: http://lists.alioth.debian.org/pipermail/logcheck-
devel/2004-October/000924.html
"""
> # chown -R logcheck:logcheck /var/lib/logcheck
This resolved the issue on my box...
let me know if there is anything I can do to help find the bug...
"""
--
logcheck fails when auth.log.1.gz
22 matches
Mail list logo
