Nagios Support Forum

Hello,

Please see picture attached. I'm trying to track down what is causing these errors.

I've reach out to my Exchange admins and they are telling me there is nothing wrong with OWA on the servers listed in the screenshot. I'm not seeing anything in the logs or in event viewer on the servers themselves.

Please assist. Thank you.

Hi @rferebee,

Can you post or take a screen shot of the check command for this service?

Determining Check Command
You will need to go through a few steps to establish what exactly is being run. Grab some paper to note settings as you go.
Start by going to Configure > Core Config Manager.
Under Monitoring > Services in the left sidebar, find the service in question, and click the crossed tools Configure icon
On the Common Settings tab, note what it says for Command view and the values of the eight ARG variables

Documentation: Nagios XI - How To Test Check Commands From The Command-line
https://support.nagios.com/kb/article.p ... ategory=44

Thank you.

See attached screenshot.

Here's the full command from the $ARG1$ field:

-H ccexch01.state.nv.us -f ok -I 10.131.10.48 -u "/exchange/" -S

Thank you!

Hi @rferebee,

Try setting the value for $ARG1$ = -f ok -I 10.131.10.48 -u "/exchange/" -S -p 443, and then select the Run Check Command button.

If that doesn't work, please test it from the command line. Log in as root and from /usr/local/nagios/libexec run the command. The check_http Plugin
https://www.monitoring-plugins.org/doc/ ... _http.html

Ok, changing the argument and testing from the CLI returns the same error:

HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 6748 bytes in 0.032 second response time |time=0.032329s;;;0.000000 size=6748B;;;0

It could be that there is actually a problem, but I'm not sure what the error is describing and my Google-fu seems to not be very powerful on this subject.

Hi @rferebee,

The plugin is working from Nagios as it's returning a critical status along with performance data. You may have a configuration issue on your Exchange Server and I would recommend viewing the log files.

This issue has been resolved and the thread can be locked. Thank you.

This issue has been resolved and the thread can be locked. Thank you.

Thanks for the update. Closing thread.