高可用pacemaker状态，db状态为stopped

admin

# pcs status
: u- C7 A8 M# S5 C0 wCluster name: my_wsrep_cluster
Stack: corosync
4 X, ~  _4 _7 c# L# R: T6 CCurrent DC: controller1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum
Last updated: Thu Dec 28 18:24:33 2017
Last change: Thu Dec 28 18:05:11 2017 by root via cibadmin on controller1
6 u* z. |# s3 H- D$ D; J, g3 nodes configured
, `) i* T2 d0 ^: q6 @( n1 resource configured
( h% U9 j# I4 B; I& Q* p" yOnline: [ controller1 controller2 controller3 ]
. I8 H# C  m. V9 J- H9 d4 \6 aFull list of resources:
$ q8 J0 x/ {% {$ n. W db (ocf::heartbeat:galera): Stopped
/ X- a, ?8 E1 g4 T, F* ?' V. mFailed Actions:
* db_start_0 on controller1 'not configured' (6): call=22, status=complete, exitreason='Galera must be configured as a multistate Master/Slave resource.',
    last-rc-change='Thu Dec 28 18:05:11 2017', queued=1ms, exec=56ms

Daemon Status:
  corosync: active/enabled
2 s, r" I  k+ a/ D9 s/ X) I  pacemaker: active/enabled
  pcsd: active/enabled

所有的状态都是active的，唯独只有db状态是stopped，为什么呢？
+ ]* _1 m- s5 D! ]" `6 a& E

admin

才疏学浅，未能解决问题，遗憾。不知哪儿出问题了，好尴尬。

admin

配置一个mariadb服务
+ a! A- a" T- F7 b3 x在所有节点上执行
& R/ L6 V3 C3 K, F3 g* s# yum install mariadb-* -y
# systemctl disable mariadb
# systemctl status mariadb
$ u4 j- p8 B  Y% M- g, M# pcs create resource DB ocf:heartbear:mysql
7 x; M# E) Y5 k. P配置一个互为备份的双机环境，一个节点作为web，一个节点作为db，各自有自己的浮动IP，出现故障的时候互相切换
# pcs resource create VIP1 ocf:heartbeat:IPaddr2 ip=192.168.122.171 cidr_netmask=24 nic=eth0
/ Z; R3 ]! B, Z  I5 C: d# pcs resource group add MyGroup1 VIP1 DB(因为前面已经把DB添加到MyGroup组，所以需要先用pcs resource disable WEB; pcs resource diable DB;pcs resource group remove MyGroup DB; pcs resource enable WEB;才可以添加DB到MyGroup1 )
# pcs constraint location add server1 DB node1 1
# pcs constraint location add server1 VIP1 node1 1
# pcs constraint location add server2 FS node2 1
# pcs constraint location add server2 VIP node2 1
  D* f& g1 v# n4 H8 {" p# pcs constraint location add server2 WEB node2 1
( d! x7 s+ M4 y: g* N. a3 d执行上述命令后，DB和VIP1将启动在node1上而剩下的FS VIP WEB将启动在node2上

admin

突然想起来好像用的是pike版本的源，这个版本有可能有问题。还需要验证，想着回退到octa版本，试试。

admin

controller_start_0 on controller1 'unknown error'