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 - Login Screen Keeps Redirecting To Itself
Viewed 8694 times since Wed, Jan 27, 2016
NDOUtils - Message Queue Exceeded
Viewed 18636 times since Thu, Jan 21, 2016
Nagios XI - Reset Upgrade Status In Web Interface
Viewed 13769 times since Tue, May 7, 2019
Disabling Port 113 IDENT Requests
Viewed 7775 times since Tue, Mar 12, 2019
Nagios XI - Core 4 Load Spikes on 1.75 and 7 Hour Intervals
Viewed 6045 times since Mon, Jan 25, 2016
XI 5.4 monitoring engine not running
Viewed 13593 times since Mon, Feb 6, 2017
Nagios XI - Resolving "Cannot connect to database" Error - Core Config Manager
Viewed 10149 times since Mon, Jan 25, 2016
Nagios XI - ICMP and Ping Checks Stopped Graphing
Viewed 16516 times since Mon, Jan 25, 2016
Nagios XI - Scheduled Backup Log Level
Viewed 7168 times since Tue, Apr 18, 2017
Nagios XI - SNMP MIB Upload Problems
Viewed 11570 times since Mon, Apr 10, 2017