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

admin

# pcs status
Cluster name: my_wsrep_cluster
Stack: 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
* H- d  R# @; K; a$ E+ JLast change: Thu Dec 28 18:05:11 2017 by root via cibadmin on controller1
# |$ E: l/ j* m& ^7 d% S3 _  ~- r3 nodes configured
1 resource configured
Online: [ controller1 controller2 controller3 ]
Full list of resources:
7 ]# B; i! o3 r, B# x; @. b& I db (ocf::heartbeat:galera): Stopped
! m. x" b* a( M$ t0 e& 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

8 o0 m% ]2 r) b. o3 V6 YDaemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
, k$ l4 d# V9 ^' _) B8 F1 X  pcsd: active/enabled

9 ]5 z% ]+ {: ?* a6 G- |$ o& }所有的状态都是active的，唯独只有db状态是stopped，为什么呢？

admin

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

admin

配置一个mariadb服务
6 o2 [) h1 M7 a/ A. \/ q+ v! n在所有节点上执行
! B6 C. u+ |, t# yum install mariadb-* -y
9 I. @. ~2 t9 c; J+ Z1 x# systemctl disable mariadb
# systemctl status mariadb
6 B5 i2 j0 N: E! v# S# pcs create resource DB ocf:heartbear:mysql
配置一个互为备份的双机环境，一个节点作为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
# pcs constraint location add server1 VIP1 node1 1
2 [. T8 ~3 |: A" R/ U6 n# pcs constraint location add server2 FS node2 1
# pcs constraint location add server2 VIP node2 1
# pcs constraint location add server2 WEB node2 1
  x" D' q/ D0 |; r执行上述命令后，DB和VIP1将启动在node1上而剩下的FS VIP WEB将启动在node2上

admin

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

admin

controller_start_0 on controller1 'unknown error'