AD/Witness Server Restart : Critical Alarm for URL Checks

An open discussion forum for obtaining help with Nagios Core. Nagios Core users of all experience levels are welcome here. Subforum have been created for the discussion of Nagios Core and Nagios Plugin development.

NOTE: The SourceForge.net mailing lists have been deprecated in favor of this forum in order to expedite support and provide additional features not available on the old mailing list.

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby nickanderson1982 » Thu Oct 10, 2019 2:33 pm

I'm going to PM the information I have
nickanderson1982
 
Posts: 57
Joined: Wed Feb 06, 2019 3:22 pm

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby scottwilkerson » Thu Oct 10, 2019 3:15 pm

Based on what you sent prod1.yyyy.com always resolves to the same IP address, this doesn't show what happens when the server at that IP address fails to respond
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 16263
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby nickanderson1982 » Thu Oct 10, 2019 4:07 pm

I'm working with some third party on this and they stated the following:
That sounds like he is asking for information from the device that is hosting the site (Devices APIServerA and APIServerB). However the problem is that the site isn't going down during this issue. Nagios only thinks it is.

Can you explain what you want from us so we can help you figure this out?
nickanderson1982
 
Posts: 57
Joined: Wed Feb 06, 2019 3:22 pm

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby scottwilkerson » Fri Oct 11, 2019 6:26 am

When the site goes down I'm assuming the DNS changes from xxx.xxx.xxx.xxx to yyy.yyy.yyy.yyy

Does this happen? And if so, then I need to see that the Nagios server is making the request to yyy.yyy.yyy.yyy and then as a followup that yyy.yyy.yyy.yyy is returning the expected result.

Nagios works by calling plugins that interact with the destination servers, and if it doesn't go to the correct server, that would be a problem for Nagios the same way it would be a problem for your users.

Nagios gives results based on it calling commands that you define, and in this example making a call to a website that you define, based on the command definition and arguments you pass to it.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 16263
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby nickanderson1982 » Fri Oct 11, 2019 2:28 pm

PM-ing you what the third party responded with.
nickanderson1982
 
Posts: 57
Joined: Wed Feb 06, 2019 3:22 pm

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby scottwilkerson » Fri Oct 11, 2019 2:40 pm

The errors you are seeing are from the URL Status service

Can you post the command definition for the check_service_http command
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 16263
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby nickanderson1982 » Fri Oct 11, 2019 2:58 pm

I have it listed under my commands cfg file

define command {
command_name check_service_http
command_line $USER1$/check_http -H $HOSTADDRESS$ $ARG1$
}
nickanderson1982
 
Posts: 57
Joined: Wed Feb 06, 2019 3:22 pm

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby scottwilkerson » Fri Oct 11, 2019 3:05 pm

When you reboot the server next time you can run the following from the Nagios Server CLI as many times as you want for verbose output of the command that is failing

Code: Select all
/usr/local/nagios/libexec/check_http -H prod1.yyyy.com -f follow -u '/api/api.asmx' -vvv


This is the exact command nagios is running based on the config fragments you have posted, but we added -vvv to get verbose output
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 16263
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby nickanderson1982 » Fri Oct 11, 2019 4:09 pm

Ran the following command provided. While down we were on the secondary dns also.

The output when AD down restarting:
[root@]# /usr/local/nagios/libexec/check_http -H prod1.yyyyy.com -f follow -u '/api/api.asmx' -vvv
GET /api/api.asmx HTTP/1.1
User-Agent: check_http/v2.2.1.git (nagios-plugins 2.2.1)
Connection: close
Host: prod1.yyyy.com
Accept: */*


http://prod1.yyyy.com:80/api/api.asmx is 137 characters
STATUS: HTTP/1.0 301 Moved Permanently
**** HEADER ****
location: https://prod1.yyyyy.com/api/api.asmx
Server: BigIP
Connection: close
Content-Length: 0
**** CONTENT ****

Redirection to https://prod1.yyyy.com:443/api/api.asmx
CRITICAL - Socket timeout
nickanderson1982
 
Posts: 57
Joined: Wed Feb 06, 2019 3:22 pm

Re: AD/Witness Server Restart : Critical Alarm for URL Check

Postby nickanderson1982 » Fri Oct 11, 2019 4:14 pm

Additional Info when working properly:
[root@]# /usr/local/nagios/libexec/check_http -H prod1.yyyy.com -f follow -u '/api/api.asmx' -vvv
GET /api/api.asmx HTTP/1.1
User-Agent: check_http/v2.2.1.git (nagios-plugins 2.2.1)
Connection: close
Host: prod1.yyyy.com
Accept: */*


http://prod1.yyyy.com:80/api/api.asmx is 137 characters
STATUS: HTTP/1.0 301 Moved Permanently
**** HEADER ****
location: https://prod1.yyyy.com/api/api.asmx
Server: BigIP
Connection: close
Content-Length: 0
**** CONTENT ****

Redirection to https://prod1.yyyy.com:443/api/api.asmx
SSL initialized
GET /api/api.asmx HTTP/1.1
User-Agent: check_http/v2.2.1.git (nagios-plugins 2.2.1)
Connection: close
Host: prod1.yyyy.com
Accept: */*


https://prod1.yyyy.com:443/api/api.asmx is 28695 characters
STATUS: HTTP/1.1 200 OK
**** HEADER ****
Cache-Control: private, max-age=0
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
X-Robots-Tag: noindex
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: accept, content-type, soapaction
Access-Control-Request-Method: POST
Date: Fri, 11 Oct 2019 21:12:25 GMT
Connection: close
Content-Length: 28223
Strict-Transport-Security: max-age=16070400; includeSubDomains
X-Frame-Options: SAMEORIGIN
**** CONTENT ****
<html>
-
</body>
</html>

HTTP OK: HTTP/1.1 200 OK - 28695 bytes in 0.012 second response time |time=0.011678s;;;0.000000 size=28695B;;;0
nickanderson1982
 
Posts: 57
Joined: Wed Feb 06, 2019 3:22 pm

PreviousNext

Return to Nagios Core

Who is online

Users browsing this forum: sgopalakrishnan and 28 guests