AdminUI health queries fail when the first node isn't active
Details
| Detail name | Value |
|---|---|
| Changelog Number | 30180 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 2025.1.0 |
| Fix Versions | Exasol 2026.1.2, Exasol 2025.1.16 |
| Resolution Date | 2026-08-28 |
Description
In AdminUI, health queries (the Test database button and all Health charts) failed whenever the deployment's first configured node was not the currently active/serving node. The root cause was that the monitoring connection always used the first node in the static EXAConf node list, regardless of whether that node was actually serving client connections — so as soon as fail-safety moved the database's connection endpoint off that first node, every health query failed.
Workaround
There is no workaround, other than bringing the affected node back up so it becomes the active/serving node again.
Fix
The monitoring connection now resolves the database's current connection endpoint from confd's db_info (the same live endpoint maintained by DWAd/fail-safety) instead of assuming it's always the first configured node, so health queries keep working as long as at least one node is active.
Authentication failures on this connection are now also handled consistently as a connection error rather than an unhandled server error.
