Zevenet CE Health check (farmguardian) issue

[greg-kl]

Hello,

We have a new problem with verifying Exchange publications using health-checks. We publish Exchange using Microsoft Web Application Proxy (WAP) and use Zevenet Load Balancer to route network traffic to the WAP servers.
Here is an simple explanation how is the infrastructure configured:

We observe that a Health-Check result every few attempts on all publications results in a "CRITICAL - Socket timeout after 15 seconds" (timeout is configured for 15s) error which causes the publication to become unavailable and clients to disconnect until the next Health-check verification is successful. This is happening on marked DMZ Zevenet NLB Cluster. NLB and WAP are both in the same DMZ network.

Below are examples:

Example 1

Example 2 (after refresh)

We can reproduce non availability status by manual tests:
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 15
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.053 second response time |time=0.053404s;;;0.000000;15.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 15
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.064 second response time |time=0.064276s;;;0.000000;15.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 15
CRITICAL - Socket timeout after 15 seconds

System specs:
ZEVENET Community Edition

"params": {
"appliance_version": "ZCE 6, hypervisor: HyperV",
"edition": "community",
"hostname": "KWARV-LBZ01",
"kernel_version": "4.19.0-17-amd64",
"language": "",
"last_zapi_version": "4.0.1",
"platform": "nocloud",
"supported_zapi_versions": [
"3",
"3.1",
"3.2",
"4.0.1"
],
"system_date": "Wed Apr 20 11:19:49 2022",
"user": "root",
"zevenet_version": "5.11.2"

[emiliocampos-zevenet]

Thanks for the detailed explanation, it seems like the timeout of 15 seconds is not enough time to wait for the reply from the backend. So you should increase the timeout in the command and the time interval in the farmguardian definition taking into consideration that the interval value is: (the timeout configured in the check_http command (-t value) * the number of backends in the farm) + 1 second. Regards El mié, 20 abr 2022 a las 12:42, greg-kl ***@***.***>) escribió:

…

Hello, We have a new problem with verifying Exchange publications using health-checks. We publish Exchange using Microsoft Web Application Proxy (WAP) and use Zevenet Load Balancer to route network traffic to the WAP servers. Here is an simple explanation how is the infrastructure configured: [image: image] <https://user-images.githubusercontent.com/103255855/164211030-380e442c-de49-48fd-95eb-b103036efa20.png> We observe that a Health-Check result every few attempts on all publications results in a "CRITICAL - Socket timeout after 15 seconds" (timeout is configured for 15s) error which causes the publication to become unavailable and clients to disconnect until the next Health-check verification is successful. This is happening on marked DMZ Zevenet NLB Cluster. NLB and WAP are both in the same DMZ network. Below are examples: Example 1 [image: image] <https://user-images.githubusercontent.com/103255855/164213164-ed367f23-c163-4522-aef8-4169a4e2adb1.png> Example 2 (after refresh) [image: image] <https://user-images.githubusercontent.com/103255855/164213220-9497a16a-a2e8-4381-ac73-5cd8922c0ded.png> We can reproduce non availability status by manual tests: *[master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 15 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.053 second response time |time=0.053404s;;;0.000000;15.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 15 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.064 second response time |time=0.064276s;;;0.000000;15.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 15 CRITICAL - Socket timeout after 15 seconds* System specs: ZEVENET Community Edition "params": { "appliance_version": "ZCE 6, hypervisor: HyperV", "edition": "community", "hostname": "KWARV-LBZ01", "kernel_version": "4.19.0-17-amd64", "language": "", "last_zapi_version": "4.0.1", "platform": "nocloud", "supported_zapi_versions": [ "3", "3.1", "3.2", "4.0.1" ], "system_date": "Wed Apr 20 11:19:49 2022", "user": "root", "zevenet_version": "5.11.2" — Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPAWPJENTFSKEK2ETADVF7NSXANCNFSM5T3TPXHQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

Thank you for suggestions. I raised timeout up to 100s to measure real time of response and now I'm getting: HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout

