NSCA forking problem

[Marc Powell]

I had a raid5 array that was silently failing. The backplane on the
device was going bad. FWIW, I'm running a similar number of passive
checks (2763) on a 4-cpu, pIII 700 with a gig of ram. My nagios.cmd pipe
rarely exceeds 2K and is 0 length about 50% of the time so I feel I have
plenty of room to grow. The machine is doing many other things but is
still barely utilized--

  3:40pm  up 20 days, 18:51,  1 user,  load average: 0.52, 0.35, 0.29

--
Marc


> -----Original Message-----
> From: Frederik Vanhee [mailto:frederik.vanhee at perso.be]
> Sent: Friday, April 29, 2005 3:24 PM
> To: Marc Powell
> Cc: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] NSCA forking problem
> 
> Well Marc,
> 
> my system is checking for external commands, the command check
interval
> is set to -1, so the only thing I'm not sure of is the hardware.
> What exactly did you experience with hardware problems ?
> 
> I rebooted the server twice and now it runs fine, I don't understand
> anymore, I just have around 20 instances now
> 
> Frederik
> 
> >This is normal if you don't have nagios checking for external
commands,
> >the command check interval is too long for the amount of updates you
> >have incoming or you have hardware problems (I've experienced all
> >three). I'd suggest you start by setting your command_check_interval
in
> >nagios.cfg to be -1 to have nagios look for external commands as
often
> >as it can.
> >
> >
> >


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r 
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null