Reports section on side bar

[jdalrymple]

Sorry, coming in a bit late and a bit fuzzy. I feel like we didn't ask you to properly clarify the problem.

So reports in core are done by reading through the flat files. If you have a big environment this can take a devastatingly long time. It is what it is, can't really be fixed easily. Often times apache will timeout the CGI prior to the results finishing processing. This is easily fixed by adjusting the apache timeout directive:

http://httpd.apache.org/docs/current/mo ... ml#timeout

This can be verified by looking in the httpd error_log which is the original direction this thread headed, but it seemed to veer way out in left field.

Does it seem like that could be the problem?

A good reference thread:

https://support.nagios.com/forum/viewto ... he+timeout

[eloyd]

How many hosts and services are you monitoring?

[tmcdonald]

Thanks @eloyd and @jdalrymple!

OP, keep in touch!

[sinkak]

How many hosts and services are you monitoring?

35 hosts and around 700 services

[eloyd]

Then I do not believe you are looking at a timeout issue caused by Nagios needing lots of time to create the report. Something else is going on.

[sinkak]

timeout in apache2.conf

Code: Select all

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

its already 5 min. do i have to increase more than that?

[eloyd]

No. Something else is going on that is causing Apache to time out. If you want to try it, just to prove it, set that to 600, which is ten minutes. I'm willing to bet it will still timeout.

It is possible for you to recompile your Nagios binaries and reinstall them? I wonder if they did not get created correctly in the first place. Were they made on this machine or made somewhere else and moved to this machine?

[hsmith]

Thanks Eric. Let us know what you come up with @sinkak.

[sinkak]

I installed new version of nagios on new server but copied old nagios config files and scripts and made changes to the conf files accordingly.

changed timeout to 600 still same error.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.
Apache/2.4.7 (Ubuntu) Server at xx.xx.xx.xx Port 80

[eloyd]

I have a hunch you have an Apache problem, not a Nagios problem at this point. I'd really look closely at the /var/log/httpd/error_log for more information.