Wsrep doesn't turn on

I’m trying to start a new cluster named pxc-cluster
Cluster is being bootstrapped successfully but galera library isn’t being read if placed in wsrep.cnf but after transferring it to my.cnf it shows the following error:

2023-05-09T07:29:51.948011Z 0 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view (pc.wait_prim_timeout): 110 (Connection timed out)
at gcomm/src/pc.cpp:connect():161
2023-05-09T07:29:51.948088Z 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():209: Failed to open backend connection: -110 (Connection timed out)
2023-05-09T07:29:51.948227Z 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1528: Failed to open channel ‘pxc-cluster’ at ‘gcomm://,,,1192.168.1.186’: -110 (Connection timed out)
2023-05-09T07:29:51.948254Z 0 [ERROR] WSREP: gcs connect failed: Connection timed out
2023-05-09T07:29:51.948281Z 0 [ERROR] WSREP: Provider/Node (gcomm://,,,1192.168.1.186) failed to establish connection with cluster (reason: 7)
2023-05-09T07:29:51.948291Z 0 [ERROR] Aborting

Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
Percona version: 5.7.36-39

Hello Aldrin and Welcome to the Percona Community.

So, reading error log whenever I see “Connection timed out”, I always question that something is blocking me from talking to someone else on the other side. Check firewalls selinux or other networking access and verify that the following ports are open: 3306, 4444, and 4567.

Also check this question hinting at similar problems for PXC.


1 Like

Thanks for the reply @kedarpercona, those ports were already added to the security group of both ec2-instances. Anyways we found out that the config file location was the issue. We transferred the config from wsrep.cnf to my.cnf.