After Upgrade - XI System Component Status

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
bosecorp
Posts: 929
Joined: Thu Jun 26, 2014 1:00 pm

After Upgrade - XI System Component Status

Post by bosecorp »

After upgrading the XI System component status wont show the status anymore of the first three

it;s that they are in a UNKNOWN STATE

But nagios seems to be running fine
jomann
Development Lead
Posts: 611
Joined: Mon Apr 22, 2013 10:06 am
Location: Nagios Enterprises

Re: After Upgrade - XI System Component Status

Post by jomann »

What operating system are you running on? Are they red status right now? There is a cron that runs that will check for the proper status of those processes. There should be a log in /usr/local/nagiosxi/var/sysstat.log - and if you hover over the icons what does it say in the tooltip?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
bosecorp
Posts: 929
Joined: Thu Jun 26, 2014 1:00 pm

Re: After Upgrade - XI System Component Status

Post by bosecorp »

UNKNOWN

[min_latency] => 0
[max_latency] => 1.68304
[avg_latency] => 0.03005778829604135
[min_execution_time] => 0.00159
[max_execution_time] => 10.01711
[avg_execution_time] => 0.22565664371772803
)

[activeservicecheckperf] => Array
(
[min_latency] => 0
[max_latency] => 1.7786
[avg_latency] => 0.03480955804804548
[min_execution_time] => 0
[max_execution_time] => 62.78395
[avg_execution_time] => 1.2129244211936006
)

)
LOAD:
Array
(
[load1] => 10.51
[load5] => 20.13
[load15] => 17.34
)
MEMORY:
Array
(
[total] => 122710
[used] => 5923
[free] => 17480
[shared] => 4187
[buffers] => 99306
[cached] => 111662
)
SWAP:
Array
(
[total] => 0
[used] => 0
[free] => 0
)
jomann
Development Lead
Posts: 611
Joined: Mon Apr 22, 2013 10:06 am
Location: Nagios Enterprises

Re: After Upgrade - XI System Component Status

Post by jomann »

Here try this, this should show the last run of the commands that check if the services are running:

Code: Select all

cat /usr/local/nagiosxi/var/sysstat.log | grep DAEMONS -C 25 | tail -38
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
bosecorp
Posts: 929
Joined: Thu Jun 26, 2014 1:00 pm

Re: After Upgrade - XI System Component Status

Post by bosecorp »

cat /usr/local/nagiosxi/var/sysstat.log | grep DAEMONS -C 25 | tail -38
Jul 13 15:34:56 usvanagiospxi3 ndo2db[123203]: Trimming timedevents.
Jul 13 15:34:56 usvanagiospxi3 ndo2db[123203]: Trimming systemcommands.
Jul 13 15:34:56 usvanagiospxi3 ndo2db[123203]: Trimming servicechecks.
Jul 13 15:34:56 usvanagiospxi3 ndo2db[123203]: Trimming hostchecks.
Jul 13 15:34:56 usvanagiospxi3 ndo2db[123203]: Trimming eventhandlers.
Jul 13 15:35:57 usvanagiospxi3 ndo2db[123203]: Trimming timedevents.
Jul 13 15:35:57 usvanagiospxi3 ndo2db[123203]: Trimming systemcommands.
Jul 13 15:35:57 usvanagiospxi3 ndo2db[123203]: Trimming servicechecks.
Jul 13 15:35:57 usvanagiospxi3 ndo2db[123203]: Trimming hostchecks.
Jul 13 15:35:57 usvanagiospxi3 ndo2db[123203]: Trimming eventhandlers.
OUTPUT=Jul 13 15:35:57 usvanagiospxi3 ndo2db[123203]: Trimming eventhandlers.
RETURNCODE=0
DAEMONS:
Array
(
[nagioscore] => Array
(
[daemon] => nagios
[output] => Jul 13 15:35:43 usvanagiospxi3 nagios[123195]: job 6083 (pid=127932): read() returned error 11
[return_code] => 0
[status] => 0
)

[pnp] => Array
(
[daemon] => npcd
[output] => └─62879 /usr/local/nagios/bin/npcd -d -f /usr/local/nagios/etc/pnp/npcd.cfg
[return_code] => 0
[status] => 0
)

[ndoutils] => Array
(
[daemon] => ndo2db
[output] => Jul 13 15:35:57 usvanagiospxi3 ndo2db[123203]: Trimming eventhandlers.
[return_code] => 0
[status] => 0
)
root@usvanagiospxi3:(07-13 11:09): /etc/snmp
#
npolovenko
Support Tech
Posts: 3457
Joined: Mon May 15, 2017 5:00 pm

Re: After Upgrade - XI System Component Status

Post by npolovenko »

@bosecorp, Please go to:

Code: Select all

/usr/local/nagiosxi/scripts/
And run:

Code: Select all

reset_config_perms.sh
After that:

Code: Select all

service crond restart
Also, rebooting the server can help here as well.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
bosecorp
Posts: 929
Joined: Thu Jun 26, 2014 1:00 pm

Re: After Upgrade - XI System Component Status

Post by bosecorp »

it didnt work

action the actions button doesnt work either. the one next to the status icon.
jomann
Development Lead
Posts: 611
Joined: Mon Apr 22, 2013 10:06 am
Location: Nagios Enterprises

Re: After Upgrade - XI System Component Status

Post by jomann »

Is it possible to run the following command on your nagiosxi database?

Code: Select all

SELECT * FROM nagiosxi.xi_sysstat WHERE metric = 'daemons';
I would like to see exactly what sysstat is grabbing. From the log you posted it looks like it should be showing up properly.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
bosecorp
Posts: 929
Joined: Thu Jun 26, 2014 1:00 pm

Re: After Upgrade - XI System Component Status

Post by bosecorp »

MariaDB [(none)]> SELECT * FROM nagiosxi.xi_sysstat WHERE metric = 'daemons';
+------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| sysstat_id | metric | value | update_time |
+------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| 20 | daemons | a:3:{s:10:"nagioscore";a:4:{s:6:"daemon";s:6:"nagios";s:6:"output";s:92:"Jul 16 14:34:20 usvanagiospxi3 nagios[54195]: job 2926 (pid=54390): read() returned error 11";s:11:"return_code";i:0;s:6:"status";i:0;}s:3:"pnp";a:4:{s:6:"daemon";s:4:"npcd";s:6:"output";s:90:" ??62879 /usr/local/nagios/bin/npcd -d -f /usr/local/nagios/etc/pnp/npcd.cfg";s:11:"return_code";i:0;s:6:"status";i:0;}s:8:"ndoutils";a:4:{s:6:"daemon";s:6:"ndo2db";s:6:"output";s:69:"Jul 16 14:33:58 usvanagiospxi3 ndo2db[54198]: Trimming eventhandlers.";s:11:"return_code";i:0;s:6:"status";i:0;}} | 2018-07-16 14:34:21 |
+------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
1 row in set (0.00 sec)

MariaDB [(none)]>
jomann
Development Lead
Posts: 611
Joined: Mon Apr 22, 2013 10:06 am
Location: Nagios Enterprises

Re: After Upgrade - XI System Component Status

Post by jomann »

All normal, can you send us a profile or the apache error log from /var/log/error_log ? It looks like XI is not able to find this data, which is strange. It shows up properly in the DB so the next step is to figure out if it's not displaying correctly due to PHP errors.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked