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

admin

# pcs status
Cluster name: my_wsrep_cluster
Stack: corosync
/ C7 H0 I" E1 _: L+ U2 ECurrent DC: controller1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum
! m( @( Y# r1 }Last updated: Thu Dec 28 18:24:33 2017
Last change: Thu Dec 28 18:05:11 2017 by root via cibadmin on controller1
3 nodes configured
! z+ ^" ]; h4 h# d  ~" V3 C( u, `) |1 resource configured
9 [0 i" O2 ]& C9 m: S0 \* H+ wOnline: [ controller1 controller2 controller3 ]
Full list of resources:
db (ocf::heartbeat:galera): Stopped
Failed 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
  P# [' z. Y& q2 e4 V% z
- C4 G. U. d8 G5 s$ jDaemon Status:
: ?* L/ M( v3 D  corosync: active/enabled
& ?; C* J* ~+ m( v  pacemaker: active/enabled
5 v$ f  Y  N3 H( [( q5 j: K2 w2 B  pcsd: active/enabled

所有的状态都是active的，唯独只有db状态是stopped，为什么呢？
3 I+ o8 X0 v; _+ I

admin

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

admin

配置一个mariadb服务
在所有节点上执行
# yum install mariadb-* -y
0 G) ?+ i7 L! y; X& M- @# systemctl disable mariadb
$ ?& W  d2 ?! B- C; `8 M$ t7 ~# systemctl status mariadb
# pcs create resource DB ocf:heartbear:mysql
) u" Q+ _, H6 Q$ V% h配置一个互为备份的双机环境，一个节点作为web，一个节点作为db，各自有自己的浮动IP，出现故障的时候互相切换
# pcs resource create VIP1 ocf:heartbeat:IPaddr2 ip=192.168.122.171 cidr_netmask=24 nic=eth0
  o4 ~* z& ?* [' C/ H) `# 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
. s9 N) e' D( e) i8 x8 e% Q# pcs constraint location add server1 VIP1 node1 1
% D! M( Z5 M& g+ ~2 \4 y/ f# pcs constraint location add server2 FS node2 1
* [$ `# O: Y) _. @# pcs constraint location add server2 VIP node2 1
3 P4 A2 A! \, s2 n3 o$ H& S' X# 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'