ports/138536: Amavisd dying when newsyslog is run

[Jim]

>Number:         138536
>Category:       ports
>Synopsis:       Amavisd dying when newsyslog is run
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 04 17:10:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Jim
>Release:        7.1-RELEASE
>Organization:
Graff Chevrolet
>Environment:
FreeBSD xxxxxxxxxx.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan  1 14:37:25 UTC 2009     root at logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386       
>Description:
I update ports more or less daily as new versions come out.  After updating ports yesterday mid-day, errors started being logged to /var/log/messages indicating a dying process.  After noticing that the time-stamps are almost always 1 hour and 10 minutes apart, I did some troubleshooting and discovered that it happens when the hourly cron job to fire newsyslog activates.  An example of the errors I get are:

Sep  4 06:31:56 xxxxxxxxxx kernel: pid 2644 (perl), uid 110: exited on signal 11

This doesn't appear right away when newsyslog fires, but there is a delay of a few seconds to a few minutes.  I did a ps -ax and saved the output, then ran newsyslog manually from a root shell.  When the error appeared in /var/log/messages, I grepped the saved output of ps and discovered that the dying process is one of the child processes of amavisd-new.  The exact name of the child process varies somewhat, but seems to follow the following pattern:

amavisd (chN-avail) (perl)

Where N is an integer from 1 to 9.

I tried re-compiling, stopping, deinstalling, reinstalling, and starting amavisd-new; this had no effect whatsoever - when I run newsyslog, one of the amavisd children dies a short while later.  These errors did not happen prior to my updating ports yesterday, so I have to assume that something related to the update is causing the problem.  Also, executing newsyslog will result in the error being logged more often than the 70 minutes observed in the system log, which tells me there is something clashing between these two processes.  There have been no configuration changes to the machine during this time other than adding/removing normal users and the updating of these ports:

p5-Compress-Raw-Zlib  (Updated to 2.021) ***
p5-Convert-UUlib  (Updated to 1.30,1) ***
p5-Date-Calc  (Updated to 5.7)
squirrelmail  (Updated to 1.4.20.r2_1)


According to pkg_info -R, the ports that have an asterisk above are dependencies of amavisd.
>How-To-Repeat:
Run newsyslog from a command prompt when amavisd is running or allow it to fire from cron when amavisd is running, then watch /var/log/messages for one of the child processes of amavisd to die.
>Fix:
Not a clue - sorry. :(

>Release-Note:
>Audit-Trail:
>Unformatted: