On 18.08.2012 22:43, Camaleón wrote:
I check that and there was only one process running.
I stopped and started the Daemon anyway, but nothing changed.
Ah, okay then. As you commented something about it was working fine in another
instance, that "triggered" a light in my head :-)
I have two machines running the Nagios Daemon. One for all internal
machines, one for all external machines.
From the configuration file you uploaded to Debian paste I only miss the
definitions for "services", is that correct? Unless they're set in a
different configuraion file, there should be listed somewhere.
Yes, it's rather long. Some Services are defined in
services_nagios2.cfg, but most Services are defined in the Host
configuration itself, example:
define service{
use generic-service ; Name
of service template to use
host_name vm.local
service_description Disk Space
check_command check_nrpe_1arg!check_all_disks
notification_interval 0
}
define service{
use generic-service ; Name
of service template to use
host_name vm.local
service_description VirtualBox WinXP IE6
check_command check_nrpe_1arg!check_vm_wxpie6
notification_interval 0
}
define service{
use generic-service ; Name
of service template to use
host_name vm.local
service_description VirtualBox WinXP IE7
check_command check_nrpe_1arg!check_vm_wxpie7
notification_interval 0
}
define service{
use generic-service ; Name
of service template to use
host_name vm.local
service_description VirtualBox WinXP IE8
check_command check_nrpe_1arg!check_vm_wxpie8
notification_interval 0
}
I didn't post them as I don't think it has anything to do with the problem.
Weird, yes. Maybe a problem/glitch coming from the web interface (the CGI
script in charge of rendering the information) and not from Nagios itself.
Can you generate a fake event to check if the reaction from Nagios is as
expected in all levels?
Events working fine. Warnings, Critical, Recovery, Acknowledge
everything works as expected. So, yes, it might be just a CGI-Problem.
Also, given you updated from Squeeze, it could be useful to review the Nagios
logs and also starting, not from scratch but from a "basic" template and
then adding new hosts/services to see how it goes, to discard a simple
configuration issue that can be making noise.
I've purged the Nagios installation (apt-get purge nagios*) and checked
that all config files we're deleted. The I reinstalled Nagios (localhost
was shown correctly). Then I just copied the dx_nagios2.cfg and the
vm_nagios2.cfg into "conf.d". Same problem as before.
Also I compared the "internal" config with the "external" config (again)
but can't see any difference. Beside from the Host-Config and the
htpasswd.users it is identical, according to "diff".
Anyway I was able to narrow it down to one single config file
(dx_nagios2.conf) but I can't see any flaw in it. The funny thing is, if
I rename the host from "dx.local" to "zdx.local" everything works fine
as the Host is the last Host to show up in "Services".
Strange, but I think I can live with that.
Thanks for your help.
Bye.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50334f1f.5060...@concepts-and-training.de
