I've noticed that when stopping and restarting Spamassassin I see the below:

Jun  4 17:29:31 localhost spamd[14482]: spamd: server killed by SIGTERM,
shutting down
Jun  4 17:29:31 localhost spamd[14482]: spamd: handled cleanup of child pid
31167 due to SIGCHLD
Jun  4 17:29:31 localhost spamd[14482]: spamd: handled cleanup of child pid
24686 due to SIGCHLD
Jun  4 17:29:31 localhost spamassassin: spamd shutdown succeeded
Jun  4 17:29:37 localhost spamd[6778]: logger: removing stderr method
Jun  4 17:29:37 localhost spamassassin: spamd startup succeeded
Jun  4 17:29:41 localhost spamd[6783]: Can't locate Log/Agent.pm in @INC (@INC
contains:
lib /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl) at (eval 1362) line 2.
Jun  4 17:29:41 localhost spamd[6783]: Can't locate Log/Agent.pm in @INC (@INC
contains:
lib /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl) at (eval 1362) line 2.
Jun  4 17:29:41 localhost spamd[6783]: BEGIN failed--compilation aborted at
(eval 1362) line 2.

I have the razor plug-in enabled and razor-admin -v reports the version to be:

Razor Agents 2.84, protocol version 3

If I go and disable the razor plug-in and stop and start spamassassin I still
see the above:

# Razor2 - perform Razor2 message checks.
#
# Razor2 is disabled here because it is not available for unlimited free
# use.  It is currently free for personal use, subject to capacity
# constraints.  See the Cloudmark SpamNet Service Policy for more details.
#
# loadplugin Mail::SpamAssassin::Plugin::Razor2

Using a test message that with Razor enabled it received this score:

1.5 RAZOR2_CF_RANGE_E8_51_100 Razor2 gives engine 8 confidence level
                            above 50%
                            [cf: 100]
0.5 RAZOR2_CHECK           Listed in Razor2 (http://razor.sf.net/)
0.5 RAZOR2_CF_RANGE_51_100 Razor2 gives confidence level above 50%
                            [cf: 100]

After disabling the razor plugin there are no razor checks performed:

1.2 INVALID_DATE           Invalid Date: header (not RFC 2822)
2.9 DATE_SPAMWARE_Y2K      Date header uses unusual Y2K formatting
3.2 FROM_LOCAL_NOVOWEL     From: localpart has series of non-vowel letters
3.1 MSGID_YAHOO_CAPS       Message-ID has ALLCAPS@yaho...
4.2 MSGID_SPAM_CAPS        Spam tool Message-Id: (caps variant)
1.0 FREEMAIL_FROM          From-address is freemail domain
-0.0 NO_RELAYS              Informational: message was not relayed via SMTP
1.4 DATE_IN_FUTURE_96_XX   Date: is 96 hours or more after Received: date
2.0 FREEMAIL_REPLYTO       Different freemail address found in Reply-To or
Body
                             than From
2.3 FORGED_YAHOO_RCVD      'From' yahoo.com does not match 'Received' headers
-6.4 BAYES_00               BODY: Bayesian spam probability is 0 to 1%
                            [score: 0.0000]
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.0 DCC_CHECK_NEGATIVE     Not listed in DCC
                            [cpollock 1117; Body=2 Fuz1=2 Fuz2=2]
1.7 SARE_SPEC_ROLEX        Rolex watch spam
2.5 L_UNVERIFIED_YAHOO     L_UNVERIFIED_YAHOO
1.0 SAGREY                 Adds 1.0 to spam from first-time senders

I did this to ensure that I had in fact disabled razor checks in SA. Again
stopping and starting SA I get the same output with the plug-in disabled:

Jun  4 18:02:13 localhost spamd[7788]: spamd: server killed by SIGTERM,
shutting down
Jun  4 18:02:13 localhost spamassassin: spamd shutdown succeeded
Jun  4 18:02:15 localhost spamd[9483]: logger: removing stderr method
Jun  4 18:02:15 localhost spamassassin: spamd startup succeeded
Jun  4 18:02:19 localhost spamd[9488]: Can't locate Log/Agent.pm in @INC (@INC
contains: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl) at (eval 1355) line 2.
Jun  4 18:02:19 localhost spamd[9488]: Can't locate Log/Agent.pm in @INC (@INC
contains: /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5
/usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4
/usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3
/usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1
/usr/lib/perl5/vendor_perl) at (eval 1355) line 2.
Jun  4 18:02:19 localhost spamd[9488]: BEGIN failed--compilation aborted at
(eval 1355) line 2.

My razor-agent.conf file looks like this, and this is the same it has always
looked with the exception of the debug level which I may change from time to
time.

#
# Razor2 config file
#
# Autogenerated by Razor-Agents v2.84
# Wed Jun  4 19:11:28 2008
# Created with all default values
#
# see razor-agent.conf(5) man page
#

debuglevel             = 6
identity               = identity
ignorelist             = 0
listfile_catalogue     = /home/chris/.razor/servers.catalogue.lst
listfile_discovery     = /home/chris/.razor/servers.discovery.lst
listfile_nomination    = /home/chris/.razor/servers.nomination.lst
logfile                = /home/chris/.razor/razor-agent.log
logic_method           = 4
min_cf                 = ac
razordiscovery         = discovery.razor.cloudmark.com
rediscovery_wait       = 172800
report_headers         = 1
turn_off_discovery     = 0
use_engines            = 4,8
whitelist              = razor-whitelist

Bottom line, I'm baffled as to what is causing this. Razor is still working
correctly as far as I can tell.

Anyone have any ideas/suggestions?

--
Chris
KeyID 0xE372A7DA98E6705C