neroping.blogg.se

1. #Vmware horizon client error http error 503 how to#
2. #Vmware horizon client error http error 503 code#

To calculate this timer, you have to know what options you’ve setup in Horizon for the global settings “Forcibly Disconnect Users” and “Disconnect Applications and Discard SSO credentials for idle users” When configuring the IP table, you have to specify an expiry timer. In HAProxy we can create an IP table and tell HAproxy to keep connections “sticky” based on the IP address. However, we must make sure that source persistence is enabled so that a client doesn’t switch connection servers between 2 connections because that would force the client to re-login to the other connection server. Server cs2 192.168.1.22:443 weight 1 check check-ssl verify none inter 30s fastinter 2s rise 5 fall 2įinally, the last optimization I’ve done, is to change the load balancing method from “source” to “least connection”. Server cs1 192.168.1.21:443 weight 1 check check-ssl verify none inter 30s fastinter 2s rise 5 fall 2 This results in the following HAProxy configuration.

VMware recommends to schedule the health checks every 30 seconds and to set a timeout of 91 seconds (3 times a health check + 1 second). Once a connection server is disabled, HAProxy will put the backend server correctly in maintenance mode now:Īpart from getting a more accurate status from the connection servers, VMware also has some recommendations on the check frequency so you don’t overload the connection servers with health checks. Server cs2 192.168.1.22:443 weight 1 check check-ssl verify none inter 30s fastinter 2s downinter 5s rise 3 fall 3 Server cs1 192.168.1.21:443 weight 1 check check-ssl verify none inter 30s fastinter 2s downinter 5s rise 3 fall 3 For this we have to adjust the HAProxy config from the earlier post as follows.

#Vmware horizon client error http error 503 code#

With HAProxy we have the ability to check this and put a backend server in maintenance mode once the returned status code is anything but 200.

On earlier versions, the “disabled” status of a connection server is not reflected in this check. If the connection server is (administratively) disabled, it will return a status code 503. This will return a status code 200 if the connection server is available and ready to accept connections. VMware Horizonįor VMware Horizon, the supported way to check if a connection server is available is to check the

#Vmware horizon client error http error 503 how to#

So I looked into the details about how to get the correct status of the backend servers and to make HAProxy use that status in stead of just checking if we get a reply from the webserver. database connection lost) the webserver will still be running, but AppVolumes won’t work anymore. Same for the AppVolumes managers, if there’s an error (e.g. The drawback of this is when you set a connection server “disabled”, the webserver is still responding, so HAProxy will still be redirecting connections to that server, although they will get blocked on the server itself. The load balancing config used in that post was a basic one who just checked if the connection servers or appvolumes managers were running by checking if the webserver on the servers responded. A while ago I wrote a blog post about using HAProxy and Keepalived to make VMware Horizon connection servers and AppVolumes managers high available.