Gutsy RC logcheck won't run (when calling logtail2)

Bug #153447 reported by David Clayton
6
Affects Status Importance Assigned to Milestone
logcheck (Debian)
Fix Released
Unknown
logcheck (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Gutsy by Daniel Hahler

Bug Description

Binary package hint: logcheck

Ubuntu Gutsy-64bit RC fresh install.

Standard logcheck install returns the following error in the e-mail message:
------------
Warning: If you are seeing this message, your log files may not have been
checked!

Details:
Could not run logtail or save output
(and other info)
----------

Upon investigation of the /usr/sbin/logcheck script, it was set to call the "logtail2" program, changing this to the alternative "logtail" eliminated the error and things now seem to run correctly.

Revision history for this message
Marcel Schaal (marcelschaal) wrote :

I can confirm this bug for Gutsy i386. Replacing logtail2 with logtail solves the issues.

Error Messages:
<------------------------>
sudo -u logcheck logcheck -d -o -t
D: [1192792290] Turning debug mode on
D: [1192792290] Sourcing - /etc/logcheck/logcheck.conf
D: [1192792290] Setting MAILOUT to 1
D: [1192792290] Setting LOGTAIL_OPTS to -t
D: [1192792290] Finished getopts c:dhH:l:L:m:opr:RsS:tTuvw
D: [1192792290] Trying to get lockfile: /var/lock/logcheck/logcheck.lock
D: [1192792290] Running lockfile-touch /var/lock/logcheck/logcheck.lock
D: [1192792291] cleanrules: /etc/logcheck/violations.ignore.d/local
D: [1192792291] cleanrules: /etc/logcheck/ignore.d.workstation/cracklib-runtime
D: [1192792291] cleanrules: /etc/logcheck/ignore.d.workstation/local
D: [1192792291] cleanrules: /etc/logcheck/ignore.d.server/cracklib-runtime
D: [1192792291] cleanrules: /etc/logcheck/ignore.d.server/ntpdate
D: [1192792291] cleanrules: /etc/logcheck/ignore.d.paranoid/apmd
D: [1192792291] cleanrules: /etc/logcheck/ignore.d.paranoid/cracklib-runtime
D: [1192792291] logoutput called with file: /var/log/syslog-errors.log
D: [1192792291] Running /usr/sbin/logtail2 on /var/log/syslog-errors.log
D: [1192792291] error: Killing lockfile-touch - 7862
D: [1192792291] error: Removing lockfile: /var/lock/logcheck/logcheck.lock
D: [1192792291] Error: Could not run logtail or save output
Error: Could not run logtail or save output.
D: [1192792291] cleanup: Removing - /tmp/logcheck.HY7863
<------------------------>

Revision history for this message
Daniel Hahler (blueyed) wrote :

This looks like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443134.
What's the output of "dpkg -s logtail | grep Version" for you?
It should be 1.2.61 and if it's not the workaround appears to be manually installing logcheck (again), so the new version gets pulled in.
I'll provide a patch for a SRU to fix the dependency of logcheck on logtail.

Changed in logcheck:
assignee: nobody → blueyed
status: New → In Progress
Revision history for this message
Daniel Hahler (blueyed) wrote :

The patch/debdiff in bug 149641 fixes this, too.

Changed in logcheck:
assignee: blueyed → nobody
status: In Progress → Confirmed
Revision history for this message
Marcel Schaal (marcelschaal) wrote :

output of "dpkg -s logtail | grep Version" is
Version: 1.2.61

thx a lot

Revision history for this message
Daniel Hahler (blueyed) wrote :

And you have /usr/sbin/logtail2 then, correct?
Then it's a duplicate of bug 149641 - I'll mark it as such.

Changed in logcheck:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.