You've added the high-availability service to the public zone. Can you
verify that the interface you're using for pcsd is bound to the public
zone?
Check whether the https_proxy environment variable is set. You may
need to unset it or to add it to /etc/sysconfig/pcsd.
Just an FYI, the `--name`
Can you share your pacemaker configuration (i.e.,
/var/lib/pacemaker/cib/cib.xml)? If you're concerned about quorum,
then also share your /etc/corosync/corosync.conf just in case.
Also there's a db2 resource agent already written, if you're interested:
-
Hi,
I have DB2 resource agent scripted by myself.
It is working fine with a small glitch.
I have node1 and node2 in the cluster. No stonith enabled as I don't need one.
The environment is for learning purpose only.
If node one is down [power off], it is starting the resource on other node
Hi,
I have DB2 resource agent scripted by myself.
It is working fine with a small glitch.
I have node1 and node2 in the cluster. No stonith enabled as I don't need one.
The environment is for learning purpose only.
If one is down, it is starting the resource on other node which is good. My
>>> Ken Gaillot schrieb am 30.11.2020 um 19:52 in
>>> Nachricht
:
...
>
> Though there's nothing wrong with putting all nodes in standby. Another
> alternative would be to set the stop-all-resources cluster property.
Hi Ken,
thanks for the valuable feedback!
I was looking for that, but
