Service with no CCM entry and no info showing

[GldRush98]

As far as I can tell the "Service Status" screen is the only place this exists, but I can't get it to go away.

85 Services is incorrect (the ghost service is the first one on this screen, you can see it has no host or name!)

ghost1.PNG

This server only has 84 services on it:

ghost2.PNG

I have:
+Config File Management -> Delete -> Write -> Verify -> Restart Nagios
+Rebooted the server
+Checked the MariaDB database (only shows 84 rows in the services table).

So I'm not sure where this mystery service is coming from. It looks like a copy of the CentOS machine's disk usage from a couple weeks ago, but I can't seem to get it to go away.

[GldRush98]

I found it. There is a nagios_servicestatus entry with a service_object_id of -1!

Code: Select all

MariaDB [nagios]> select * from nagios_servicestatus where service_object_id=-1;
+------------------+-------------+-------------------+---------------------+-----------------------------------------------------------------------------------------+-------------+--------------------------------------------------------------+---------------+------------------+---------------------+-----------------------+--------------------+---------------------+---------------------+------------+---------------+---------------------+------------------------+-----------------+---------------------+---------------------+---------------------+---------------------+------------+---------------------+---------------------+-----------------------+-----------------------+-------------------------------+----------------------+-----------------------------+------------------------+-----------------------+-----------------------+------------------------+-------------+----------------------+----------------------+----------------+--------------------------+----------------------------+--------------------------+---------------------+-----------------------------+---------------+--------------------------------------------------------------------------------------+-----------------------+----------------------+----------------------------+
| servicestatus_id | instance_id | service_object_id | status_update_time  | output                                                                                  | long_output | perfdata                                                     | current_state | has_been_checked | should_be_scheduled | current_check_attempt | max_check_attempts | last_check          | next_check          | check_type | check_options | last_state_change   | last_hard_state_change | last_hard_state | last_time_ok        | last_time_warning   | last_time_unknown   | last_time_critical  | state_type | last_notification   | next_notification   | no_more_notifications | notifications_enabled | problem_has_been_acknowledged | acknowledgement_type | current_notification_number | passive_checks_enabled | active_checks_enabled | event_handler_enabled | flap_detection_enabled | is_flapping | percent_state_change | latency              | execution_time | scheduled_downtime_depth | failure_prediction_enabled | process_performance_data | obsess_over_service | modified_service_attributes | event_handler | check_command                                                                        | normal_check_interval | retry_check_interval | check_timeperiod_object_id |
+------------------+-------------+-------------------+---------------------+-----------------------------------------------------------------------------------------+-------------+--------------------------------------------------------------+---------------+------------------+---------------------+-----------------------+--------------------+---------------------+---------------------+------------+---------------+---------------------+------------------------+-----------------+---------------------+---------------------+---------------------+---------------------+------------+---------------------+---------------------+-----------------------+-----------------------+-------------------------------+----------------------+-----------------------------+------------------------+-----------------------+-----------------------+------------------------+-------------+----------------------+----------------------+----------------+--------------------------+----------------------------+--------------------------+---------------------+-----------------------------+---------------+--------------------------------------------------------------------------------------+-----------------------+----------------------+----------------------------+
|              105 |           1 |                -1 | 2021-04-29 18:27:10 | OK: Used disk space was 46.80 % (Used: 221.10 GiB, Free: 250.95 GiB, Total: 472.05 GiB) |             | 'used'=221.10GiB;;; 'free'=250.95GiB;;; 'total'=472.05GiB;;; |             0 |                1 |                   1 |                     1 |                  5 | 2021-04-29 18:27:08 | 2021-04-29 18:32:08 |          0 |             0 | 2021-04-10 23:12:54 | 2021-04-10 23:12:54    |               0 | 2021-04-29 18:27:08 | 1969-12-31 18:00:00 | 2021-03-15 01:07:53 | 2021-04-10 23:12:54 |          1 | 1969-12-31 18:00:00 | 1969-12-31 18:00:00 |                     0 |                     1 |                             0 |                    0 |                           1 |                      1 |                     1 |                     1 |                      1 |           0 |                    0 | 0.004637000150978565 |       1.697154 |                        0 |                          0 |                        1 |                   1 |                           0 |               | check_xi_ncpa!-t 'redacted' -P 5694 -M 'disk/logical/|' -w '80' -c '90'!!!!!!! |                     5 |                    1 |                        125 |
+------------------+-------------+-------------------+---------------------+-----------------------------------------------------------------------------------------+-------------+--------------------------------------------------------------+---------------+------------------+---------------------+-----------------------+--------------------+---------------------+---------------------+------------+---------------+---------------------+------------------------+-----------------+---------------------+---------------------+---------------------+---------------------+------------+---------------------+---------------------+-----------------------+-----------------------+-------------------------------+----------------------+-----------------------------+------------------------+-----------------------+-----------------------+------------------------+-------------+----------------------+----------------------+----------------+--------------------------+----------------------------+--------------------------+---------------------+-----------------------------+---------------+--------------------------------------------------------------------------------------+-----------------------+----------------------+----------------------------+
1 row in set (0.00 sec)

MariaDB [nagios]> delete from nagios_servicestatus where service_object_id=-1;
Query OK, 1 row affected (0.00 sec)

Well that's a weird one.
Thing is nothing happened on April 29th (the last date from that entry). No reconfigs, no updates applied, anything.
Bizarre.

[ssax]

I've seen this before, please run this command and then apply configuration to fix the issue:

Code: Select all

mysql -uroot -pnagiosxi nagios -e "delete from nagios_servicestatus where service_object_id = '-1';"

If you see it again (not sure you will), I would downgrade your NDO3 to NDO2DB (your XI version stays the same) following the guide below as you're likely hitting a bug in the new NDO3:

Run these commands as root:

Code: Select all

systemctl stop nagios
cd /tmp
rm -rf /tmp/nagiosxi
wget https://assets.nagios.com/downloads/nagiosxi/5/xi-5.6.14.tar.gz
tar zxf xi-5.6.14.tar.gz
cd /tmp/nagiosxi
./init.sh
cd /tmp/nagiosxi/subcomponents/ndoutils
./install
systemctl enable ndo2db

If you have an offloaded database you will need to edit your /usr/local/nagios/etc/ndo2db.cfg file and update these before running the next command to start it up:
- You can get the info from your /usr/local/nagios/etc/ndo.cfg or from /usr/local/nagiosxi/html/config.inc.php

db_host
db_port
db_user
db_pass

Then run this command to start it up.:

Code: Select all

systemctl start ndo2db

Then edit your /usr/local/nagios/etc/nagios.cfg and make sure this line is uncommented/add it if needed:

Code: Select all

broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg

Make sure all occurrences of this line are commented:

Code: Select all

#broker_module=/usr/local/nagios/bin/ndo.so /usr/local/nagios/etc/ndo.cfg

Then start the nagios service:

Code: Select all

systemctl start nagios