So we use old version of pacemaker? What version should we update to?
On 01/04/2013 11:57 AM, Andrew Beekhof wrote:
On Fri, Jan 4, 2013 at 8:30 PM, Michal Fiala fi...@mfiala.net wrote:
Hallo,
thanks for information. We are using corosync-1.4.4 and
pacemaker-1.1.6.1.
Oh, thats the old lrmd
Hello,
is there a way how to online add a new node to corosync/pacemaker
cluster, where nodes communicate by unicast UDP?
Thanks
Michal
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
On 05/08/2013 01:17 AM, Andrew Beekhof wrote:
On 07/05/2013, at 11:42 PM, Michal Fiala fi...@mobil.cz wrote:
Hallo,
I have updated corosync/pacemaker cluster, versions see bellow. Cluster
is working fine, but when I change configuration via crm configure edit,
crm_mon is exited
Hi,
it works, thank you.
M.
On 07/17/2015 10:32 AM, Vladislav Bogdanov wrote:
17.07.2015 10:46, Dejan Muhamedagic wrote:
[...]
The attribute is not listed in the PE meta-data and therefore
considered an error. You can make crmsh less strict like this:
# crm option set core.check_mode
Hi,
I am running 2 node cluster with simple configuration for mysql
replication. Resource agent mysql (ocf:heartbeat:mysql) saves
replication info into property mysql_replication but this property is is
unknown by crm shell when changing configuration.
using distro Gentoo and package versions:
