ports/169759: nrpe2 doesn't start after subsequent reboots
Lawrence Chen
lchen at lhaven.homeip.net
Tue Jul 10 04:30:12 UTC 2012
>Number: 169759
>Category: ports
>Synopsis: nrpe2 doesn't start after subsequent reboots
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Jul 10 04:30:11 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Lawrence Chen
>Release: FreeBSD 9.0-RELEASE-p3 amd64
>Organization:
>Environment:
System: FreeBSD zen.lhaven.homeip.net 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
On subsequent reboots, it sees /var/spool/nagios/nrpe2.pid already
exists and refuses to start. Even though nrpe2 isn't running as the
indicated pid.
>How-To-Repeat:
Reboot system after nrpe2 is working.
>Fix:
Initially, I changed pidfile location to somewhere that is cleaned up
after reboot (/tmp). But, later making the directory /var/run/nagios,
with 0775 permissions and nagios:nagios ownership also worked.
Though I feel rc scripts should also be able to handle stale pid files.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list