Page 3 of 3

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

Posted: Fri Oct 11, 2019 4:16 pm
by scottwilkerson
So there you have it, socket timeout on 443
nickanderson1982 wrote:Redirection to https://prod1.yyyy.com:443/api/api.asmx
CRITICAL - Socket timeout

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

Posted: Fri Oct 11, 2019 4:17 pm
by scottwilkerson
Is port 443 (SSL) enabled on the server it is redirecting to?

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

Posted: Tue Oct 15, 2019 9:36 am
by nickanderson1982
Yes the api services have ssl enabled. I'm struggling to determine how to fix this. Is it the secondary dns server causing this? Because the only change is the AD/Witness server restarting and the secondary dns server taking over until the AD/Witness server finishes rebooting.

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

Posted: Tue Oct 15, 2019 10:12 am
by scottwilkerson
nickanderson1982 wrote:Yes the api services have ssl enabled. I'm struggling to determine how to fix this. Is it the secondary dns server causing this? Because the only change is the AD/Witness server restarting and the secondary dns server taking over until the AD/Witness server finishes rebooting.
Based on what you have posted (not actually seeing everything) it would appear that the backup server that you get directed to isn't setup properly on SSL. I say this because the redirect is working correctly and it is failing after being redirected.

the only way to confirm this would be to take down the primary again and try to reach this URL from another server (not the Nagios server) while it is down and the Nagios check is failing

Code: Select all

https://prod1.yyyy.com:443/api/api.asmx

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

Posted: Tue Oct 22, 2019 8:50 am
by nickanderson1982
I'm still working this issue, will have a response soon.

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

Posted: Tue Oct 22, 2019 8:53 am
by scottwilkerson
nickanderson1982 wrote:I'm still working this issue, will have a response soon.
sounds good