Your message dated Thu, 25 Aug 2011 21:45:16 -0700
with message-id <[email protected]>
and subject line Re: Bug#455818: sa-update feature: syslog heavily spammed 
after system reboot
has caused the Debian Bug report #455818,
regarding sa-update feature: syslog heavily spammed after system reboot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
455818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455818
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: spamassassin
Version: 3.2.3-0.volatile1
Severity: normal

I needed to reboot my server after a kernel update. After that I got huge
logcheck mails with warnings like the following:
spamd[3151]: Subroutine <some test or other>_one_line_body_test redefined at 
/var/lib/spamassassin/3.002003/updates_spamassassin_org/20_phrases.cf, rule 
DEAR_SOMETHING, line 4.

Before the reboot spamassassin was running cleanly.

(I've removed the actual tests for fear of this mail being caught by the
BTS spamfilters, but can supply them on request.)

As I had enabled the sa-compile feature a short time ago, that seemed a
likely cause for the problem.

I first tried running sa-compile, but that did not help.

In the end I decided to disable the feature and did an
# rm -r /var/lib/spamassassin/compiled/
which did solve the problem.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages spamassassin depends on:
ii  libarchive-tar-perl         1.30-2       Archive::Tar - manipulate tar file
ii  libdigest-sha1-perl         2.11-1       NIST SHA-1 message digest algorith
ii  libhtml-parser-perl         3.55-1       A collection of modules that parse
ii  libio-zlib-perl             1.04-1       IO:: style interface to Compress::
ii  libnet-dns-perl             0.59-1       Perform DNS queries from a Perl sc
ii  libsocket6-perl             0.19-1       Perl extensions for IPv6
ii  libsys-hostname-long-perl   1.4-1        Figure out the long (fully-qualifi
ii  libwww-perl                 5.805-1      WWW client/server library for Perl
ii  perl                        5.8.8-7etch1 Larry Wall's Practical Extraction

Versions of packages spamassassin recommends:
ii  gcc                    4:4.1.1-15        The GNU C compiler
ii  gnupg                  1.4.6-2           GNU privacy guard - a free PGP rep
ii  libc6-dev              2.3.6.ds1-13etch2 GNU C Library: Development Librari
ii  libmail-spf-query-perl 1:1.999.1-2       query SPF (Sender Policy Framework
ii  libsys-syslog-perl     0.18-1            Perl interface to the UNIX syslog(
ii  make                   3.81-2            The GNU version of the "make" util
ii  re2c                   0.9.12-2          Tool for generating fast C-based r
ii  spamc                  3.2.3-0.volatile1 Client for SpamAssassin spam filte

-- debconf information:
  spamassassin/upgrade/2.40:
  spamassassin/upgrade/2.40w:
  spamassassin/upgrade/cancel: Continue
  spamassassin/upgrade/2.42m: No
  spamassassin/upgrade/2.42u: No

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
--- Begin Message ---
On Wed, Dec 12, 2007 at 12:58:59AM +0100, Frans Pop wrote:
> I needed to reboot my server after a kernel update. After that I got huge
> logcheck mails with warnings like the following:
> spamd[3151]: Subroutine <some test or other>_one_line_body_test redefined at 
> /var/lib/spamassassin/3.002003/updates_spamassassin_org/20_phrases.cf, rule 
> DEAR_SOMETHING, line 4.

Frans, wherever you are, I hope it's spam-free.

For anybody following along, I suspect that this bug was actually
triggered by a perl upgrade that happened somewhere between the previous
spamd restart and the restart that was triggered by the reboot.  In that
case, this bug would have been resolved with the perl-major-upgrade
trigger action added in bug 619817.  Therefor, I'm marking this bug
resolved.

noah

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to