Subject: amavisd-new: Rotate the log file /var/log/amavis.log
Date: Fri, 09 Jul 2004 12:38:21 +0200
Package: amavisd-new
Version: 20030616p9-1
Severity: minor
Tags: patch
Hi,
When the log file (/var/log/amavis.log) is enable, there is no rotation of this file.
Can you include in the package the following file :
cat /etc/logrotate.d/amavisd
/var/log/amavis.log {
rotate 7
weekly
compress
missingok
create 0640 root root
postrotate
if [ -s /var/run/amavis/amavisd.pid ]; then kill -1 `cat /var/run/amavis/amavisd.pid`; fi
endscript
}
Best regards.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.6
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro
Versions of packages amavisd-new depends on:
ii adduser 3.57 Add and remove users and groups
ii file 4.09-1 Determines file type using "magic"
ii libarchive-tar-perl 1.08-1 Archive::Tar - manipulate tar file
ii libarchive-zip-perl 1.05-1 Module for manipulation of ZIP arc
ii libcompress-zlib-perl 1.16-1.1 Perl module for creation and manip
ii libconvert-tnef-perl 0.17-3 Perl module to read TNEF files
ii libconvert-uulib-perl 1.0.1-1 Perl interface to the uulib librar
pn libdigest-md5-perl Not found.
ii libmailtools-perl 1.62-1 Manipulate email in perl programs
pn libmime-base64-perl Not found.
ii libmime-perl 5.411-3 Perl5 modules for MIME-compliant m
ii libnet-perl 1:1.18-4 Implementation of Internet protoco
ii libnet-server-perl 0.85-3 An extensible, general perl server
ii libunix-syslog-perl 0.100-2 Perl interface to the UNIX syslog(
ii perl [libtime-hires-perl] 5.8.3-3 Larry Wall's Practical Extraction
ii perl-modules [libnet-perl] 5.8.3-3 Core Perl modules.
-- no debconf information
Subject: Re: Bug#258387: amavisd-new: Rotate the log file
/var/log/amavis.log
Date: Sun, 11 Jul 2004 10:12:07 +1000
>>>>> "Frederic" == Frederic MASSOT <[email protected]> writes:
Frederic> When the log file (/var/log/amavis.log) is enable, there
Frederic> is no rotation of this file.
Why would you want to enable /var/log/amavis.log?
The Debian supported configuration is to log via syslog.
Frederic> Can you include in the package the following file :
I believe this would cause errors for people who use the Debian
default of logging via syslog.
(Does amavisd correctly responds to the SIGHUP signal? I haven't
tested it.)
As such I am reluctant to add it.
--
Brian May <[email protected]>
Subject: Re: Bug#258387: amavisd-new: Rotate the log file /var/log/amavis.log
Date: Fri, 16 Jul 2004 10:39:23 +0200
Brian May wrote:
>>>>>>"Frederic" == Frederic MASSOT <[email protected]> writes:
>
>
> Frederic> When the log file (/var/log/amavis.log) is enable, there
> Frederic> is no rotation of this file.
>
> Why would you want to enable /var/log/amavis.log?
>
> The Debian supported configuration is to log via syslog.
To separate the log file by service, and uses. To make them more
readable. I can authorize certain users to consult certain log file.
For example, we installed a email proxy at a customer, I allow him to
consult the Amavis log file. It can see which email were refused and why.
> Frederic> Can you include in the package the following file :
>
> I believe this would cause errors for people who use the Debian
> default of logging via syslog.
>
> (Does amavisd correctly responds to the SIGHUP signal? I haven't
> tested it.)
>
That functions on all the machines where I installed Amavisd-new, except
on the last ?!! :o(
On this machine I replaced the line:
kill -1 `cat /var/run/amavis/amavisd.pid`
by:
/etc/init.d/amavis restart
Best regards.
--
==============================================
| FREDERIC MASSOT |
| http://www.juliana-multimedia.com |
| mailto:[email protected] |
===========================Debian=GNU/Linux===
Subject: Re: Bug#258387: amavisd-new: Rotate the log file
/var/log/amavis.log
Date: Sat, 31 Jul 2004 14:49:18 +1000
tags 258387 wontfix
thanks
>>>>> "Frédéric" == Frédéric Massot <[email protected]> writes:
Frédéric> To separate the log file by service, and uses. To make
Frédéric> them more readable. I can authorize certain users to
Frédéric> consult certain log file.
Frédéric> For example, we installed a email proxy at a customer, I
Frédéric> allow him to consult the Amavis log file. It can see
Frédéric> which email were refused and why.
Sorry, but I believe this situation is very specific to your
particular setup. As such, I feel it is your responsibility rotate the
required log files. I don't want to restart the amavis process
regularly if I can avoid it, this is one of the benefits of using
syslog.
Debian has no software for allowing customers to consult the log file
that I know of either.
The way it is now, all mail logs on my setup go to
/var/log/mail.log. This means that there is only one file to consult
if any mail goes missing.
--
Brian May <[email protected]>
Subject: Re: Bug#289892: amavisd-new: Actually, use this logrotate config instead
Date: Wed, 19 Jan 2005 18:47:56 -0600
On Sat, 31 Jul 2004, Brian May wrote:
>Sorry, but I believe this situation is very specific to your
>particular setup. As such, I feel it is your responsibility rotate the
>required log files. I don't want to restart the amavis process
>regularly if I can avoid it, this is one of the benefits of using
>syslog.
I don't believe that this situation is that specific, I too separate
the amavis logs out and do so on quite a number of installations.
Other people I know who use amavis prefer to do it this way as well,
especially with large mail installations.
It is not required to restart amavis to rotate the logfile.
>The way it is now, all mail logs on my setup go to
>/var/log/mail.log. This means that there is only one file to consult
>if any mail goes missing.
This works great on a machine that doesn't do much mail processing,
but if you run a medium to large mail installation (we have over
10,000 users for email, and over a half-million subscribers to mailing
lists using amavisd-new) you desperately want to separate out your
logfiles so that you can identify problems and deal with them in a
rapid manner. With amavis logging to /var/log/mail.log, courier
logging to /var/log/mail.log, postfix logging to /var/log/mail.log,
etc. you can imagine what its like when hundreds of thousands of
messages are being sent in and out of a machine every minute, its
basically impossible to sort through this information if everything is
blowing their noise into the same logfile all at the same time. If I
didn't separate all the different logging elements that were being
pumped into /var/log/mail.log I would not have been able to identify
amavis specific errors on upgrades, or postfix specific errors when
that subsystem is upgraded, etc.
Additionally, incredibly large logfiles are very difficult to process.
I appreciate trying to keep the system from getting too many logfiles,
however there are really good reasons why things like apache sort the
error logs from the access logs, and one of them isn't because its
fun. If you monitor your amavisd filtering statistics, with either a
logwatch program, a alert system, or a statistical analysis graphing
program, chewing through /var/log/mail.log puts an enormously larger
burden on the system than if amavisd has its own logfile.
> As explained in bug 289892, (see <URL:http://bugs.debian.org/289892>),
> amavisd-new doesn't create a amavis.log file in the default debian
> installation, and rotating a file that doesn't exist seems silly.
I agree, I had changed this in my amavisd config file and had
forgotten that it wasn't the default. However, I believe this *should*
be the default, not just because thats how I like it, or the original
bug submitter likes it, but because its a really good idea.
> If you disagree please let me know why.
See above :)
> Thanks.
Thanks for considering this!
Micah
Dear Customer,
Your parcel was successfully delivered February 03 to UPS Station, but our courier cound not contact you.
Please review delivery label in attachment!
Thanks,
Dan Curtis,
UPS Chief Office Manager.
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.