Re: Host Detail Page - High CPU usage
Posted: Mon Jul 27, 2015 2:31 pm
Could you post the following file?
Code: Select all
/usr/local/nagios/etc/ndo2db.cfgSupport for Nagios products and services
https://support.nagios.com/forum/
Code: Select all
/usr/local/nagios/etc/ndo2db.cfgCode: 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=xxx.xxx.xxx.xxx
db_port=3306
db_name=nagios4
db_prefix=nagios_
db_user=xxxxx
db_pass=xxxxx
## 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=0
# 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=1
# 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
Code: Select all
mysqlcheck -f -r -u <db_user> -p<db_pass> --databases nagios -h xxx.xxx.xxx.xxxI assume you meant nagios4, is this safe to run on a production system?tgriep wrote:Could you run the following from the Nagios XI server and post the output?
Code: Select all
mysqlcheck -f -r -u <db_user> -p<db_pass> --databases nagios -h xxx.xxx.xxx.xxx
Sure he did, and while it's safe to run, it will lock tables and prevent updates while running the checks. Depending on the size of your system and whether or not there are data issues it could prevent updates for minutes.TBT wrote:I assume you meant nagios4, is this safe to run on a production system?
Code: Select all
mysqlcheck -f -r -u <db_user> -p<db_pass> --databases nagios4 -h xxx.xxx.xxx.xxxCode: Select all
ulimit -a
ipcs -qCode: Select all
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 30488
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 30488
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Code: Select all
------ Message Queues --------
key msqid owner perms used-bytes messages
0xf5000002 8814592 nagios 600 0 0
Code: Select all
slow_query_log=1
slow_query_log_file=/var/log/mysql_slow.log