We have a 2-node cluster with an arbiter, and all three servers are in the same subnet.
The cluster reports that one member is unreachable on ports 3306, 4444, and 4568, while the arbiter is reported as unreachable on 4567.
What’s confusing is that both the Web UI and the CLI report that the cluster is healthy and show no cluster errors, but the incidents keep appearing and the cluster is clearly not communicating correctly and API tokens are not Synchronized.
Similar errors on my lab (on Version 4.2.7., issue persists since 4.2.5), except that the token sync seems to work. Both appliances work well (except the errors ofc).
I did patch to 4.2.9 (2 Segura nodes + 1 arbitrator) and the cluster related incidents seem to be gone now. Release notes aren’t up yet, hopefully tomorrow.
The only thing i still get every minute in database logs is:
2026-07-08 0:04:01 0 [Note] WSREP: Failed to establish connection: unexpected eof while reading (SSL routines)
→ There don’t seem to be any negative consequences
Also there’s now a “tuning” related incident, current child process value seems to be not set through the GUI.
I was getting same error : [Note] WSREP: Failed to establish connection: unexpected eof while reading (SSL routines)
→ There don’t seem to be any negative consequences
Just a follow-up - The wsrep specific cluster error seems documented now and is nothing to worry about:
Periodic SSL disconnect messages in the MySQL log
The mysql-error.log file may periodically display (every 30 to 60 seconds):
WSREP: Failed to establish connection: unexpected eof while reading (SSL routines)
Bash
This message can appear even on healthy clusters and does not necessarily indicate a replication failure. Before treating it as an issue, confirm the cluster health directly:
sudo mysql -e "SHOW STATUS LIKE 'wsrep_%';"
Shell Session
Verify that:
wsrep_cluster_status is Primary.
wsrep_ready is ON.
wsrep_local_state_comment is Synced.
