Hi guys!
I am now officially baffled on how Nagios handles service escalations and
notifications. I'm using Nagios 3.2.3 on SLES 10 SP3 and my current setup
is this:
service_escalation.cfg:
define serviceescalation {
service_description http_80
host_name apache02
>
> I've got a Nagios installation all up and running and working just fine.
> Now I have to start monitoring some Windows Servers.
>
> There are so many different plugins. What are the recommendations for doing
> this?
>
> We have some Win Server 2003, 2008 as well as Exchange and SQL.
>
> Thanks
I finally figured this one out. The reason why the plugin was spewing out
the "out of bounds" error was because of the underlying performance issue of
the server. When the server becomes slow to respond, Nagios throws this
error. The hint provided by Sven proved that it was indeed the disk I/O
issu
Hi Allan,
I'm just saying that this could be a bug in the current Nagios, or the
plugin as Terry pointed out, since this was never present in the previous
version that I was using. This really freaks me out.
I enabled Nagios's debug mode in the hopes of getting more about this. I am
also consider
Jun 20, 2011 at 9:24 AM, Rai Ricafrente
> wrote:
> > Hi everyone,
> >
> > I just installed a fresh Nagios v3.2.3 with about 150 hosts and 600
> > services. I just noticed from time to time, hosts are throwing out
> "Return
> > code of 141 is out of bounds
Have you checked your time periods?
On Fri, Jun 17, 2011 at 10:42 PM, Manish Kumar wrote:
>
> Hi Friends,
>
> I have implemented Nagios Core-3.2.3 on Fedora Core 14 and configured it
> for monitoring of around 230 network devices for different services like
> up/down status, uptime, ports link st
Hi everyone,
I just installed a fresh Nagios v3.2.3 with about 150 hosts and 600
services. I just noticed from time to time, hosts are throwing out "Return
code of 141 is out of bounds" status every now and then, then it will
eventually go away. I don't know if this has anything to do with the plu
Thanks for pointing the doc. I've been going through that and I guess I was
looking for the part where it says that DOWN = 1 and not 2.
On Thu, Mar 17, 2011 at 3:40 PM, Giacomo Montagner wrote:
> On Thu, 17 Mar 2011 14:57:08 +0800
> Rai Ricafrente wrote:
>
> > I am looki
I am looking at the status.dat file and I noticed that the current_state is
=1 even when the host is down and is in critical state. I assume that if a
host is down, the current_state should be =2. I am not sure how Nagios sets
the current_status but in my case, the host is definitely off:
admin1@s
