Hello,
I install Pacemaker in accordance with
http://clusterlabs.org/quickstart-ubuntu.html on Ubuntu 13.04 two nodes
changing only the IP addresses.
/etc/cluster/cluster.conf:
?xml version=1.0?
cluster config_version=1 name=pacemaker1
logging debug=off/
clusternodes
clusternode
Hi,
On 09/18/13 17:54, Lars Marowsky-Bree wrote:
On 2013-09-18T17:53:16, Gao,Yan y...@suse.com wrote:
actions-limit is a good name. (One of the three hard problems in
computer science! ;-)
(If we need it more fine grained at any point in the future, we can
always add class/provider/type/op
I've tried Googling for this, with little success. Wondering if someone
here can help.
I am operating Pacemaker in a clone configuration with multiple nodes
(usually between 4 and 6). In the event that one of the nodes fails, I
want one of the remaining nodes to perform a database update
Am a newbie to pacemaker, as far as my experience Pacemaker is not
configured properly, basically XML file is not properly configured. Check
for crm configure show xml and make sure the output is matching with
cluster lab examples.
Thanks.
On Thu, Sep 26, 2013 at 6:35 PM, Bartłomiej Wójcik
Hi,
I have a problem starting up a cluster after upgrading corosync from
1.4 to 2.3.2 and pacemaker from 1.8 to 1.9.
All crm_node calls report well, but any CIB manipulation fails, i.e.:
* crm_node -q: 1
* crm_node -l: OK
* crm_node -p: OK
* cibadmin -Q: Call cib_query failed (-62): Timer
On 26/09/2013, at 8:35 PM, Bartłomiej Wójcik bartlomiej.woj...@turbineam.com
wrote:
Hello,
I install Pacemaker in accordance with
http://clusterlabs.org/quickstart-ubuntu.html on Ubuntu 13.04 two nodes
changing only the IP addresses.
/etc/cluster/cluster.conf:
?xml version=1.0?
On 27/09/2013, at 8:45 AM, Radoslaw Garbacz
radoslaw.garb...@xtremedatainc.com wrote:
Hi,
I have a problem starting up a cluster after upgrading corosync from
1.4 to 2.3.2 and pacemaker from 1.8 to 1.9.
All crm_node calls report well, but any CIB manipulation fails, i.e.:
* crm_node
26.09.2013 17:55, Dermot Tynan wrote:
I've tried Googling for this, with little success. Wondering if someone
here can help.
I am operating Pacemaker in a clone configuration with multiple nodes
(usually between 4 and 6). In the event that one of the nodes fails, I
want one of the
