Starting ndo2db:Support for the specified database - FAILED

[bala_bk]

hi,
no success until now

[bala_bk]

some more debugging info :

-----------------------------------------------------
# service nagios start
Starting Nagios done
-------------------------------------------------------------

From the Nagios log, I see the module is loaded successfully, but since ndo2db service is not started, it is not able to inject data to mysql.

# tail -f /var/log/nagios/nagios.log
[1444807023] Nagios 3.0.6 starting... (PID=23400)
[1444807023] Local time is Wed Oct 14 12:47:03 IST 2015
[1444807023] LOG VERSION: 2.0
[1444807023] ndomod: NDOMOD 2.0.0 (02-28-2014) Copyright (c) 2009 Nagios Core Development Team and Community Contributors
[1444807023] ndomod: Could not open data sink! I'll keep trying, but some output may get lost...
[1444807023] ndomod registered for contact data'
[1444807023] ndomod registered for contact notification data'
[1444807023] Event broker module '/usr/local/nagios/bin/ndomod.o' initialized successfully.
[1444807023] Finished daemonizing... (New PID=23401)
--------------------------------------------------------
# service ndo2db start
Starting ndo2db:Support for the specified database server is either not yet supported, or was not found on your system.
done.

[jdalrymple]

From what I can gather the only thing that would cause the error you're seeing is if db_servertype was anything besides mysql in ndo2db.cfg.

Can you verify that you're using the right path when trying to spin up ndo2db?

Code: Select all

[root@localhost etc]# ps -ef | grep ndo
nagios     1299      1  0 14:12 ?        00:00:00 /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg

Check the settings in your init script.

[bala_bk]

Hi,
I configured this on RHEL 7 and everything works fine. I'll start comparing the config files between Suse 11.2 & RHEL 7.1 and see if there are any differences.

Thanks to all for your support and help.
-Bala.

[tgriep]

Let us know what you find out.
It looks like the database may be corrupted or that it cannot be accessed for some reason.
Take a look in the mysqld.log file and see if there are any errors that can help.