Hi
I reboot my node, and it appears
node2 pingd: [3932]: info: stand_alone_ping: Node 192.168.10.100 is
unreachable (read)
and the node could not start
192.168.10.100 is ib network I will start ib after the node start, so do
you have any idea let the node start first?Thanks very much.:-)
Don't use IP resources as ping nodes.
You should use the IP of something outside of your cluster, like an external
router
stand_alone_ping is start automatically, I have never start it by hand, so how
to set it ping external router.
Thanks
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs:
http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
-- next part --
An HTML attachment was scrubbed...
URL:
http://oss.clusterlabs.org/pipermail/pacemaker/attachments/2010/4d7f3ea1/attachment-0001.htm
--
Message: 3
Date: Thu, 11 Nov 2010 11:38:24 +0100
From: Simon Jansen simon.jans...@googlemail.com
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Multistate Resources is not promoted
automatically
Message-ID:
aanlktikwgmy4nutz4807vv2x=nn_smj+e8y1pru6x...@mail.gmail.com
Content-Type: text/plain; charset=iso-8859-1
Hi Andrew,
thank you for your answer.
Does the ocf:heartbeat:Rsyslog script call crm_master?
It needs to to tell pacemaker which instance to promote.
Yes it does. But I forgot to call crm_master with the option -D in the stop
action. I think that this was the error. After correcting this issue the ra
starts as expected.
Two questions though...
1) Why use master/slave for rsyslog?
In the master role the rsyslog daemon should function as central log server
and write the entries received on UDP port 514 into a MySQL database.
On the passive node the rsyslog service should be started with the standard
config.
Do you think there is a better solution to solve this requirement?
2) Is this an upstream RA? If not, you shouldn't be using the
ocf:heartbeat namespace.
Ok thank you for the advice. Should I use the pacemaker class instead or
should I define a custom namespace?
--
Regards,
Simon Jansen
---
Simon Jansen
64291 Darmstadt
-- next part --
An HTML attachment was scrubbed...
URL:
http://oss.clusterlabs.org/pipermail/pacemaker/attachments/2010/9e6d50bf/attachment-0001.htm
--
Message: 4
Date: Thu, 11 Nov 2010 11:44:47 +0100
From: Andrew Beekhof and...@beekhof.net
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Infinite fail-count and migration-threshold
after node fail-back
Message-ID:
aanlktimmlwzmhkxszchu95x0d2wgnjcujn-b7eowb...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Oct 11, 2010 at 9:40 AM, Dan Frincu dfri...@streamwide.ro wrote:
Hi all,
I've managed to make this setup work, basically the issue with a
symmetric-cluster=false and specifying the resources' location manually
means that the resources will always obey the location constraint, and (as
far as I could see) disregard the rsc_defaults resource-stickiness values.
This definitely should not be the case.
Possibly your stickiness setting is being eclipsed by the combination
of the location constraint scores.
Try INFINITY instead.
This behavior is not the expected one, in theory, setting
symmetric-cluster=false should affect whether resources are allowed to run
anywhere by default and the resource-stickiness should lock in place the
resources so they don't bounce from node to node. Again, this didn't happen,
but by setting symmetric-cluster=true, using the same ordering and
collocation constraints and the resource-stickiness, the behavior is the
expected one.
I don't remember seeing anywhere in the docs from clusterlabs.org being
mentioned that the resource-stickiness only works on
symmetric-cluster=true, so for anyone that also stumbles upon this issue,
I hope this helps.
Regards,
Dan
Dan Frincu wrote:
Hi,
Since it was brought to my attention that I should upgrade from
openais-0.80 to a more recent version of corosync, I've done just that,
however I'm experiencing a strange behavior on the cluster.
The same setup was used with the below packages:
# rpm -qa | grep -i (openais|cluster|heartbeat|pacemaker|resource)
openais-0.80.5-15.2
cluster-glue-1.0-12.2
pacemaker-1.0.5-4.2
cluster-glue-libs-1.0-12.2
resource-agents-1.0-31.5
pacemaker-libs-1.0.5-4.2
pacemaker-mgmt-1.99.2-7.2
libopenais2-0.80.5-15.2
heartbeat-3.0.0-33.3
pacemaker-mgmt-client-1.99.2-7.2
Now I've migrated to the most recent stable packages I could find (on the
clusterlabs.org website) for RHEL5:
# rpm -qa | grep -i
