Nagios Support Forum

max_execution_time = 60     ; Maximum execution time of each script, in  seconds
max_input_time = 60     ; Maximum amount of time each script may spend parsing request data
memory_limit = 256M      ; Maximum amount of memory a script may consume 

service httpd restart

My Management would like to schedule the reports to be automatically send every month to nearly 90 Customers.

kyang wrote:You can try increasing the php values in the /etc/php.inifile.
Try doubling the values that you have for these 3 fields.

Code: Select all

max_execution_time = 60     ; Maximum execution time of each script, in  seconds
max_input_time = 60     ; Maximum amount of time each script may spend parsing request data
memory_limit = 256M      ; Maximum amount of memory a script may consume 

Then restart apache.

Code: Select all

service httpd restart

My Management would like to schedule the reports to be automatically send every month to nearly 90 Customers.

Do you have these scheduled reports sending right now? Is it 90 reports at one time? Or is the time when it's sent separate from each other?

tgriep wrote:The Availability Report uses a mixture of PHP and a cgi script to generate the data so increasing the settings in the php.ini file will help out in the performance.

The failure to create the PDF file could be caused by the External URL settings in the Admin > System Settings menu.
If it is set, make sure the hostname in the field is correct and that the name is resolvable in DNS.
Or, you can use the IP address in place of the host name and see if that helps.

If not, if you can post the error, that would help out in troubleshooting the issue.

by tmcdonald
So a few things:

• I do believe your issue has to do with the number of objects being monitored, as 20k checks is usually the most I recommend for a single XI server for just this reason. Especially if your checks are running on average more than once every 5 minutes, you are going to see a lot of historical data that the reports need to dig through.
• You can somewhat mitigate the timeouts by increasing some PHP limits:
  

  Code: Select all

  max_execution_time = 60     ; Maximum execution time of each script, in  seconds
  max_input_time = 60     ; Maximum amount of time each script may spend parsing request data
  memory_limit = 256M      ; Maximum amount of memory a script may consume 

  but even that will only get you so far, and will not help too much with the speed.
  
  As for the original issue itself, we now generate reports using AJAX so the timeouts should not be due to any hanging on the frontend. It still may take a long time, but as long as your PHP settings in /etc/php.ini are high enough it should eventually complete. It's basically now just a "too much data" issue causing the slowness.
  
  We do have a developer here who has a caching component for reports in the works that should help a bit, but it will not be available until 5.3.0. I won't have many more details until then, unfortunately.