99% Utilization on Rogue MailScanner Process

[Jason Burzenski]

Was wondering if someone could make a recommendation on how to go about
debugging this problem:

I have two dual processor MS servers that I recently upgraded over the
weekend from 4.26.1 to 4.28.6.  Been running for 200+ days without incident.
After the upgrade, one of the two seems to have a rogue MS process that
manifests after 2-10 hours of uptime after the services are started clean.

Here are my processes on the bad machine:

root     30368  0.0  0.6 19312 15580 ?       S    08:25   0:00 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root     29149 99.8  2.1 60096 55448 ?       R    13:28 229:53 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      4762  2.6  1.2 34968 31408 ?       S    17:15   0:04 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      4805  3.5  1.2 35100 31544 ?       S    17:15   0:05 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      4861  2.4  1.2 34880 31280 ?       S    17:15   0:03 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      4947  2.8  1.2 34872 31304 ?       S    17:16   0:04 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      5026  2.3  1.1 34528 30960 ?       S    17:16   0:03 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      5103  1.1  1.1 34280 30708 ?       S    17:16   0:01 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      5133  1.3  1.1 34280 30712 ?       S    17:16   0:01 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      5188  1.4  1.1 34432 30864 ?       S    17:16   0:01 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      5249  2.1  1.1 34300 30728 ?       S    17:16   0:01 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf
root      5490 61.2  2.3 64108 59496 ?       R    17:18   0:14 /usr/bin/perl
-I/usr/lib/MailScanner /usr/sbin/MailScanner
/etc/MailScanner/MailScanner.conf

That 99% process does not die after a service MailScanner reload.  Although
it was sent a SIGHUP properly.  Here are my logs reporting a restart of
these processes:

Mar 16 17:15:36 ms2 MailScanner[28918]: MailScanner child caught a SIGHUP
Mar 16 17:15:36 ms2 MailScanner[29000]: MailScanner child caught a SIGHUP
Mar 16 17:15:36 ms2 MailScanner[29049]: MailScanner child caught a SIGHUP
Mar 16 17:15:36 ms2 MailScanner[28950]: MailScanner child caught a SIGHUP
Mar 16 17:15:36 ms2 MailScanner[29112]: MailScanner child caught a SIGHUP
Mar 16 17:15:36 ms2 MailScanner[28649]: MailScanner child caught a SIGHUP
Mar 16 17:15:36 ms2 MailScanner[29173]: MailScanner child caught a SIGHUP
Mar 16 17:15:36 ms2 MailScanner[28480]: MailScanner child caught a SIGHUP
Mar 16 17:15:37 ms2 MailScanner[29212]: MailScanner child caught a SIGHUP
Mar 16 17:15:37 ms2 MailScanner[4762]: MailScanner E-Mail Virus Scanner
version 4.28.6 starting...

I get no other error messages.  The other box does not have this problem.
Both are running identical configurations.

Any ideas on where to start with this one?

Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20040316/6560056b/attachment.html