Hello
My web interface is functioning fine. My configuration verifing command
is functioning too.
But at the web interface when trying to something at hosts the
following message appear:
The rights on the directory in freebsd are root:wheel but I added in
nagios.cfg
nagios_user=root
Hi,
I have NSCA configured on my Nagios host, and enabled the necessary plugins on
NSClient++ to support NSCA, configure XINETD appropriately inside my NSClient
config I have:
[NSCA Commands]
my_cpu_check=checkCPU warn=80 crit=90 time=20m time=10s time=4
my_mem_check=checkMem MaxWarn=80%
The short answer is yes, the service description you configure on the
client nsca message needs to match that of the service description on
your nagios server. If you want to migrate to a passive check you need
to disable active checks and enable passive ones. You can leave the
check command
Thanks, after reading the 3.x on passive_checks I get how to configure the
service.
Now, what would be the benefit of having active/passive checks enabled for a
service? Say, it takes 5 minutes for Nagios to process my 80 hosts/600
services, if the service that I am looking to enable passive
I just blew away all my nagios config files. Nagios is still running. Is there
any way I can make nagios spit up the configs that were loaded from the command
line or is all hope lost?
--
ThinkGeek and WIRED's GeekDad
A pretty significant portion of the configurations are stored in the objects
cache (/var/log/Nagios/objects.cache for me). This won't be as clean as your
configs (and I'm not sure Nagios can use this file as a config directly), but
you should be able to recover a pretty good amount of your
You can also try /nagios/cgi-bin/config.cgi, not sure if that shows the
running or on-disk configs.
-s
-Original Message-
From: Gius, Mark [mailto:mg...@createspace.com]
Sent: Thursday, June 24, 2010 4:11 PM
To: Nagios Users List
Subject: Re: [Nagios-users] Help - I just blew away my
Shows running settings (config.cgi)
Objects.cache contains a flattened version of all the configuration
objects your configuration tree had; the primary loss is that there
are no templates in objects.cache, so you will have to recreate those.
Isave a copy of objects.cache in a very safe place
