Nagios Support Forum

Thanks,
I cannot get to CCM->Tools->Write Config Files->Write->Verify because nagios is not running
Nagios status show its not running, but acutally it is..
nagios 4666 1 1 10:41 ? 00:06:02 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

Here is requested info..

[root@nagios01 var]# /usr/local/nagios/bin/nagios | head -2
Nagios Core 4.0.7
[root@nagios01 var]# /usr/local/nagios/bin/ndo2db | head -2
NDO2DB 2.0.0
[root@nagios01 var]# service npcd status
NPCD running (pid 25116).
[root@nagios01 var]# service ndo2db status
ndo2db is not running but subsystem locked
[root@nagios01 var]# ls /usr/local/nagios/var/spool/xidpe | wc -l
2525
[root@nagios01 var]# ls /usr/local/nagios/var/spool/perfdata | wc -l
0
[root@nagios01 var]# ls /usr/local/nagios/var/spool/checkresults | wc -l
0

Getting to CCM write config, should have no regard for whether core is running or not. Is the whole XI web interface down at the moment? You can correct the ndo locked issue and get the service started again by:

do you mean this..

[root@nagios01 etc]# grep lock ndo2db.cfg
lock_file=/usr/local/nagios/var/ndo2db.lock

[root@nagios01 etc]rm -f /usr/local/nagios/var/ndo2db.lock
[root@nagios01 etc]# service ndo2db start
Starting ndo2db: done.
[root@nagios01 etc]# service ndo2db status
ndo2db is not running but subsystem locked

What do you see with: ps -ef | grep 'ndo\|bin/nag'

upgrade is successful after some filesystems fixes. But now autodiscovery job never completes.
grep "COMPONENT_VERSION" /usr/local/nagiosxi/html/includes/components/autodiscovery/autodiscovery.inc.php
COMPONENT_VERSION => '2.05',

anil406 wrote:upgrade is successful after some filesystems fixes. But now autodiscovery job never completes.
grep "COMPONENT_VERSION" /usr/local/nagiosxi/html/includes/components/autodiscovery/autodiscovery.inc.php
COMPONENT_VERSION => '2.05',

Unfortunately, you will have to delete the current job and re-create a new one.

I tried that few times, no luck.

How big of a subnet are you scanning? If you scan 1 specific ip, does it finish?

thanks abrist, it was file ownership issue. autodiscovery file has to be set to apache.nagios. But it was set nagios.nagios, I am not sure these were set in build? anyways that made the scan hung. It working after chaning ownership to apache.nagios, however it still can not detect the os type and services, how does autodiscovery detect os type and services, fyi we are using check_by_ssh, no nrpe.

The OS and services are mostly a guess on the part of nmap, the tool that is run in the background. It uses a technique called fingerprinting that, while normally pretty good at guessing, is not 100% and can be foiled by the remote system intentionally not responding with identifying information. This applies to both the OS and services running on it.

Can you post a screenshot of the page that shows all the hosts and services you can check/uncheck? I want to see what nmap is reporting beside the port.