Hello -Am thinking that this is progress.
Have made some updates, but still getting the same result ("require others to
stonith node st15-mds1").
Referencing this link for the updates made:
http://www.hastexo.com/resources/hints-and-kinks/fencing-libvirtkvm-virtualized-cluster-nodes
Updates in
change to_syslog: yes to to_syslog: no like that you put all your logs in
/var/log/corosync.log
2012/6/29 Arnold Krille
> Hi all,
>
> this is a strange problem I seem to have: What pacemaker/corosync logs to
> rsyslog has deamon-names, severity-levels but no messages. So I see a lot
> of
> entr
- Original Message -
> From: "Andreas Stallmann"
> To: pacemaker@oss.clusterlabs.org
> Sent: Thursday, June 28, 2012 10:05:06 AM
> Subject: [Pacemaker] Resource is monitored only till promote... bug or
> config error?
>
>
>
>
>
>
>
> Hi!
>
>
>
> For some yet unknown rea
On 06/28/2012 01:29 PM, David Vossel wrote:
I've been looking into multistate resource colocations quite a bit this week.
I have a branch I'm working with that may improve this situation for you.
If you are feeling brave, test this branch out with your configuration and see
if it fairs better
Hi -
Am new to pacemaker and now have a shiny new configuration that will not
stonith. This is a test system using KVM and external/libvirt - all VMs are
running CentOS 5.
Am (really) hoping someone might be willing to help troubleshoot this
configuration. Thank you for your time and effor
On 06/29/2012 01:42 AM, Dan Frincu wrote:
> Hi,
>
> On Thu, Jun 28, 2012 at 6:13 PM, Andrew Martin wrote:
>> Hi Dan,
>>
>> Thanks for the help. If I configure the network as I described - ring 0 as
>> the network all 3 nodes are on, ring 1 as the network only 2 of the nodes
>> are on, and using "
- Original Message -
> From: "Andreas Stallmann"
> To: pacemaker@oss.clusterlabs.org
> Sent: Thursday, June 28, 2012 10:05:06 AM
> Subject: [Pacemaker] Resource is monitored only till promote... bug or
> config error?
>
>
>
>
>
>
>
> Hi!
>
>
>
> For some yet unknown rea
On Friday 29 June 2012 13:13:37 Arnold Krille wrote:
> this is a strange problem I seem to have: What pacemaker/corosync logs to
> rsyslog has deamon-names, severity-levels but no messages. So I see a lot of
> entries in the logs, I see where they come from and whether the are
> important but I don
Hi all,
this is a strange problem I seem to have: What pacemaker/corosync logs to
rsyslog has deamon-names, severity-levels but no messages. So I see a lot of
entries in the logs, I see where they come from and whether the are important
but I don't see the messages themselv. That is the parts t
On Jun 28, 2012, at 10:26 PM, renayama19661...@ybb.ne.jp wrote:
>> We set order limitation as follows.
>
> with-rsc="msPostgresql" with-rsc-role="Master"/>
> score="INFINITY" then="msPostgresql" then-action="promote"/>
>
>> However, promote was carried out even if primitvei resource
Hi,
On Thu, Jun 28, 2012 at 6:13 PM, Andrew Martin wrote:
> Hi Dan,
>
> Thanks for the help. If I configure the network as I described - ring 0 as
> the network all 3 nodes are on, ring 1 as the network only 2 of the nodes
> are on, and using "passive" - and the ring 0 network goes down, corosync
11 matches
Mail list logo
