After upgrading to PXC 8.4.5-5.1, I see TLS init warnings, missing binlog_utils_udf.so, and constant Galera “End of file” messages despite a healthy cluster

Description

After upgrading to Percona XtraDB Cluster 8.4.5-5.1 via the Percona Operator (crVersion: 1.18.0), I’m seeing several recurring issues in the MySQL logs across all PXC nodes:

1. TLS initialization warning

[Warning] [MY-013595] [Server] Failed to initialize TLS for channel: mysql_admin.

[Warning] [MY-010069] [Server] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key

[System] [MY-013603] [Server] No TLS configuration was given for channel mysql_admin; re-using TLS configuration of channel mysql_main.

Even though TLS is enabled and configured via sslSecretName and sslInternalSecretName.

2. Missing shared library error

[ERROR] [MY-010901] [Server] Can’t open shared library ‘binlog_utils_udf.so’ (errno: 2 /usr/lib64/mysql/plugin/binlog_utils_udf.so: cannot open shared object file: No such file or directory)

This repeats multiple times on startup, though the cluster continues to operate normally.

3. Repeated Galera “Failed to establish connection: End of file” messages

[Note] [MY-000000] [Galera] Failed to establish connection: End of file

These appear continuously every few seconds, even though the cluster remains healthy and synced (wsrep_cluster_status=Primary, all nodes connected).

Steps to Reproduce

1\.  Deploy a Percona XtraDB Cluster 8.4.5-5.1 using the Percona Operator (crVersion: 1.18.0) on Kubernetes (AKS).

2\.  Enable TLS using sslSecretName and sslInternalSecretName.

3\.  Check MySQL logs after pod restart.

Version

•   Percona Operator: 1.18.0

•   Percona XtraDB Cluster: 8.4.5-5.1

•   Kubernetes: Azure AKS

•   TLS: Enabled (tls.enabled: true)

Logs

Relevant excerpts:

[Warning] [MY-013595] Failed to initialize TLS for channel: mysql_admin

[ERROR] [MY-010901] Can’t open shared library ‘binlog_utils_udf.so’

[Note] [MY-000000] [Galera] Failed to establish connection: End of file

Expected Result

•   TLS should initialize cleanly for all channels.

•   No missing plugin warnings for binlog_utils_udf.so if it is not expected in this version.

•   No continuous “End of file” messages once the cluster is in SYNCED state.

Actual Result

•   TLS initialization produces repeated warnings.

•   The binlog_utils_udf.so plugin cannot be loaded.

•   Galera logs constant “Failed to establish connection: End of file” despite replication being healthy.

Additional Information

•   The cluster is deployed in Azure AKS using the following Helm values (excerpt):

crVersion: 1.18.0

pxc:

image:

repository: percona/percona-xtradb-cluster

tag: "8.4.5-5.1"

configuration: |-

\[mysqld\]

pxc-encrypt-cluster-traffic=ON

default-time-zone = 'Asia/Jerusalem'

sql_mode=STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION

wsrep_sync_wait = 1



\[galera\]

socket.ssl=YES



\[sst\]

encrypt=4

ssl-ca=/etc/mysql/ssl-internal/ca.crt

ssl-cert=/etc/mysql/ssl-internal/tls.crt

ssl-key=/etc/mysql/ssl-internal/tls.key

tls:

enabled: true

All nodes complete SST/IST successfully and join the cluster (SYNCED), but the above warnings and errors persist.

Questions

1\.  Is the TLS warning expected in 8.4.5 or a known regression?

2\.  Is the missing binlog_utils_udf.so plugin intentional or a packaging issue?

3\.  Do the repeated “End of file” messages indicate a harmless retry, or is there an underlying connectivity issue?
1 Like

Hi @noops did you perform an update from PXC 8.0 to PXC 8.4? Or just upgrade the operator from 1.17.0 to 1.18.0.

1 Like

i hade upgraded from pxc 8.0 into the 8.4 previusly to that oporator upgrade