RA is not working anymore on RHEL7 / CentOS 7 / Ubuntu 14.04

[m4r1k]

Hi there,

I tried the resource agent with a PCS cluster with up to date OS (RHEL/CentOS 7.1 and Ubuntu 14.04.3) and up to date Percona Server (5.6.26-74.0-log and 5.6.27-75.0-log) and it is not working.
Creating a master/slave cluster the RA cannot initiate the M/S.

Brlow my my.cnf and the pacemaker config

node 1: SRVOWNSQL01
node 2: SRVOWNSQL02
primitive p_vip IPaddr2
params ip=172.28.107.200 cidr_netmask=24 nic=bond1
op start interval=0s timeout=20s
op stop interval=0s timeout=20s
op monitor interval=20s
meta target-role=Started
p_mysql ocf:percona:mysql
params config="/etc/my.cnf" pid="/var/lib/mysql/mysqld.pid" socket="/var/run/mysqld/mysqld.sock" replication_user="repl_user"
replication_passwd="_" max_slave_lag="60" evict_outdated_slaves="false" binary="/sbin/mysqld"
test_user="test_user" test_passwd="_******"
op monitor interval="5s" role="Master" OCF_CHECK_LEVEL="1"
op monitor interval="2s" role="Slave" OCF_CHECK_LEVEL="1"
op start interval="0" timeout="60s"
op stop interval="0" timeout="60s"
ms ms_MySQL p_mysql
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" notify="true" globally-unique="false" target-role="Master" is-managed="true"
colocation writer_on_master inf: p_vip ms_MySQL:Master
order ms_MySQL_promote_before_vip inf: ms_MySQL:promote p_vip:start
property cib-bootstrap-options:
stonith-enabled=false
no-quorum-policy=ignore
have-watchdog=false
dc-version=1.1.13-a14efad
cluster-infrastructure=corosync
cluster-name=DBCluster
last-lrm-refresh=1446108717
rsc_defaults rsc_defaults-options:
migration-threshold=1

[mysql]

CLIENT

port = 3306
socket = /var/lib/mysql/mysql.sock

[mysqld]

GENERAL

user = mysql
default-storage-engine = InnoDB
socket = /var/lib/mysql/mysql.sock
pid-file = /var/lib/mysql/mysql.pid
bind-address=0.0.0.0

relay-log=mysql-relay-bin

log-slave-updates

replicate-ignore-db=mysql

MyISAM

key-buffer-size = 32M
myisam-recover = FORCE,BACKUP

SAFETY

max-allowed-packet = 16M
max-connect-errors = 1000000

skip-name-resolve

sql-mode = STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY
sysdate-is-now = 1
innodb = FORCE
innodb-strict-mode = 1

DATA STORAGE

datadir = /var/lib/mysql/

BINARY LOGGING

log-bin = /var/lib/mysql/mysql-bin
expire-logs-days = 14
sync-binlog = 1
binlog_format = ROW
log-slave-updates

CACHES AND LIMITS

tmp-table-size = 32M
max-heap-table-size = 32M
query-cache-type = 0
query-cache-size = 0
max-connections = 100000
thread-cache-size = 500
open-files-limit = 65535
table-definition-cache = 4096
table-open-cache = 10000

INNODB

innodb-flush-method = O_DIRECT
innodb-log-files-in-group = 2
innodb-log-file-size = 512M
innodb-flush-log-at-trx-commit = 1
innodb-file-per-table = 1
innodb-buffer-pool-size = 32G

LOGGING

log-error = /var/lib/mysql/mysql-error.log
log-queries-not-using-indexes = 1
slow-query-log = 1
slow-query-log-file = /var/lib/mysql/mysql-slow.log

REPLICATION

server_id = 1
slave_transaction_retries=4294967295

[client-server]

include all files from the config directory

!includedir /etc/my.cnf.d

[m4r1k]

Ping !?!?!?

[y-trudeau]

I'll take a look

[y-trudeau]

Anything in the logs? Can you enable the trace file and see what is going on? To enable the trace:

mkdir /tmp/mysql.ocf.ra.debug
touch /tmp/mysql.ocf.ra.debug/log

The file should quickly grow, after a few events, do:

mv /tmp/mysql.ocf.ra.debug/log /tmp/mysql.ocf.ra.debug/log.1

and examine log.1. You can post an event here, sanitized for passwords.