We retry the HA sync very aggressively, but we also log each failed attempt. This can result in a lot of spam in vsmserver.log when a node is down.
Example output: > 2017-01-19 16:33:45 WARNING vsmserver.HA: [Errno 111] Connection refused talking to VSM Agent 10.47.253.120:9000 in request to update other HA node with session change (new, root). Retrying later. > 2017-01-19 16:33:46 WARNING vsmserver.HA: [Errno 111] Connection refused talking to VSM Agent 10.47.253.120:9000 in request to update other HA node with session change (new, root). Retrying later.
Log message seems weird, "agent"?
Similar issue happens when there is something misconfigured with HA: > 2019-12-16 15:00:24 WARNING vsmserver.HA: VSM Agent tl2:9000 responded with permission denied in request to update other HA node with session change (new, user). Retrying later. > 2019-12-16 15:00:25 WARNING vsmserver.HA: VSM Agent tl2:9000 responded with permission denied in request to update other HA node with session change (new, user). Retrying later. > 2019-12-16 15:00:26 WARNING vsmserver.HA: VSM Agent tl2:9000 responded with permission denied in request to update other HA node with session change (new, user). Retrying later.