Nagios Support Forum

/usr/local/nagios/bin/ndo2db | head -2
NDO2DB 1.5.2
---
I do indeed have check_mk (ver 1.2.2p3) running.
If that is an issue is there a specific method for removing it?

I do indeed have check_mk (ver 1.2.2p3) running.
If that is an issue is there a specific method for removing it?

You can just comment out the lines, that refer to mk-livestatus in the nagios.cfg file and restart nagios. The problem is that the nagios service won't start as ndo2db didn't get upgraded for some reason (possibly config errors or "ghost" hosts/services).

Go to: CCM->Tools->Write Config Files->Click on "Write" and "Verify" buttons and examine the output for errors. If you have config errors (warnings are OK), go back to CCM and fix them, then run the "Write Config Tool" again to check for more errors. Run the "Write Config Tool" as many times as you have to, until ALL of the config errors are gone. Then Apply Configuration. Go to the original install directory, and re-run the upgrade script:
After this is done, make sure the ndo2db has been upgraded:
You should see:
Let me know if this helped.

I get only warnings, for alleged "Duplicate definition" issues, that is all.
I have learned that when I have several similar named hosts that have the same service check names NagiosXI gives me these duplicate problems.
Nothing to fix then.?.
It ends with "No serious problems were detected during the pre-flight check "

This seems to be a dead end.

What is the ndo2db version?
Did you have any mk-livestatus entries in the nagios.cfg? Are they commented out?

Downloaded the -2014r1.1 version.
--------------------------------------------
Commented out these 2 lines at end of nagios.cfg:
###use_true_regexp_matching=0# Load Livestatus Module
###broker_module=/usr/lib/check_mk/livestatus.o /opt/nagios/var/rw/live
----------
Ran upgrade, all looked good.
At end:
> ndodb was: NDO2DB 2.0.0
> 'System Status ' was all green
> 'Monitoring Engine Status' showed not started
> Selecting 'Start' for 'Monitoring Engine' would show Success but it would not start.

The web interface may be having trouble picking up the lock file. Let's make sure it is running and see what permissions are in place.

Cleared /tmp then ran upgrade again, after upgrade:
---------------------------------------------------------------
$ ps -ef | grep bin/nag


$ ll /usr/local/nagios/var/nagios.lock
-rw-r--r-- 1 nagios nagios 6 Jun 10 06:38 /usr/local/nagios/var/nagios.lock

$ cat /usr/local/nagios/var/nagios.lock
14797
-----------------------------------------------------
Could not start from command line either.
Went to "Write Config Files" and did a verify, all looks fine:
-----------------------------------------------------
Nagios Core 4.0.6
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 04-29-2014
License: GPL

Website: http://www.nagios.org
Reading configuration data...
Read main config file okay...
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in host type objects (config file '/usr/local/nagios/etc/static/check_mk_templates.cfg', starting at line 88)
Warning: failure_prediction_enabled is obsoleted and no longer has any effect in service type objects (config file '/usr/local/nagios/etc/static/check_mk_templates.cfg', starting at line 157)
Read object config files okay...

Running pre-flight check on configuration data...

Checking objects...
Checked 436 services.
Checked 63 hosts.
Checked 14 host groups.
Checked 5 service groups.
Checked 13 contacts.
Checked 3 contact groups.
Checked 125 commands.
Checked 18 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 63 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 18 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check

If nagios is not running, there should be no lock file. Make sure nagios is stopped, kill any potential instances, delete the lock file, and then restart nagios. If you get any errors, post them here.

service nagios stop
Stopping nagios: /etc/init.d/nagios: line 67: kill: (32016) - No such process
done.

killall nagios
nagios: no process killed

ps -aef | grep nagios.cfg
myid 307 24147 0 11:38 pts/0 00:00:00 grep nagios.cfg

cat /usr/local/nagios/var/nagios.lock
cat: /usr/local/nagios/var/nagios.lock: No such file or directory

service nagios start
Starting nagios: done.

service nagios status
nagios is not running

cat /usr/local/nagios/var/nagios.lock
584
------------------
NOTE: The lock file is generated every time Nagios tries to start.
It is not cleaned up when the start fails.

Run the following commands and show us the output: