>Number: 126237
>Category: ports
>Synopsis: amavisd refuses to start with "Invalid process ID"
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Aug 04 12:00:10 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Guido Boehm
>Release: FreeBSD 7.0
>Organization:
unixuni
>Environment:
FreeBSD xxx.ctnm.de 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #1: Thu Jul 24 13:16:19 CEST 2008 root@xxx.ctnm.de:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
After a crash, amavisd-new (installed inside a jail) refused to start, this is the message i got from /var/log/jail_vscan01_console.log:
..
Starting clamav_clamd.
Starting clamav_freshclam.
Starting amavisd.
Invalid process ID in file /var/amavis/amavisd.pid: [1528] at /usr/local/sbin/amavisd line 12827.
Starting sshd.
..
Line 12827 looks like this:
$amavisd_pid =~ /^\d{1,10}\z/ && $amavisd_pid > 1 && $amavisd_pid != $$
or die "Invalid process ID in file $pidf: [$amavisd_pid]";
I guess amavisd got exactly the same PID it had after the last boot, which isn't that uncommon after all, i'm not sure what this check is supposed to do..
>How-To-Repeat:
>Fix:
After executing
/usr/local/etc/rc.d/amavisd start
a second time from inside the jail amavisd started without errors.
>Release-Note:
>Audit-Trail:
>Unformatted: