Hi,
I'm sorry for my delay.
I tried the revision 0af0ef92b0fd,
(Medium: snmp_subagent: Improved for openais support
http://hg.clusterlabs.org/pacemaker/pygui/rev/0af0ef92b0fd)
and it worked well!
Many thanks!
Regards,
Junko
On Thu, 16 Jul 2009 23:32:42 +0900, Yan Gao wrote:
> Hi,
> On Thu, 20
On another note, what remote power device do you recommend for fencing an
UNCLEAN node?
-Original Message-
From: Eliot Gable [mailto:ega...@broadvox.com]
Sent: Tuesday, July 21, 2009 9:40 AM
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Master/Slave failover during reboot
Y
Yes, I realized that after upgrading to 1.0.4. When using 1.0.3, when I simply
issued a 'reboot' command at the prompt, the node would go offline in UNCLEAN
state. With 1.0.4, it just shows as OFFLINE without the UNCLEAN modifier. I am
just going to assume that I somehow botched the 1.0.3 instal
On 2009-07-20T15:27:23, Eliot Gable wrote:
> I have a resource that is configured as a Master/Slave resource. If I
> kill a resource it is dependent on, it properly fails over to the
> other node. However, if I reboot the master node, it does not fail
> over. What I see is that the master node sw
I have a resource that is configured as a Master/Slave resource. If I kill a
resource it is dependent on, it properly fails over to the other node. However,
if I reboot the master node, it does not fail over. What I see is that the
master node switches to UNCLEAN - Offline, the master resource
I guess I lied. I was running 1.0.3. After upgrading to 1.0.4, I do not seem to
have this problem anymore. At least, my first test resulted in exactly what I
would expect - the slave took over immediately upon issuing a reboot command on
the master. I will run some more tests and if I see it hap
