Nagios Support Forum

Hi Team,
We are facing an issue that availability report is taking nearly 10 minutes to display. Please find below the system profile.

/etc/php.ini
max_execution_time = 400 ; Maximum execution time of each script, in seconds
max_input_time = 400 ; Maximum amount of time each script may spend parsing request data
memory_limit = 512M ; Maximum amount of memory a script may consume

That error is often related to the output_buffering directive in /etc/php.ini. It appears the default in CentOS 6 is 4096. Try increasing that.

Your system is very large, so I'm not surprised it takes some time to run reports. What amount of time are you trying to run in the report? What I mean is, what option is selected in "Period" from the report screen?

Hi dwhitfield,
We have disable the auto load for availability reports. But when we run availability reports, it takes neraly 8-10 minutes to load the reports.
Increased the output buffering to 8192 but still its behaving same way.
Checking for the period 24 hours.

Was there recently a change in this? With your size of system, that does not seem that long to me.

Generate a report. While the report is running, generate a profile and either post it or PM it. You can download it by going to Admin > System Config > System Profile and click the ***Download Profile*** button towards the top. If for whatever reason you *cannot* download the profile, please put the output of View System Info (5.3.4+, Show Profile if older) in the thread (that will at least get us some info). This will give us access to many of the logs we would otherwise ask for individually. If security is a concern, you can unzip the profile take out what you like, and then zip it up again. We may end up needing something you remove, but we can ask for that specifically.

After you PM the profile, please update this thread. Updating this thread is the only way for it to show back up on our dashboard.

Hi dwhitfield,
I have had already posted the profile in my first question. Please correct me if i did not understand what you are asking from me?

what type of report are you attempting to run, and with how much data? this is expected, depending on your query, because SQL is only single threaded. you may want to reduce the history of your alert if possible.

sarfarosh wrote:Hi dwhitfield,
I have had already posted the profile in my first question.

Yes, but that was before you made the change I suggested. Be sure the profile is generated while the report is running.