Date: Wed, 23 Aug 2017 13:05:37 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 221740] net-mgmt/nrpe: not starting after crash Message-ID: <bug-221740-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221740 Bug ID: 221740 Summary: net-mgmt/nrpe: not starting after crash Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: zeising@FreeBSD.org Reporter: mat@FreeBSD.org Assignee: zeising@FreeBSD.org Flags: maintainer-feedback?(zeising@FreeBSD.org) Created attachment 185691 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D185691&action= =3Dedit v1 When nrpe quits ungracefully, for example, if the box was rebooted, it often does not start because the pid file is still there, and the pid in it exists and the pid in it is in use by some other process. The dubious code is in src/nrpe.c in write_pid_file() around line 1756 that could be axed. But I think the easiest way to fix this is with the attached patch. precmd = is run just before starting the daemon and after checking that it is not alrea= dy running. With this, it starts just fine, and still refuses to start if it is really already running, but starts fine if the pid file contains a pid that exists= but is not nrpe. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221740-13>