Page 2 of 2
Re: Issues after upgrading to 5.4.0
Posted: Fri Jan 06, 2017 12:21 pm
by jomann
That output on the manage_services.sh is a bit strange for a 0 exit code.
Can you show us what you get when running:
Code: Select all
systemctl start ndo2db
systemctl status ndo2db -l
Re: Issues after upgrading to 5.4.0
Posted: Fri Jan 06, 2017 2:08 pm
by kcarlson
Code: Select all
[root@nagios ~]# systemctl start ndo2db
[root@nagios ~]# systemctl status ndo2db -l
● ndo2db.service - Nagios Data Out Daemon
Loaded: loaded (/usr/lib/systemd/system/ndo2db.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2017-01-06 13:07:28 CST; 11s ago
Docs: http://www.nagios.org/documentation
Process: 25233 ExecStopPost=/bin/rm -f /usr/local/nagios/var/ndo2db.pid (code=exited, status=0/SUCCESS)
Process: 25231 ExecStart=/usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg -f (code=exited, status=1/FAILURE)
Main PID: 25231 (code=exited, status=1/FAILURE)
Jan 06 13:07:28 nagios.lcom.net systemd[1]: Started Nagios Data Out Daemon.
Jan 06 13:07:28 nagios.lcom.net systemd[1]: Starting Nagios Data Out Daemon...
Jan 06 13:07:28 nagios.lcom.net ndo2db[25231]: Could not bind socket: Address already in use
Jan 06 13:07:28 nagios.lcom.net systemd[1]: ndo2db.service: main process exited, code=exited, status=1/FAILURE
Jan 06 13:07:28 nagios.lcom.net systemd[1]: Unit ndo2db.service entered failed state.
Jan 06 13:07:28 nagios.lcom.net systemd[1]: ndo2db.service failed.
Thanks for the help.
Re: Issues after upgrading to 5.4.0
Posted: Fri Jan 06, 2017 2:46 pm
by dwhitfield
Do you have anything other than what I told you to add in your /usr/local/nagios/etc/ndo2db.cfg?
If so, can you post that entire file?
Re: Issues after upgrading to 5.4.0
Posted: Fri Jan 06, 2017 3:18 pm
by kcarlson
Code: Select all
#####################################################################
# NDO2DB DAEMON CONFIG FILE
#####################################################################
lock_file=/usr/local/nagios/var/ndo2db.lock
ndo2db_user=nagios
ndo2db_group=nagios
socket_type=unix
socket_name=/usr/local/nagios/var/ndo.sock
tcp_port=5668
db_servertype=mysql
db_host=localhost
db_port=3306
db_name=nagios
db_prefix=nagios_
db_user=ndoutils
db_pass=n@gweb
## TABLE TRIMMING OPTIONS
# Several database tables containing Nagios event data can become quite large
# over time. Most admins will want to trim these tables and keep only a
# certain amount of data in them. The options below are used to specify the
# age (in MINUTES) that data should be allowd to remain in various tables
# before it is deleted. Using a value of zero (0) for any value means that
# that particular table should NOT be automatically trimmed.
# Keep timed events for 24 hours
max_timedevents_age=1440
# Keep system commands for 1 week
max_systemcommands_age=10080
# Keep service checks for 1 week
max_servicechecks_age=10080
# Keep host checks for 1 week
max_hostchecks_age=10080
# Keep event handlers for 31 days
max_eventhandlers_age=44640
# DEBUG LEVEL
# This option determines how much (if any) debugging information will
# be written to the debug file. OR values together to log multiple
# types of information.
# Values: -1 = Everything
# 0 = Nothing
# 1 = Process info
# 2 = SQL queries
debug_level=1
# DEBUG VERBOSITY
# This option determines how verbose the debug log out will be.
# Values: 0 = Brief output
# 1 = More detailed
# 2 = Very detailed
debug_verbosity=2
# DEBUG FILE
# This option determines where the daemon should write debugging information.
debug_file=/usr/local/nagios/var/ndo2db.debug
# MAX DEBUG FILE SIZE
# This option determines the maximum size (in bytes) of the debug file. If
# the file grows larger than this size, it will be renamed with a .old
# extension. If a file already exists with a .old extension it will
# automatically be deleted. This helps ensure your disk space usage doesn't
# get out of control when debugging.
max_debug_file_size=1000000
Re: Issues after upgrading to 5.4.0
Posted: Mon Jan 09, 2017 11:21 am
by lmiltchev
Run the following commands, and show the output:
Code: Select all
rm -f /usr/local/nagios/var/ndo.sock
systemctl start ndo2db.service
systemctl status ndo2db.service
If this doesn't solve your issue, post the "/usr/local/nagios/var/ndo2db.debug" file.
Re: Issues after upgrading to 5.4.0
Posted: Mon Jan 09, 2017 11:45 am
by kcarlson
That seems to have taken care of the issue! Ndo2db is now running and the "database backend" object has now gone out of alarm in the dashboard. Thanks for all the help!
Re: Issues after upgrading to 5.4.0
Posted: Mon Jan 09, 2017 11:48 am
by dwhitfield
Excellent news! Are you ready to lock this up?
Re: Issues after upgrading to 5.4.0
Posted: Mon Jan 09, 2017 11:59 am
by kcarlson
Yes, I believe we can lock it. Thanks again!