Hi All,
I had a 3 node HB+pacemaker setup. When I restarted the nodes, all the
nodes have HB restarted but they are not joining ONLINE group in crm
status.
#vim /etc/ha.d/ha.cf
..
node nvsd-1 nvsd-2 nvp-common
crm respawn
Dec 10 14:13:48 nvp-common
Am Dienstag, 10. Dezember 2013, 14:30:32 schrieb ESWAR RAO:
Hi All,
I had a 3 node HB+pacemaker setup. When I restarted the nodes, all the
nodes have HB restarted but they are not joining ONLINE group in crm
status.
#vim /etc/ha.d/ha.cf
..
node nvsd-1 nvsd-2
On 09/12/13 23:01, Brian J. Murrell wrote:
So, I'm trying to wrap my head around this need to migrate to pacemaker
+CMAN. I've been looking at
http://clusterlabs.org/quickstart-redhat.html and
Hi Micheal,
There are no firewall rules.
I could only see below messages in logs:
Dec 10 14:13:48 nvp-common crmd: [9220]: WARN: crmd_ha_msg_callback:
Ignoring HA message (op=join_announce) from nvsd-1: not in our membership
list (size=1)
On Tue, Dec 10, 2013 at 2:46 PM, Michael
On Tue, 2013-12-10 at 10:27 +, Christine Caulfield wrote:
Sadly you're not wrong.
That's what I was afraid of.
But it's actually no worse than updating
corosync.conf manually,
I think it is...
in fact it's pretty much the same thing,
Not really. Updating corosync.conf on any
On 10/12/13 12:31, Brian J. Murrell wrote:
On Tue, 2013-12-10 at 10:27 +, Christine Caulfield wrote:
Sadly you're not wrong.
That's what I was afraid of.
But it's actually no worse than updating
corosync.conf manually,
I think it is...
in fact it's pretty much the same thing,
Not
version of pacemaker?
On 10 Dec 2013, at 10:41 pm, ESWAR RAO eswar7...@gmail.com wrote:
Hi Micheal,
There are no firewall rules.
I could only see below messages in logs:
Dec 10 14:13:48 nvp-common crmd: [9220]: WARN: crmd_ha_msg_callback: Ignoring
HA message (op=join_announce) from
On 10 Dec 2013, at 11:31 pm, Brian J. Murrell br...@interlinx.bc.ca wrote:
On Tue, 2013-12-10 at 10:27 +, Christine Caulfield wrote:
Sadly you're not wrong.
That's what I was afraid of.
But it's actually no worse than updating
corosync.conf manually,
I think it is...
in
Hi Andrew,
# pacemakerd --version
Pacemaker 1.1.7
Written by Andrew Beekhof
# ps -aef|grep heart
root 8926 1 0 20:02 ?00:00:00 heartbeat: master control
process
root 8930 8926 0 20:02 ?00:00:00 heartbeat: FIFO reader
root 8931 8926 0 20:02 ?
Hi Micheal,
I am configuring the ClusterMon as below on the 3 node setup:
I am following
http://floriancrouzat.net/2013/01/monitor-a-pacemaker-cluster-with-ocfpacemakerclustermon-andor-external-agent/
# crm configure primitive ClusterMon ocf:pacemaker:ClusterMon params
user=root update=10
Hi All,
When I ran below configuration on a 3 node HB+pacemaker setup I am getting
WARNING: Resources cluster-ip,nvp_vip violate uniqueness for parameter
ip: 192.168.101.205
Do you still want to commit? y
++
# crm configure primitive
11 matches
Mail list logo