Troubleshooting
- Last Updated: June 10, 2025
- 2 minute read
- LoadMaster
- LoadMaster GA
- Documentation
Refer to the following sections for details on troubleshooting steps relating to LoadMaster clusters.
Ensure the Partner Shared Secret Matches on all Cluster Units
- Regular/shared WUI: Certificates & Security > Remote Access
- Local WUI (of a configured cluster unit): Local Administration > Remote Access
When an incoming shared secret does not match the local Partner Shared Secret (including if only one side is providing a shared secret), a warn-level log message is recorded that says Unauthorized Remote Machine connection from <ClientIPAddress> and the connection fails.
Check the Logs
Logs are recorded to track certain clustering events, such as when a node goes offline. Viewing the logs can help to troubleshoot problems which may occur. To view the logs relating to clustering, in the LoadMaster WUI go to System Configuration > Logging Options > System Log Files. The logs relating to clustering are available in the Warning Message File and the System Message File.
Some examples of log entries relating to clustering are listed and described below.
In the following log example, there was a worker node and admin node. The admin node failed and the worker node became the admin node. There were then no worker nodes left because there was only one previously, which is why the last line says Cluster has no functioning nodes:
2023-01-24T13:40:06+00:00 LM03 ucarp: [CRITICAL] Partner has failed, becoming ACTIVE
2023-01-24T13:40:06+00:00 LM03 logger: HA Switching to Active
2023-01-24T13:40:07+00:00 LM03 l4d: Cluster has no functioning nodes.
The following log example shows a node going offline. This could be because the node was rebooted.
lb100 l4d: Node 3 now deadlb100 l4d: Cluster running ononly 3 of 4 nodes
The following log example indicates that a node has gone offline.
lb100 l4d: Cluster running on 3 of 4 nodes (1 disabled)
The following log example indicates that a node is alive, for example a disabled node has been enabled.
lb100 l4d: Node 3 now alive