This is a cache of https://support.nagios.com/kb/article/nagios-xi-troubleshooting-reports-829.html. It is a snapshot of the page at 2025-05-12T01:12:26.698+0000.
Nagios <strong>xi</strong> - Troubleshooting Reports
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!

0 (0)
Article Rating (No 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 - Debugging Bandwidth Performance Graphs
Viewed 15972 times since Tue, Jan 27, 2015
Nagios xi - Uploaded plugin returns "/bin/bash^M: bad interpreter: No such file or directory"
Viewed 7400 times since Thu, Feb 25, 2016
SSL Certificate does not validate properly
Viewed 5358 times since Wed, Jan 20, 2021
Nagios xi - Core Configuration Mananger Display Issues
Viewed 5072 times since Tue, Jan 26, 2016
Nagios xi - Common Upgrade Failures And Solutions
Viewed 14548 times since Thu, Jun 29, 2017
Nagios xi - Defining Global Environment Variables
Viewed 10865 times since Thu, Mar 17, 2016
Nagios xi - Upgrade errors - root.crontab.orig: cannot overwrite existing file
Viewed 4758 times since Tue, Jan 26, 2016
NDOUtils - Message Queue Exceeded
Viewed 16412 times since Thu, Jan 21, 2016
Nagios xi - How To Use CA Certificates With check_ldaps Plugin
Viewed 12597 times since Tue, Jul 26, 2016
Nagios xi - Login Screen Keeps Redirecting To Itself
Viewed 7408 times since Wed, Jan 27, 2016