THIS KNOWLEDGE BASE HAS BEEN ARCHIVED AND IS NO LONGER BEING UPDATED
Please visit library.nagios.com/docs for the latest and most up-to-date documentation.
Home » Categories » Products » Nagios XI » Troubleshooting » Common Problems

Nagios XI - Troubleshooting Reports

Overview

This KB article explains how to troubleshoot problems with reports taking a long time to run on your Nagios XI server.

 

 

Check Log Files

When you are experiencing issues with reports the first step is to analyze the log files for the Apache web server. Establish a terminal session to your Nagios XI server and execute the following command:

tail -f /var/log/httpd/error_log /var/log/httpd/ssl_error_log

 

This display the last few errors that may have occurred and any new ones. You should try and run the report which is taking a long time and observe any log entries that are displayed. Use this log data to help you with the remaining steps in this KB article.

Press CTRL + C to stop the log file from being watched.

 

 

Report Is Exhausting PHP Limits

A common cause with larger reports is that the php.ini file has limits imposed on it to prevent malious attacks which may cause a web server to crash. These same safety measures may also restrict larger reports from running.

The solution is to review the following KB article and edit the php.ini file to increase the max_execution, max_input, and memory variables.

Nagios XI - Optimizing The PHP Settings File

Once you have performed the changes try to re-run the Report and see if this fixes the problem. You may need to increase the values several times to find the right values, this all depends on the size of the report.

 

 

Nagios XI Program URL Is Invalid

Another reason why a report may not run is if the URL defined for the Nagios XI interface is not correct. This may be because an internal DNS record might not be resolvable when being access from the outside world, or perhaps it is spelt incorrectly.

Navigate to Admin > System Config > System Settings and review the Program URL and External URL options. Ensure there is a trailing forward slash (/) after the URL, for example:

http://<xi_server_address>/nagiosxi/

 

 

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/



Special Offer For Knowledgebase Visitors! Get a huge discount on Nagios Log Server by clicking below.

Get 60% Off Nagios Log Server!

Did you know? Nagios provides complete monitoring of: Windows, Linux, UNIX, Servers, Websites, SNMP, DHCP, DNS, Email, Storage, Files, Apache, IIS, EC2, and more!

1 (2)
Article Rating (2 Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Nagios XI - Empty Screen for Wizard, Component, Dashlet
Viewed 10174 times since Wed, Jan 27, 2016
Nagios XI - Scheduled Backups No Longer Working
Viewed 10881 times since Fri, Jun 3, 2016
Nagios XI - Uploaded plugin returns "/bin/bash^M: bad interpreter: No such file or directory"
Viewed 10450 times since Thu, Feb 25, 2016
Nagios XI - ERROR: PostgresQL not running - exiting
Viewed 6964 times since Tue, Jan 26, 2016
Nagios XI - Scheduled Backup Log Level
Viewed 7606 times since Tue, Apr 18, 2017
Nagios XI - Optimizing The PHP Settings File
Viewed 72691 times since Thu, Jul 13, 2017
Nagios XI - How To Test Check Commands From The Command-line
Viewed 56188 times since Tue, Jan 26, 2016
Nagios XI - Can’t Log Into The Web Interface
Viewed 69169 times since Tue, Jan 27, 2015
Nagios XI - Apply Configuration Never Completes
Viewed 25934 times since Tue, Jan 27, 2015
Upgrading to NDO 3 after having been downgraded in newer versions of Nagios XI
Viewed 6152 times since Fri, Jan 15, 2021