The Ultimate Guide to High Availability with MariaDB

Comments - MariaDB with Galera on RedHat 7.2 not starting

8 years, 6 months ago Veselin Vasilev
Re: MariaDB with Galera on RedHat 7.2 not starting
This comment has the status of 'removed' and can only be seen by you.

Thank you for the answer. I proceeded according to the last method and got partial success:

[dbadmin@mariadb-N1 ~]$ mysql -u root -p --execute="SHOW GLOBAL STATUS WHERE Variable_name IN ('wsrep_ready', 'wsrep_cluster_size', 'wsrep_cluster_status', 'wsrep_connected');"
Enter password:
+----------------------+--------------+
| Variable_name        | Value        |
+----------------------+--------------+
| wsrep_cluster_size   | 0            |
| wsrep_cluster_status | Disconnected |
| wsrep_connected      | OFF          |
| wsrep_ready          | OFF          |
+----------------------+--------------+
[dbadmin@mariadb-N1 ~]$ mysql -u root -p --execute="SET GLOBAL wsrep_cluster_address='gcomm://172.20.1.56,172.20.1.57,172.20.1.58';"
Enter password:
ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query

When I dig into the log I see this:

[dbadmin@mariadb-N1 ~]$ systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: failed (Result: exit-code) since Mon 2016-06-13 22:08:54 EEST; 9s ago
  Process: 18400 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER (code=exited, status=1/FAILURE)
 Main PID: 18400 (code=exited, status=1/FAILURE)
   Status: "Taking your SQL requests now..."
   CGroup: /system.slice/mariadb.service
           └─3051 /usr/sbin/mysqld

Jun 13 22:08:54 mariadb-N1.intelligene.local mysqld[18400]: Some pointers may be invalid and cause the dump to abort.
Jun 13 22:08:54 mariadb-N1.intelligene.local mysqld[18400]: Query (0x7fa5c2efd020): SET GLOBAL wsrep_cluster_address='gcomm://172.20.1.56,172.20.1.57,172.20.1.58'
Jun 13 22:08:54 mariadb-N1.intelligene.local mysqld[18400]: Connection ID (thread ID): 2
Jun 13 22:08:54 mariadb-N1.intelligene.local mysqld[18400]: Status: NOT_KILLED
Jun 13 22:08:54 mariadb-N1.intelligene.local mysqld[18400]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_me...,in_to_exi
Jun 13 22:08:54 mariadb-N1.intelligene.local mysqld[18400]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Jun 13 22:08:54 mariadb-N1.intelligene.local mysqld[18400]: information that should help you find out what is causing the crash.
Jun 13 22:08:54 mariadb-N1.intelligene.local systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
Jun 13 22:08:54 mariadb-N1.intelligene.local systemd[1]: Unit mariadb.service entered failed state.
Jun 13 22:08:54 mariadb-N1.intelligene.local systemd[1]: mariadb.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
 
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.