Are you facing Core Configuration Manager Displaying Issues in Nagios XI?
This guide will help you.
Sometimes our customers using Nagios XI report that while using Core Configuration Manager (CCM) they face issues. Generally, it will be an issue with the interface or likely caused by a bug.
Basically, Nagios XI is a powerful server and network monitoring solution for any kind of server, application, web-service, or network. Also, it provides monitoring of all mission-critical infrastructure components.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to resolve issues regarding Nagios XI.
How to fix Core Configuration Manager Displaying Issues in Nagios XI ?
This error usually arises due to the web browser’s implementation of JavaScript. It is better to use a browser that more closely implements the ECMAScript Language Specification.
We can use the following steps to fix this issue:
Often with Nagios XI, we can see that the Core Config Manager not visible or some components are missing from the page.
Generally, this relates to a proxy issue.
i. Firstly, we can use the below command:
pear config-set http_proxy http://proxy:portii. Make sure to change proxy:port to match our proxy server, an example is given below:
pear config-set http_proxy http://192.168.44.20:8080iii. Then execute the following command:
pear install HTML_Template_ITAfter performing these steps, we can go back to CCM and check if it works.
[Need Assistance in fixing Nagios related errors? We are happy to help you! ]
Conclusion
This article covers how to resolve the issue with Nagios XI that stops displaying the core configuration manager or the components inside the core configuration manager.
If this is the case, When using Core Configuration Manager (CCM), the interface does not work as expected, it does not appear to display correctly and generally it feels like there is a bug. This issues is related to the web browsers implementation of JavaScript. If possible, use a browser that more closely implements the ECMAScript Language Specification.
A quick way to see if this is the problem is to see if you experience the same issue using another web browser.
To fix this Nagios configuration Problem:
1. In the event of the the Core Config Manager not visible or components missing from the page, this generally relates to a proxy and the following steps may resolve this issue:
pear config-set http_proxy http://proxy:port
2. Make sure to change proxy:port to match your proxy server, example:
pear config-set http_proxy http://192.168.44.20:8080
3. Then execute the following:
pear install HTML_Template_IT
After performing these steps go back to CCM and see if it works.
This article covers how to resolve the issue with Nagios XI that stops displaying the core configuration manager or the components inside the core configuration manager.
If this is the case, When using Core Configuration Manager (CCM), the interface does not work as expected, it does not appear to display correctly and generally it feels like there is a bug. This issues is related to the web browsers implementation of JavaScript. If possible, use a browser that more closely implements the ECMAScript Language Specification.
A quick way to see if this is the problem is to see if you experience the same issue using another web browser.
To fix this Nagios configuration Problem:
1. In the event of the the Core Config Manager not visible or components missing from the page, this generally relates to a proxy and the following steps may resolve this issue:
pear config-set http_proxy http://proxy:port
2. Make sure to change proxy:port to match your proxy server, example:
pear config-set http_proxy http://192.168.44.20:8080
3. Then execute the following:
pear install HTML_Template_IT
After performing these steps go back to CCM and see if it works.
