Displaying 20 results from an estimated 600 matches similar to: "Bug#435443: logcheck: have logtail handle rotated logs by itself"
2008 Dec 27
2
Bug#509885: does not cleanly update from logtail2
Package: logtail
Version: 1.2.68
Severity: normal
Hi,
logtail does not cleanly update from logtail2:
$ sudo dpkg --install /var/cache/apt/archives/logtail_1.2.68_all.deb
(Reading database ... 26564 files and directories currently installed.)
Unpacking logtail (from .../logtail_1.2.68_all.deb) ...
dpkg: error processing /var/cache/apt/archives/logtail_1.2.68_all.deb (--install):
trying to
2007 Jan 15
1
Bug#406973: logtail misses lines in rotated file
Package: logtail
Version: 1.2.52
Severity: normal
Tags: patch
Hi,
When a logfile is rotated, logtail misses the lines logged between the
last logtail run and the logfile rotation.
The attached patch allows to set an alternate logfile that logtail tries
to use as the old logfile if the inode has changed.
It can be used as:
logtail -f /var/log/syslog -a /var/log/syslog.1
(Please note that this
2007 Sep 09
1
Bug#441388: logtail2 doesn't work if no archived logs found
Package: logtail
Version: 1.2.61
Severity: important
Recently logcheck stopped working on my system and after running it
manually I traced it to logtail2... I'd recently been forced to delete
the archived logs on my system in order to make some space and that
appears to confuse logtail2 completely...
e.g.:
root at macaroni:~# logtail2 -t /var/log/syslog
Cannot get /var/log/syslog.1.gz mtime:
2005 Oct 29
1
Bug#336265: logrotate detection, possible attack not checked by logcheck
Package: logcheck
Version: 1.2.41
Problem: Logcheck try to detect if log file have been rotate or not by file size way.
Possible attack:
- current log file (sizeA)
- run logcheck, (logcheck/logtail put inode in offsetfile), offset=sizeA
- [attacker run attack 1]
- run logrotate
- [attacker run attack 2]
- run logcheck may don't detect the rotation and don't check the log for attack 1
2004 Nov 10
1
logtail ignoring information in rotated logs
Hi gang,
While writing a script that uses logtail, I noticed that logtail assumes
nothing interesting happened between its last invocation and the
rotation, which means that exciting bits of data could be lost.
This seems a bit dodgy (correct me if I'm wrong about how it works!) so
I made a dodgy patch to logtail that checks for the existence of
$logfile.0, which on Debian seems to always be
2007 Sep 10
1
BUG - logtail2 failing if bzip2 is used
Hello,
logtail 1.2.60. logtail2 has a hardcoded '.gz' suffix during various
checks of rotated archive logfiles, but if you use bzip2 for compressing
them, it fails, of course.
--
Micha? J?czalik, +48.603.64.62.97
INFONAUTIC, +48.33.487.69.04
2004 Jul 12
0
[patch] logtail recheck permissions of offset files
hi
before checking in that chown fix,
i wanted you to take a look.
tested on my workstation.
basicaly the patch takes care that logtail saves the
offset file with the correct permissions.
when playing around lately with file tampering
and those invoking logcheck as root.
i got similar output to #253998
Alfie may point out that i should not invoke logcheck
as root, but i better fix that before
2005 Jan 11
2
Bug#289801: Logtail should output error messages to stderr, not stdout
Package: logtail
Version: 1.2.33
Severity: normal
Hi...
Logtail should not output error messages to standard output, since this
violates the principle of least surprise.
In particular, my application was broken by the semantics of logtail changing
in version 1.2.21 (when you added switches for the default arguments to
logtail). I think this was a bad move -- you broke an interface used by
2005 May 20
0
logcheck error, logtail output
Hello,
I'm having this error:
Warning: If you are seeing this message, your log files may not have
been
checked!
Details:
Could not run logtail or save output
Check temporary directory: /tmp/logcheck.EIX3jp
declare -x HOME="/var/lib/logcheck"
declare -x LANG="en_US"
declare -x LANGUAGE="en_US:en_GB:en"
declare -x LOGNAME="logcheck"
declare -x
2006 Jul 04
0
Processed: setting package to logcheck logcheck-database logtail, tagging 354820, tagging 355085, tagging 356681 ... ... ... ... ... ... ...
Processing commands for control at bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.9.20
> package logcheck logcheck-database logtail
Ignoring bugs not assigned to: logcheck-database logtail logcheck
> tags 354820 + pending
Bug#354820: rules to filter out entries caused by ssh scanners
Tags were: patch
Tags added: pending
> tags 355085 + pending
2007 Jun 22
0
logtail is incomplete.
logtail is a great program but it is incomplete.
Currently it has no iead about log rolls which is normally done by renaming
files from log to log.1 then log.2 etc...
logtail should on seeing a different inode, try to determine if the log was
just rolled as normal, and output the remainer of that rolled file, before
outputing the other files down the chain to the current logfile.
Of course
2008 Sep 19
1
Bug#499415: setting package to logcheck-database logtail logcheck, tagging 499393, tagging 499415
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# logcheck (1.3.2) experimental; urgency=low
#
# * Apply patch from Jari Aalto for fixing package description paragraph
# ordering by importence, thanks (closes: #499415)
# * Supress cron session closed messages too, thanks to Ferenc Wagner for
# noticing (closes: #499393)
#
package logcheck-database
2008 Sep 19
1
Bug#499415: setting package to logcheck-database logtail logcheck, tagging 499415
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# logcheck (1.3.2) experimental; urgency=low
#
# * Apply patch from Jari Aalto for fixing package description paragraph
# ordering by importence, thanks (closes: #499415)
#
package logcheck-database logtail logcheck
tags 499415 + pending
2008 Jun 24
1
Bug#446310: setting package to logcheck-database logtail logcheck, tagging 452879, tagging 450660, tagging 450697 ...
# Automatically generated email from bts, devscripts version 2.10.30
# via tagpending
#
# logcheck (1.2.65) unstable; urgency=low
#
# * ignore.d.server/courier:
# - update rules to include port information; thanks to Antoine Pardignon
# (closes: #446310).
# - ignore couriertcpd messages; thanks to Andrew Gallagher
# (closes: #451118).
# * ignore.d.server/smbd_audit:
# -
2008 May 15
1
Bug#471936: setting package to logcheck-database logtail logcheck, tagging 473619, tagging 478334, tagging 472368 ...
# Automatically generated email from bts, devscripts version 2.10.27
#
# logcheck (1.2.64) unstable; urgency=low
#
# * ignore.d.server/dhcp
# - Adding dhcp rules for DNS updates by ddns_remove_a()
# (closes: #459875, #472368)
# - Added dhcp "removed reverse map" rule, which occurs on DHCPRELEASE.
# * ignore.d.server/spamd
# - deal with socket connections by e.g. evolution
2008 Jun 24
1
Bug#483214: setting package to logcheck-database logtail logcheck, tagging 487208, tagging 484546, tagging 482523 ...
# Automatically generated email from bts, devscripts version 2.10.30
# via tagpending
#
# logcheck (1.2.65) unstable; urgency=low
#
# * ignore.d.server/postfix:
# - ignore connection messages for anonymous TLS connections; thanks to
# Justin Larue (closes: #486440).
# - ignore hostname verification due to DNS name not found; thanks to
# Justin Larue (closes: #486440).
# *
2008 Aug 31
1
Bug#491694: setting package to logcheck-database logtail logcheck, tagging 491694, tagging 474239, tagging 489172 ...
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# logcheck (1.3) unstable; urgency=low
#
# * Formalise the dropping of violations.d/logcheck. Please see
# /usr/share/doc/logcheck-database/NEWS.Debian.gz for more information
# (closes: #471072).
# * Add Auto-Submitted header to outgoing mails (closes: #489172).
# * ignore.d.server/kernel:
# -
2009 Apr 09
1
Error in saveLog(currentLogFileName
Hello, very basic question from a user who is baffled by the workings of computers in general
When logging off R, a dialog box asked if I wanted to save my log, I chose yes. Then I noticed that the following message appeared in the Command Window
Error in saveLog(currentLogFileName) :
unused argument(s) ("C:/Documents and Settings/prewpj/My Documents/Data/Analyses/Healthcare/Hand Care
2008 Mar 05
1
Bug#445072: setting package to logcheck-database logtail logcheck, tagging 444097, tagging 445069, tagging 444096 ... ... ... ... ... ... ...
# Automatically generated email from bts, devscripts version 2.10.18.1
#
# logcheck (1.2.64) unstable; urgency=low
#
# * ignore.d.server/bind:
# - moved "[bind] query $FOO denied" rule to violations.ignore.d
# (closes: #443881).
# - added bind's "AXFR ended" rule alongside "AXFR started"
# (closes: #445046).
# - added "adding an
2018 Nov 11
0
CentOS 6: Logrotate / selinux problem
Ever since a recent power failure I have been getting a Logrotate error. My
machine is on a UPS -- it shutdown cleanly, but I suspect that its BIOS/RTC
battery is dead, since the machine came up thinking it was 1982 :-(. I reset
the clock and everything is fine, *except* I had to delete Logrotate's state
files (which had bad dates). But now Logrotate is raising the error:
error: error