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

admin

# pcs status
& p; g+ U: A6 q# q8 D- ZCluster name: my_wsrep_cluster
/ Z- D2 w4 u5 F/ uStack: corosync
Current DC: controller1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum
Last updated: Thu Dec 28 18:24:33 2017
4 T$ F$ v# Y& |* _# SLast change: Thu Dec 28 18:05:11 2017 by root via cibadmin on controller1
3 nodes configured
7 l8 W7 c6 s! y1 resource configured
9 \+ ^. h+ ^6 P6 R9 e( H+ `  \, bOnline: [ controller1 controller2 controller3 ]
. l4 u/ u6 U% v- n! V, mFull list of resources:
db (ocf::heartbeat:galera): Stopped
8 J& b- J, @) ?! [2 d+ @4 x( yFailed 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
7 v* G% S6 }0 \) G  pacemaker: active/enabled
  pcsd: active/enabled
4 F& z% P& b9 j! H( b! O' c
+ i; k$ l* y) V, q, q: \4 ]' c8 T所有的状态都是active的，唯独只有db状态是stopped，为什么呢？
4 o) V$ l4 {5 h5 S+ S

admin

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

admin

配置一个mariadb服务
+ Q# j7 s) ^9 i  ~  Y# m1 D8 K在所有节点上执行
# yum install mariadb-* -y
% Y) t: R" b/ L# systemctl disable mariadb
$ ~' J* l  M* q* o% t$ N# systemctl status mariadb
# pcs create resource DB ocf:heartbear:mysql
. |/ d" F" J, {3 H配置一个互为备份的双机环境，一个节点作为web，一个节点作为db，各自有自己的浮动IP，出现故障的时候互相切换
# pcs resource create VIP1 ocf:heartbeat:IPaddr2 ip=192.168.122.171 cidr_netmask=24 nic=eth0
# 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
; p' x# G) ]" V5 d8 ^# pcs constraint location add server1 VIP1 node1 1
# pcs constraint location add server2 FS node2 1
# pcs constraint location add server2 VIP node2 1
' h) R' q* c% }) x' K# pcs constraint location add server2 WEB node2 1
执行上述命令后，DB和VIP1将启动在node1上而剩下的FS VIP WEB将启动在node2上

admin

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

admin

controller_start_0 on controller1 'unknown error'