Nagios XI Frontend Problems

[SDK]

Hello all,

i have 2 very annoying problems with my Nagios XI Installation:

Version: 2012R1.6

If i reboot my server, all Hostgroup, Service Groups, basically all Groups show up empty in the Nagios XI Frontend

EmptyGroups.png

In Nagios the Groups are filled and work fine

FullGroups.png

The only solution is to restart the nagios service. Then the Groups are being populated



I tried to repair the Nagios Database as described in "Repairing_The_Nagios_XI_Database.pdf".
But since Nagios Core is working fine and the script repairs the Nagios Database, its not solving my problem!

Second Problem is the Tactical Overview:

The numbers that are shown under the Nagios XI Frontend are wrong:

NagiosXI TAC.png

Again in Nagios Core these numbers are completely different and correct.

So what can i do to correct these issues?

Kind Regards

SDK

[SDK]

Additional:

I just logged into the Nagios XI Online Demo.

The Tactical Overview there has the same issue. Maybe this is a general problem:

Nagios XI (wrong):

NagiosXI.png

Nagios Core (correct):

NagiosCore.png

When clicking on one that is incorrect in the Nagios XI TAC the link shows up empty:

Detail.png

Kind Regards

[scottwilkerson]

The TAC is a know bug we are working on, however the problem with the hostgroup being blank, this still sounds line a DB error.

Can you run the following while trying to access one of the hostgroup pages to see if any errors show up

Code: Select all

tail -f /var/log/mysqld.log

[SDK]

Hello Scott,

this is the output:

[root@]# tail -f /var/log/mysqld.log
130304 14:52:20 [Note] /usr/libexec/mysqld: Shutdown complete

130304 14:52:20 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
130304 14:52:54 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130304 14:52:55 InnoDB: Initializing buffer pool, size = 8.0M
130304 14:52:55 InnoDB: Completed initialization of buffer pool
130304 14:52:55 InnoDB: Started; log sequence number 0 44243
130304 14:52:55 [Note] Event Scheduler: Loaded 0 events
130304 14:52:55 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution

Regards

SDK

[lmiltchev]

Run the following commands:

Code: Select all

service nagios stop
killall -9 nagios
service ndo2db stop
service ndo2db start
service nagios start

Let us know if this solves your problem.

[SDK]

Run the following commands:

Code: Select all

service nagios stop
killall -9 nagios
service ndo2db stop
service ndo2db start
service nagios start

Let us know if this solves your problem.

Hi lmiltchev,

service nagios restart is enough in my case, the groups are filled after that. After a reboot i have the empty groups again.

Kind regards

SDK

[slansing]

Did you run the other commands ludmil suggested?

Code: Select all

service ndo2db stop
service ndo2db start

NDO2DB is not the same as the Nagios service, you should run both. Even though they come back when restarting Nagios as they control a different portion of the monitoring process..

[SDK]

Did you run the other commands ludmil suggested?

Code: Select all

service ndo2db stop
service ndo2db start

NDO2DB is not the same as the Nagios service, you should run both.

As i mentioned, restarting the nagios process alone is enough to make it work temporarily, no need to restart ndo2db. I executed the hole bulk of commands nonetheless.
Same result, after restart the Groups are empty.

I maybe found something. After i restart the server, the Nagios tables like "nagios_hosts" or "nagios_services" in the MySQL Database are completely empty. After i restart the nagios process they are filled. What's going on there?

Regards

SDK

[scottwilkerson]

Can you post the following 2 files
/usr/local/nagios/etc/ndomod.cfg
/usr/local/nagios/etc/ndo2db.cfg

[SDK]

Hi Scott,

here are the files:

ndo2db.cfg

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=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

ndomod.cfg

Code: Select all

#####################################################################
# NDOMOD CONFIG FILE
#####################################################################


# INSTANCE NAME
# This option identifies the "name" associated with this particular
# instance of Nagios and is used to seperate data coming from multiple
# instances.  Defaults to 'default' (without quotes).

instance_name=localhost



# OUTPUT TYPE
# This option determines what type of output sink the NDO NEB module
# should use for data output.  Valid options include:
#   file       = standard text file
#   tcpsocket  = TCP socket
#   unixsocket = UNIX domain socket (default)

#output_type=file
#output_type=tcpsocket
output_type=unixsocket



# OUTPUT
# This option determines the name and path of the file or UNIX domain 
# socket to which output will be sent if the output type option specified
# above is "file" or "unixsocket", respectively.  If the output type
# option is "tcpsocket", this option is used to specify the IP address
# of fully qualified domain name of the host that the module should
# connect to for sending output.

#output=/usr/local/nagios/var/ndo.dat
#output=127.0.0.1
output=/usr/local/nagios/var/ndo.sock



# TCP PORT
# This option determines what port the module will connect to in
# order to send output.  This option is only vlaid if the output type
# option specified above is "tcpsocket".

tcp_port=5668



# OUTPUT BUFFER
# This option determines the size of the output buffer, which will help
# prevent data from getting lost if there is a temporary disconnect from
# the data sink.  The number of items specified here is the number of
# lines (each of variable size) of output that will be buffered.

output_buffer_items=5000



# BUFFER FILE
# This option is used to specify a file which will be used to store the
# contents of buffered data which could not be sent to the NDO2DB daemon
# before Nagios shuts down.  Prior to shutting down, the NDO NEB module
# will write all buffered data to this file for later processing.  When
# Nagios (re)starts, the NDO NEB module will read the contents of this
# file and send it to the NDO2DB daemon for processing.

buffer_file=/usr/local/nagios/var/ndomod.tmp



# FILE ROTATION INTERVAL
# This option determines how often (in seconds) the output file is
# rotated by Nagios.  File rotation is handled by Nagios by executing
# the command defined by the file_rotation_command option.  This
# option has no effect if the output_type option is a socket.

file_rotation_interval=14400



# FILE ROTATION COMMAND
# This option specified the command (as defined in Nagios) that is
# used to rotate the output file at the interval specified by the
# file_rotation_interval option.  This option has no effect if the
# output_type option is a socket.
#
# See the file 'misccommands.cfg' for an example command definition
# that you can use to rotate the log file.

#file_rotation_command=rotate_ndo_log



# FILE ROTATION TIMEOUT
# This option specified the maximum number of seconds that the file
# rotation command should be allowed to run before being prematurely
# terminated.

file_rotation_timeout=60



# RECONNECT INTERVAL
# This option determines how often (in seconds) that the NDO NEB
# module will attempt to re-connect to the output file or socket if
# a connection to it is lost.

reconnect_interval=15



# RECONNECT WARNING INTERVAL
# This option determines how often (in seconds) a warning message will
# be logged to the Nagios log file if a connection to the output file
# or socket cannot be re-established.

#reconnect_warning_interval=15
reconnect_warning_interval=900



# DATA PROCESSING OPTION
# This option determines what data the NDO NEB module will process. 
# Do not mess with this option unless you know what you're doing!!!!
# Read the source code (include/ndbxtmod.h) to determine what values
# to use here.  Values from source code should be OR'ed to get the
# value to use here.  A value of -1 will cause all data to be processed.
# Read the source code (include/ndomod.h) and look for "NDOMOD_PROCESS_"
# to determine what values to use here.  Values from source code should
# be OR'ed to get the value to use here.  A value of -1 will cause all
# data to be processed. 

data_processing_options=67108669



# CONFIG OUTPUT OPTION
# This option determines what types of configuration data the NDO
# NEB module will dump from Nagios.  Values can be OR'ed together.
# Values: 
# 	  0 = Don't dump any configuration information
#         1 = Dump only original config (from config files)
#         2 = Dump config only after retained information has been restored
#         3 = Dump both original and retained configuration

config_output_options=2

Thanks a lot

SDK