db_info returned the connection string of a currently-active database node instead of the (possibly offline) first configured node.

Detail name	Value
Changelog Number	28975
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.29.0, Exasol 2025.1.0, Exasol 2026.1.0
Fix Versions	Exasol 2025.1.14
Resolution Date	2026-08-06

Description

db_info returned a wrong connection string when the first database node (as listed in the static EXAConf configuration) was offline. After DWAd completed fail-safety and restarted the database on a reserve node, db_info's connection string still pointed at the IP address of the first configured node — which was now offline — because the value was built purely from the static EXAConf node list rather than from the database's actual current state.

As a result, Admin UI charts were not working if the first node is not active anymore.

Workaround

Determine the currently active database nodes from the nodes field of db_info output and construct the connection string manually using an online node's address, instead of relying on the connection string field.

Fix

get_database_connection_string() now asks DWAd (exa_db.conn()) for the host that currently serves the connection endpoint and translates it back to that node's private IP from EXAConf, so the connection string follows the database onto the reserve node after fail-safety. If DWAd cannot provide an endpoint (e.g. the database is not running or is otherwise unreachable), it falls back to the first node of the static EXAConf configuration as before.

As a result, Admin UI charts are working irrespective of the first node being active or not.