--zYM0uCDKw75PZbzx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 20, 2006 at 03:56:44PM +0100, Ton Voon wrote:
> I think the lockfile removal is the source of the "multiple Nagios =20
> processes running". The example daemon-init script uses the lockfile =20
> as the status of the process. If you were to do a restart, Nagios =20
> would complete the stop because the signal was sent, but Nagios would =20
> actually be in the process of shutting down. Meanwhile a start would =20
> run, so another Nagios process is kicked off. Then, as both Nagios =20
> processes are trying to access the same files, mayhem can ensue
>=20
> We've got our own startup script and we've change the stop routine to =20
> wait until nagios has actually stopped before moving out of the stop =20
> function. Much more stable, but there's a long delay if Nagios is in =20
> the middle of a host check.
note that we've been seeing hard-to-reproduce problems along these
lines in the debian packages. debian bugs:
#338391: nagios-common: nagios often leaves multiple processes around=20
http://bugs.debian.org/cgi-bin/bugrepor ... g=3D338391
#376070: nagios-common: init script sporadically fails to see existing nagi=
os process=20
http://bugs.debian.org/cgi-bin/bugrepor ... g=3D376070
comments would be welcome.
sean
--zYM0uCDKw75PZbzx
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEqCqDynjLPm522B0RAj/UAJoDqtAcsmCR1rGgP0xw9B27++0i7QCePD3H
874cNubQ6PS9JLVYFFkV6ek=
=MAaD
-----END PGP SIGNATURE-----
--zYM0uCDKw75PZbzx--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]