I am using Nagios XI 2014R1.0 with RHEL 6.6 64bit. And we have to Nagios server as Active/Standby. On Server1 with Xi, the particular host, i can't open and see Host status detail. But I can open and see at Core. At second server, everything is fine.
XI:
Core:
Let me know how can i fix this issue.
PS. I can't update to latest version of Nagios XI because of maintenance license.
Currently I have monitored 45 hosts. Other 44 hosts are ok. I can see host status details for other 44 hosts. This host only i can't see the host status details.
I have attached the file of the output of the below command.
tail /var/log/httpd/error_log -n 100
You do not have the required permissions to view the files attached to this post.
I can see bunch of timezone issues in the error log. I don't think that this is causing the issue, but I would recommend that you fix this first. This will clear most of these errors.
I can see bunch of timezone issues in the error log. I don't think that this is causing the issue, but I would recommend that you fix this first. This will clear most of these errors. https://assets.nagios.com/downloads/nag ... m_Time.pdf
I already change all of the time zone setting according to Changing_The_XI_System_Time.pdf
[root@nagios01 httpd]# tail -20 /var/log/mysqld.log
150520 16:19:53 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1325' LIMIT 1
150520 16:20:04 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1326' LIMIT 1
150520 16:20:15 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1327' LIMIT 1
150520 16:20:24 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1328' LIMIT 1
150520 17:23:55 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1570' LIMIT 1
150520 17:23:55 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1571' LIMIT 1
150520 17:23:55 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1642' LIMIT 1
150520 17:23:55 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1641' LIMIT 1
150520 17:23:55 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1556' LIMIT 1
150520 17:23:55 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1557' LIMIT 1
150520 17:23:55 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1650' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1649' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1598' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1599' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1618' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1617' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1584' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1585' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1620' LIMIT 1
150520 17:23:56 [Warning] Statement may not be safe to log in statement format. Statement: DELETE FROM `tbl_service` WHERE `id`='1619' LIMIT 1
[root@nagios01 httpd]#
So far, i can't see the host details status for this host.
cd /usr/local/nagiosxi/scripts
./repair_databases.sh
Let us know if this fixes it for you.
Edit.
Are you using a database replication? If you do, you may want to turn it off for a while to see if the problem will go away. FYI, we don't support MYSQL replication for Nagios XI.
lmiltchev
Be sure to check out our Knowledgebase for helpful articles and solutions!
tgriep wrote:Are you using a database replication? If you do, you may want to turn it off for a while to see if the problem will go away. FYI, we don't support MYSQL replication for Nagios XI.
lmiltchev
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
tgriep wrote:Are you using a database replication? If you do, you may want to turn it off for a while to see if the problem will go away. FYI, we don't support MYSQL replication for Nagios XI.
lmiltchev
Previously we used. Now totally disable the replication.
Try going in to Core Config Manager and editing the host you cannot see in XI. Change the description, save it and apply the configuration to see if that updates the view.
Be sure to check out our Knowledgebase for helpful articles and solutions!