[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.062 second response time |time=0.061959s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.066 second response time |time=0.065765s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.068181s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.068449s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.061 second response time |time=0.060556s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.052 second response time |time=21.051507s;;;0.000000;100.000000 size=165B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.066 second response time |time=0.065751s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.058 second response time |time=0.057824s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.065 second response time |time=0.064926s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.060 second response time |time=0.060193s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.045 second response time |time=21.044973s;;;0.000000;100.000000 size=165B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.063 second response time |time=0.062889s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.048 second response time |time=21.048028s;;;0.000000;100.000000 size=165B;;;0

it seems like Web Application Proxy might drop this request after 21s.

[emiliocampos-zevenet]

Could you let us know if the IP *10.1.8.71 is a Virtual IP configured in the load balancer? If so you have to use the backend IP instead because check_http is ready to be used against backends where the service is really. * *Thanks!* El mié, 20 abr 2022 a las 13:26, greg-kl ***@***.***>) escribió:

…

Thank you for suggestions. I raised timeout up to 100s to measure real time of response and now I'm getting: *HTTP CRITICAL: HTTP/1.1 504 Gateway Timeou*t *[master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.062 second response time |time=0.061959s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.066 second response time |time=0.065765s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.068181s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.068449s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.061 second response time |time=0.060556s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.052 second response time |time=21.051507s;;;0.000000;100.000000 size=165B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.066 second response time |time=0.065751s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.058 second response time |time=0.057824s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.065 second response time |time=0.064926s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.060 second response time |time=0.060193s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.045 second response time |time=21.044973s;;;0.000000;100.000000 size=165B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.063 second response time |time=0.062889s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm <https://poczta.wody.gov.pl/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.048 second response time |time=21.048028s;;;0.000000;100.000000 size=165B;;;0* it seems like Web Application Proxy might drop this request after 21s. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPGUBSNWUEMZHUNHBJDVF7SXVANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

This is backend IP (Web App Proxy node.), not a VIP on loadbalancer.

[emiliocampos-zevenet]

Thanks for the confirmation, the error "getting: *HTTP CRITICAL: HTTP/1.1 504 Gateway Timeou*t" then it means that the backend is configured with a minor timeout than the timeout you configured in the check_http of 100s, then you can do one of the two things. 1- Or change the connection timeout in the backends to 100s in order to avoid 504 gateway timeout 2- Or configure the same timeout in the check_http (currently to 100s) as the backend. But right now this issue is not related to the load balancer but with the backends timeout configuration, the only thing you have to take into consideration in the load balancer is to configure a proper timeout in the check_http and in the interval in order to allow to the farmguardian enough time to check all the backends. Regards El mié, 20 abr 2022 a las 13:41, greg-kl ***@***.***>) escribió:

…

This is backend IP (Web App Proxy node.), not a VIP on loadbalancer. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPAMII2AFR6L2OLIOTDVF7UNRANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

I will verify that and send back the results.

[greg-kl]

I did some health-check accessibility testing using MS Edge on windows client. The traffic from this workstation is directed to the "DMZ nlb cluster" to simulate an external connection. I performed 100 queries every 1 second. Each query ends with a status of 200. The same attempt without a single "timeout" error from the loadbalancer is impossible.

[emiliocampos-zevenet]

Hi,I don't see any relation between the check_http timeout and 504 timeout issue and this new issue you are describing here. In this new case further review should be required in order o understand the connection from load balancer to backend and Client to backend Regards El mié., 20 abr. 2022 15:51, greg-kl ***@***.***> escribió:

…

I did some health-check accessibility testing using MS Edge on windows client. The traffic from this workstation is directed to the "DMZ nlb cluster" to simulate an external connection. I performed 100 queries every 1 second. Each query ends with a status of 200. The same attempt without a single "timeout" error from the loadbalancer is impossible. [image: image] <https://user-images.githubusercontent.com/103255855/164245328-039bb9d8-249c-4ff2-9866-ce3646b9ad55.png> — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPAHEJRFEGSBCTBY2FTVGADU5ANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

[greg-kl]

Hi,I don't see any relation between the check_http timeout and 504 timeout
issue and this new issue you are describing here.

This depend how I set Timeout value for health-check. If higher than 21s then I got 504 Timeout. Below 21s there is Socket Timeout.

