From: Owen B. <owe...@gm...> - 2006-11-30 20:48:32
|
I'm not too sure, but I have seen other people report this happening when issuing a restart to the init script. The recommended way seems to be to do a stop, wait for everything to settle and then a start. Although that was supposed to have been fixed in more recent versions. Owen On 11/30/06, Mark Hennessy <mhe...@cl...> wrote: > But how could two Nagios processes start like that? > > -- > Mark Hennessy > > > -----Original Message----- > > From: nag...@li... > > [mailto:nag...@li...] On Behalf > > Of Owen Berry > > Sent: Thursday, November 30, 2006 3:26 PM > > To: Nagios Users mailinglist > > Subject: Re: [Nagios-users] Nagios 2.5 and weird problem > > > > Check the start times of those processes. There should be 1 with the > > time that you originally started Nagios. Any others should be pretty > > close to the current time, which would indicate they're forked > > processes. > > > > If you suspect multiple Nagios's running, I would stop it the usual > > way, wait a bit and make sure everything Nagios related stops, and > > then start again. If you have 2 instances running, you might need to > > some manual process killing before starting up again. > > > > Owen > > > > On 11/30/06, Mark Hennessy <mhe...@cl...> wrote: > > > Nothing of note appears. :( > > > > > > Is it usually the case that when no checks are running that > > there would be > > > two instances of the Nagios process running? > > > > > > nagios 53577 90.2 0.1 2840 2064 ?? R 12:37PM 146:50.41 > > > /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg > > > nagios 76606 0.0 0.1 3100 2360 ?? Ss 9:40AM 0:54.89 > > > /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg > > > > > > -- > > > Mark Hennessy > > > |