# Master HA node failover **URL:** \ **Category:** Community Support\ **Tags:** ha, tlserver\ **Created:** [23 June 2026 22:37 UTC](https://community.thinlinc.com/t/master-ha-node-failover/2028 "2026-06-23T22:37:23Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Harj](https://avatars.discourse-cdn.com/v4/letter/h/3be4f8/32.png) [@Harj](https://community.thinlinc.com/u/Harj)\ **Post date:** [23 June 2026 22:37 UTC](https://community.thinlinc.com/t/master-ha-node-failover/2028/1 "2026-06-23T22:37:23Z")
Hi All Ive setup a HA broker cluster - 2 nodes using pacemaker + corosync (TL 4.20). The HA cluster appears to work fine. A failover test - node 1 was taken off line with an active session on VDA/agent server. The HA failover is ok - able to login via the VIP using the client and the VP web admin page is redirecting to node 2. However, node 2 shows 0 active sessions so the session DB failed to sync from node 1 to node 2. /opt/thinlinc/etc/conf.d/cluster.hconf HA is showing as enabled (1) and that both nodes are listed in the cluster nodes= [node1.example.com](http://node1.example.com) [node2.example.com](http://node2.example.com) Bringing node 1 back on line - node 2 stays primary and active node. Unable to reconnect to the disconnected session on the VDA Any ideas ? Thanks HArj ---
**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\ **Post date:** [24 June 2026 19:39 UTC](https://community.thinlinc.com/t/master-ha-node-failover/2028/2 "2026-06-24T19:39:04Z")
Please check the server logs for any information related to HA. You can find the logs at `/var/log/vsmserver.log` on the master server. Let us know if there are any clues there. ---
**Author:** ![Harj](https://avatars.discourse-cdn.com/v4/letter/h/3be4f8/32.png) [@Harj](https://community.thinlinc.com/u/Harj)\ **Post date:** [29 June 2026 00:04 UTC](https://community.thinlinc.com/t/master-ha-node-failover/2028/3 "2026-06-29T00:04:41Z")
Hi Aaron Thanks for the headsup on the log files. I’ll re test fail over and see if its behaving or not and check the logs accordingly. Update: from the logs on one of the brokers: 2026-06-29 08:58:10 ERROR vsmserver.HA: Failed to do hostname lookup on node ‘rocktldc-02.lab.internal’ from /HA/nodes 2026-06-29 08:58:10 ERROR vsmserver.HA: 0 matches when comparing hostnames from /HA/nodes with result of gethostname() - should be exactly one match 2026-06-29 08:58:10 ERROR vsmserver.HA: Can’t determine address of other node safely. 2026-06-29 08:58:10 ERROR vsmserver.HA: STARTING WITH HA DISABLED! 2026-06-29 08:58:10 WARNING vsmserver.loadinfo: Draining agents: [‘127.0.0.1’, ‘rocktldc-02.lab.internal’] 2026-06-29 08:58:10 INFO vsmserver.loadinfo: Agent 127.0.0.1 is back up HA/Nodes was originally configured with the fqdn of each host. Replaced that with just the hostname. On both brokers the /opt/thinlinc/etc/conf.d/cluster.hconf file is : nodes=rocktldc-01 rocktldc-02 Update 2 - got it working. set the hostnames to fqdn’s on both nodes, set the HA/nodes back to fqdn and that’s worked. HA is working and session failover is seamless - and session disconnects and reconnects. KR Harj ---
**Author:** ![wilsj](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/wilsj/32/554_2.png) [@wilsj](https://community.thinlinc.com/u/wilsj)\ **Post date:** [2 July 2026 13:28 UTC](https://community.thinlinc.com/t/master-ha-node-failover/2028/4 "2026-07-02T13:28:11Z")
Hi @Harj, Great that you got it working and thank you for sharing your solution! ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex005/uploads/thinlinc/original/1X/8077c8ac87eafb9aec32455fdf162db58e9a4881.png) [@system](https://community.thinlinc.com/u/system)\ **Post date:** [4 July 2026 13:28 UTC](https://community.thinlinc.com/t/master-ha-node-failover/2028/5 "2026-07-04T13:28:29Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.