For me it's weird to set timeout for "check" at 21s or higher if two host are in the same area and subnet. Please take a look at the response time when attempt is finished with code 200. The response in each attempt is imeddiate - no delay.

At this moment, I disabled health-check verification for all publicated services. Administrators will observe if the users are facing connection issues.

I can collect and provide you any reqired information, depending on what level of assistance will be offered.

[emiliocampos-zevenet]

Hi, please correct me if I am wrong You execute the following command from the load balancer: *./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 15* And sometimes you receive a timeout as the command reaches the 15 seconds of timeout. On the other hand you perform 100 queries every 1 seconds from a client IP different to the same backend IP *10.1.8.71*, this client IP is in a different network or architecture than the IP of the load balancer is configured and where the check_http command is executed, in the case you run the client test you don't receive any connection timeout If my understanding is correct then it seems like there is some network issue from the load balancer to the backends because with the tests that you run the ZEVENET core system doesn't enter in any action, as you only run check_http in the command line in the Linux Operating system of ZEVENET. Please add any suggestion you think can help me. Regards! El mié, 20 abr 2022 a las 17:30, greg-kl ***@***.***>) escribió:

…

*Hi,I don't see any relation between the check_http timeout and 504 timeout issue and this new issue you are describing here.* This depend how I set Timeout value for health-check. If higher than 21s then I got 504 Timeout. Below 21s there is Socket Timeout. For me it's weird to set timeout for "check" at 21s or higher if two host are in the same area and subnet. Please take a look at the response time when attempt is finished with code 200. The response in each attempt is imeddiate - no delay. At this moment, I disabled health-check verification for all publicated services. Administrators will observe if the users are facing connection issues. I can collect and provide you any reqired information, depending on what level of assistance will be offered. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPGSRHLFV75TIXVDMGTVGAPI7ANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[emiliocampos-zevenet]

On the other hand having a look to the check_http manual: check_http -H <vhost> | -I <IP-address> [-u <uri>] [-p <port>] [-J <client certificate file>] [-K <private key>] [-w <warn time>] [-c <critical time>] [-t <timeout>] [-L] [-E] [-a auth] [-b proxy_auth] [-f <ok|warning|critcal|follow|sticky|stickyport>] [-e <expect>] [-d string] [-s string] [-l] [-r <regex> | -R <case-insensitive regex>] [-P string] [-m <min_pg_size>:<max_pg_size>] [-4|-6] [-N] [-M <age>] [-A string] [-k string] [-S <version>] [--sni] [-C <warn_age>[,<crit_age>]] [-T <content-type>] [-j method] and compared with your command: *./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 15* it seems like you forgot to use the -I <IP-address> flag, that is where you have to configure the client IP in order to send directly the request to the backend. Please try this because it seems like the check_http command is not properly configured. Regards! El mié, 20 abr 2022 a las 19:37, Emilio Campos Martín (< ***@***.***>) escribió:

…

Hi, please correct me if I am wrong You execute the following command from the load balancer: *./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 15* And sometimes you receive a timeout as the command reaches the 15 seconds of timeout. On the other hand you perform 100 queries every 1 seconds from a client IP different to the same backend IP *10.1.8.71*, this client IP is in a different network or architecture than the IP of the load balancer is configured and where the check_http command is executed, in the case you run the client test you don't receive any connection timeout If my understanding is correct then it seems like there is some network issue from the load balancer to the backends because with the tests that you run the ZEVENET core system doesn't enter in any action, as you only run check_http in the command line in the Linux Operating system of ZEVENET. Please add any suggestion you think can help me. Regards! El mié, 20 abr 2022 a las 17:30, greg-kl ***@***.***>) escribió: > > *Hi,I don't see any relation between the check_http timeout and 504 > timeout issue and this new issue you are describing here.* > > This depend how I set Timeout value for health-check. If higher than 21s > then I got 504 Timeout. Below 21s there is Socket Timeout. > > For me it's weird to set timeout for "check" at 21s or higher if two host > are in the same area and subnet. Please take a look at the response time > when attempt is finished with code 200. The response in each attempt is > imeddiate - no delay. > > At this moment, I disabled health-check verification for all publicated > services. Administrators will observe if the users are facing connection > issues. > > I can collect and provide you any reqired information, depending on what > level of assistance will be offered. > > — > Reply to this email directly, view it on GitHub > <#3 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFBQEPGSRHLFV75TIXVDMGTVGAPI7ANCNFSM5T3TPXHQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> > -- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

I did tests with changed commands and I'm still getting this same timeout:

[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.070 second response time |time=0.069760s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.064 second response time |time=0.064062s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.078 second response time |time=0.078198s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.068131s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.072 second response time |time=0.071510s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.046 second response time |time=21.045910s;;;0.000000;100.000000 size=165B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.069 second response time |time=0.069194s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.045 second response time |time=21.045188s;;;0.000000;100.000000 size=165B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.070 second response time |time=0.069932s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.078 second response time |time=0.077526s;;;0.000000;100.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm -p 443 -S -t 100
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.074 second response time |time=0.074391s;;;0.000000;100.000000 size=270B;;;0

I will try to prepare additional workstation in this same DMZ network as NLB.

[emiliocampos-zevenet]

Thanks for the update, what about my comments about the difference between networks, client directly to the backend and load balancer to the backend? As I said there is not any relation in your tests with the ZEVENET load balancing core as the traffic is not passing through the ZEVENET data path when you run check_http tests. Regards El mié, 20 abr 2022 a las 22:21, greg-kl ***@***.***>) escribió:

…

I did tests with changed commands and I'm still getting this same timeout: *[master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.070 second response time |time=0.069760s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.064 second response time |time=0.064062s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.078 second response time |time=0.078198s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.068131s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.072 second response time |time=0.071510s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.046 second response time |time=21.045910s;;;0.000000;100.000000 size=165B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.069 second response time |time=0.069194s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.045 second response time |time=21.045188s;;;0.000000;100.000000 size=165B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.070 second response time |time=0.069932s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.078 second response time |time=0.077526s;;;0.000000;100.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H 10.1.8.71 -I 10.1.8.71 -u https://mail.org.com/microsoft-server-activesync/healthcheck.htm <https://mail.org.com/microsoft-server-activesync/healthcheck.htm> -p 443 -S -t 100 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.074 second response time |time=0.074391s;;;0.000000;100.000000 size=270B;;;0* I will try to prepare additional workstation in this same DMZ network as NLB. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPDN32ZHHGRXJ6NGYNDVGBRL7ANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

Regarding tests performed from a workstation. Communication to Exhcange services from this workstation is routed through Loadbalancer in DMZ network. It means that the same URL is queried with a web browser, the tests are positive, and the Loadbalancer is used in the communication, from which the execution of the same test ends with Timeout errors several times.

[emiliocampos-zevenet]

Could you share with us VIrtual IP of the Exchange farm Backend IPs and the output of the following commands ip rule list ip route list table table_eth0 in case more than one eth is configured then: ip route list table table_ethX Thank! El mié, 20 abr 2022 a las 22:43, greg-kl ***@***.***>) escribió:

…

Regarding tests performed from a workstation. Communication to Exhcange services from this workstation is routed through Loadbalancer in DMZ network. It means that the same URL is queried with a web browser, the tests are positive, and the Loadbalancer is used in the communication, from which the execution of the same test ends with Timeout errors several times. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPFN5JVOMYP3YKZUXI3VGBT6RANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

Yes. I will provide you these info tomorrow.

[greg-kl]

ViP for exchange farm: 10.1.8.55

Backend's Ip's:
10.1.8.71
10.1.8.72

[master] root@KWARV-LBZ02:~# ip rule list
0:      from all lookup local
25996:  from all fwmark 0x203/0x7fffffff lookup table_eth0
25997:  from all fwmark 0x202/0x7fffffff lookup table_eth0
25998:  from all fwmark 0x201/0x7fffffff lookup table_eth0
25999:  from all fwmark 0x200/0x7fffffff lookup table_eth0
32000:  from 10.1.8.0/25 lookup table_eth0
32766:  from all lookup main
32767:  from all lookup default
[master] root@KWARV-LBZ02:~# ip route list table table_eth0
default via 10.1.8.3 dev eth0
10.1.8.0/25 dev eth0 scope link src 10.1.8.52

