The Ultimate Guide to High Availability with MariaDB

maraiDBserver does not start with galera cluster

I had to shut down all nodes in a previously functioning cluster. Now I can no longer start the MaraiDB server on any of the nodes, I always get the following error messages:

Mai 17 08:21:09 DebianNgnix2 mariadbd[604]: at ./gcomm/src/pc.cpp:connect():160 Mai 17 08:21:09 DebianNgnix2 mariadbd[604]: 2023-05-17 8:21:09 0 [ERROR] WSREP: ./gcs/src/gcs_core.cpp:gcs_core_open():219: Failed to open backend connection: -110 (Connection timed out) Mai 17 08:21:09 DebianNgnix2 mariadbd[604]: 2023-05-17 8:21:09 0 [Note] WSREP: Deferred close timer destruct Mai 17 08:21:09 DebianNgnix2 mariadbd[604]: 2023-05-17 8:21:09 0 [ERROR] WSREP: ./gcs/src/gcs.cpp:gcs_open():1663: Failed to open channel 'mydbcluster' at 'gcomm:192.168.0.181,192.168.0.81': -110 (C> Mai 17 08:21:09 DebianNgnix2 mariadbd[604]: 2023-05-17 8:21:09 0 [ERROR] WSREP: gcs connect failed: Connection timed out Mai 17 08:21:09 DebianNgnix2 mariadbd[604]: 2023-05-17 8:21:09 0 [ERROR] WSREP: wsrep::connect(gcomm:192.168.0.181,192.168.0.81) failed: 7 Mai 17 08:21:09 DebianNgnix2 mariadbd[604]: 2023-05-17 8:21:09 0 [ERROR] Aborting

Does anyone have an idea, thanks and regards

Answer Answered by Daniel Black in this comment.

Appears to be network connectivity related. Check the required ports are listing.

If all nodes are shut down, I assume are bootstrapping a particular node?

ref: https://galeracluster.com/library/documentation/crash-recovery.html

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.