Re: [ClusterLabs] Fwd: Issue with resource-agents ocf:heartbeat:mariadb

2021-04-09 Thread Ken Gaillot
Hi, I'm not very familiar with the mariadb agent, but one thing to check is that the output of "uname -n" can be used in the CHANGE MASTER command. If not, you need to set node attributes for the right names to use. I believe you have to configure and start replication manually once before the

[ClusterLabs] Fwd: Issue with resource-agents ocf:heartbeat:mariadb

2021-04-09 Thread Olivier POUILLY
Hi team, Thanks for this great job on those library. I would like to know if it was possible to get some help on the mariadb resource. After the configuration of my cluster pcs command shows me: root@node1:~# pcs status Cluster name: clusterserver Stack: corosync Current DC: node1 (version

Re: [ClusterLabs] Fwd: issue

2020-11-17 Thread Gerry R Sommerville
Hey Reid, and Guy,I want to clarify that Guy is using the Db2 built and packaged version of Pacemaker and Corosync released for technical preview to be used with Db2 V11.5.4.0. The db2cm utility and db2 specific resource agents (db2ethmon, db2inst, db2hadr) were developed and packaged by Db2, not

[ClusterLabs] Fwd: issue

2020-11-17 Thread Reid Wahl
Forwarding Guy's response to me, onward to the list. I work on the cluster support team at Red Hat and I'm not aware that we ship this db2cm script. Since you've said the script is defined by IBM and also Red Hat, where did you obtain the script? The resource agent script for