[emiliocampos-zevenet]

Hi, thanks for sharing this information with us, I see backends and VIP are in the same network, I don't see any that would require special attention. Please could you repeat tests with this modified command and let us know if it fails as well? ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 El jue, 21 abr 2022 a las 14:52, greg-kl ***@***.***>) escribió:

…

ViP for exchange farm: 10.1.8.55 Backend's Ip's: 10.1.8.71 10.1.8.72 [master] ***@***.***:# ip rule list 0: from all lookup local 25996: from all fwmark 0x203/0x7fffffff lookup table_eth0 25997: from all fwmark 0x202/0x7fffffff lookup table_eth0 25998: from all fwmark 0x201/0x7fffffff lookup table_eth0 25999: from all fwmark 0x200/0x7fffffff lookup table_eth0 32000: from 10.1.8.0/25 lookup table_eth0 32766: from all lookup main 32767: from all lookup default [master] ***@***.***:# ip route list table table_eth0 default via 10.1.8.3 dev eth0 10.1.8.0/25 dev eth0 scope link src 10.1.8.52 — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPAGXTYFZEEWNV5SXDDVGFFO3ANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

still some timeouts:

[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 6.467 second response time |time=6.466989s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.043 second response time |time=0.043138s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.034 second response time |time=0.033805s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.038 second response time |time=0.038105s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.041 second response time |time=0.040568s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
**connect to address mail.org.com and port 443: Connection timed out
HTTP CRITICAL - Unable to open TCP socket**
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.056 second response time |time=0.055771s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.048 second response time |time=0.047886s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.044689s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.046 second response time |time=0.045601s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.052 second response time |time=0.052083s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.043 second response time |time=0.042965s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.046871s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.052 second response time |time=0.051764s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.046 second response time |time=0.045729s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.044 second response time |time=0.044052s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.047158s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.045243s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.042 second response time |time=0.042202s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.046879s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
**connect to address mail.org.com and port 443: Connection timed out
HTTP CRITICAL - Unable to open TCP socket**
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.049 second response time |time=0.049068s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.047345s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.051 second response time |time=0.050597s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
**connect to address mail.org.com and port 443: Connection timed out
HTTP CRITICAL - Unable to open TCP socket**
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.046 second response time |time=0.045866s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.045190s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
connect to address mail.org.com and port 443: Connection timed out
HTTP CRITICAL - Unable to open TCP socket
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.038 second response time |time=0.037686s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.038 second response time |time=0.037895s;;;0.000000;40.000000 size=248B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.044962s;;;0.000000;40.000000 size=248B;;;0

[emiliocampos-zevenet]

Sorry but I don't see the -I 10.1.8.71 as I requested in my previous command, see below: ./check_http -H mail.org.com *-I 10.1.8.71 *-u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 I don't have knowledge about how to do health checks to Exchange but I suspect that you are running checks against the host mail.org.com that is on the internet with IP 34.206.39.153 for that reason you experience connection timeout randomly Thanks! El jue, 21 abr 2022 a las 17:36, greg-kl ***@***.***>) escribió:

…

