
Chapter 6. High Availability (HA)
Warning
It is VERY IMPORTANT that 127.0.0.1 is not in the list of terminal
servers. If the machines running VSM server are also VSM agents, their
unique hostnames or IP addresses must be added to the
/vsmserver/terminalservers instead of 127.0.0.1. The reason for this
is that 127.0.0.1 will be a different server based on which VSM server is
currently active.
7. After verifying that normal ThinLinc connections work as intended when using both the primary
and the secondary VSM server’s hostname, it is time to enable HA in the VSM servers. This is done
by setting /vsmserver/HA/enabled to 1, and by specifying the nodes in the cluster in
/vsmserver/HA/nodes. For example:
[root@tlha-primary root] tl-config /vsmserver/HA/enabled=1
[root@tlha-primary root] tl-config ’/vsmserver/HA/nodes=tlha-primary.example.com tlha-secondary.example.com’
Configuration should be identical on both nodes. Restart the VSM server on both nodes after
configuration.
8. If vsmserver can’t safely determine which of the two nodes in /vsmserver/HA/nodes is the
remote node, and which is the local node, it will start without HA enabled, and log a message. If this
happens, validate your hostname and DNS setup. One of the entries of /vsmserver/HA/nodes
must match the local machine. Either the resolved IP of one of the entries in
/vsmserver/HA/nodes must match the local IP, or one entry must exactly match the local
hostname as returned by uname -n.
9. Once HA has been configured, tests should be performed in order to confirm that the failover works
as expected. This can normally be done by simply removing the network cable from the primary
node, and ensuring that the secondary node then takes over. Check also that any active ThinLinc
sessions have been synchronized from the primary to the secondary node, and that logging in to such
a session on the secondary node succeeds once the primary node has been disabled.
Your ThinLinc HA cluster is now configured! When sessions are created, changed or deleted on the
currently active node, the information about them will be transferred to the other node using a inter-VSM
server protocol. If the other node has to take over service, its copy of the session data will be up to date,
and it can start serving new requests instantly. When the primary node comes up again, the secondary
node will resynchronise with the master.
6.2.2. Reconfiguring an existing ThinLinc Installation into HA mode
If you have an existing ThinLinc installation and want to eliminate the single point of failure (the VSM
server), the procedure is very much like the procedure for installing a new HA cluster.
6.3. Recovering from hardware failures
If situations occur where the secondary node has been forced to take over service because the primary
node failed for some reason, it’s important to know how to recover.
34
Comentarios a estos manuales