still some timeouts: [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 6.467 second response time |time=6.466989s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.043 second response time |time=0.043138s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.034 second response time |time=0.033805s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.038 second response time |time=0.038105s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.041 second response time |time=0.040568s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 **connect to address mail.org.com and port 443: Connection timed out HTTP CRITICAL - Unable to open TCP socket** [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.056 second response time |time=0.055771s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.048 second response time |time=0.047886s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.044689s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.046 second response time |time=0.045601s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.052 second response time |time=0.052083s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.043 second response time |time=0.042965s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.046871s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.052 second response time |time=0.051764s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.046 second response time |time=0.045729s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.044 second response time |time=0.044052s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.047158s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.045243s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.042 second response time |time=0.042202s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.046879s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 **connect to address mail.org.com and port 443: Connection timed out HTTP CRITICAL - Unable to open TCP socket** [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.049 second response time |time=0.049068s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.047 second response time |time=0.047345s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.051 second response time |time=0.050597s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 **connect to address mail.org.com and port 443: Connection timed out HTTP CRITICAL - Unable to open TCP socket** [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.046 second response time |time=0.045866s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.045190s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 connect to address mail.org.com and port 443: Connection timed out HTTP CRITICAL - Unable to open TCP socket [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.038 second response time |time=0.037686s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.038 second response time |time=0.037895s;;;0.000000;40.000000 size=248B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 248 bytes in 0.045 second response time |time=0.044962s;;;0.000000;40.000000 size=248B;;;0 — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPELL3G7XGRERQHYSIDVGFYWTANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Emilio CamposZEVENET Teamwww.zevenet.com Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr> <https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet> <https://www.facebook.com/zevenet> <https://github.com/zevenet> [image: ZEVENET] <https://www.zevenet.com/signature/> DISCLAIMER: This message contains confidential information and is intended only for the individual named. If you are not the named addressee please notify the sender immediately by email if you have received it by mistake and delete it from your system, you should not disseminate, distribute or copy this email in whole or in part.

[greg-kl]

Sorry, jus missed -I in command. Here is short result still getting:

HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.015 second response time |time=21.015130s;;;0.000000;40.000000 size=165B;;;0

[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.067838s;;;0.000000;40.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.072 second response time |time=0.072147s;;;0.000000;40.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.069 second response time |time=0.068943s;;;0.000000;40.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.015 second response time |time=21.015130s;;;0.000000;40.000000 size=165B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.060 second response time |time=0.060004s;;;0.000000;40.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.069 second response time |time=0.068622s;;;0.000000;40.000000 size=270B;;;0
[master] root@KWARV-LBZ02:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40
HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.065 second response time |time=0.065477s;;;0.000000;40.000000 size=270B;;;0
mail.org.com

Im using mail.org.com as example here. I will not publish full adress of the mailbox service of my customer here on public forum. If you need real names to check something, we need to switch to direct e-mail corrsepondence.

[emiliocampos-zevenet]

Are you using proxy ? Type : env In command line and paste here the output for verification As I already said it doesn't seem to be related to Zevenet Thanks El jue., 21 abr. 2022 19:14, greg-kl ***@***.***> escribió:

…

Sorry, jus missed -I in command. Here is short result still getting: HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.015 second response time |time=21.015130s;;;0.000000;40.000000 size=165B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.068 second response time |time=0.067838s;;;0.000000;40.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.072 second response time |time=0.072147s;;;0.000000;40.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.069 second response time |time=0.068943s;;;0.000000;40.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP CRITICAL: HTTP/1.1 504 Gateway Timeout - 165 bytes in 21.015 second response time |time=21.015130s;;;0.000000;40.000000 size=165B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.060 second response time |time=0.060004s;;;0.000000;40.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.069 second response time |time=0.068622s;;;0.000000;40.000000 size=270B;;;0 [master] ***@***.***:/lib/nagios/plugins# ./check_http -H mail.org.com -I 10.1.8.71 -u /microsoft-server-activesync/healthcheck.htm -p 443 -S -t 40 HTTP OK: HTTP/1.1 200 OK - 270 bytes in 0.065 second response time |time=0.065477s;;;0.000000;40.000000 size=270B;;;0mail.org.com — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBQEPENCUHUAQGK5B5UIKTVGGEIFANCNFSM5T3TPXHQ> . You are receiving this because you commented.Message ID: ***@***.***>

[greg-kl]

there is no proxy configured, all servers are hosted in one data center.

SHELL=/bin/bash
LANGUAGE=en_US:en
PWD=/lib/nagios/plugins
LOGNAME=root
XDG_SESSION_TYPE=tty
HOME=/root
LANG=en_US.UTF-8
PROMPT_COMMAND=echo -n [$(cat /etc/zevenet-ce-cluster.status 2>/dev/null)]
SSH_CONNECTION=192.168.5.25 58279 10.1.8.50 22
XDG_SESSION_CLASS=user
TERM=xterm
USER=root
SHLVL=1
XDG_SESSION_ID=65341
XDG_RUNTIME_DIR=/run/user/0
SSH_CLIENT=192.168.5.25 58279 22
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
MAIL=/var/mail/root
SSH_TTY=/dev/pts/0
_=/usr/bin/env
OLDPWD=/root