On 22 Jan 2014, at 2:52 pm, Bob Haxo <bh...@sgi.com> wrote:

> I have filed a bug, including crm_report, against my encounter with what 
> seems to be the issue being referred to in this thread. 
> 
> Bug 5191 - pcs stonith confirm server doesn't

Didn't you file one with RH too?  Just one is enough :-)
Current state is... why on earth doesn't fenced leave the "manual ack" pipe 
open for longer than 3s!

> 
> "stonith_admin --confirm=server" appears to behave the same as "pcs stonith 
> confirm server"
> 
> I found  "fence_ack_manual server" to successfully provided the needed ack 
> that stonith has been successful.
> 
> Bob Haxo
> 
> 
> On Mon, 2014-01-13 at 14:58 +1100, Andrew Beekhof wrote:
>> On 10 Jan 2014, at 3:54 pm, Nikita Staroverov <nsfo...@gmail.com> wrote:
>> 
>> 
>> 
>> > 
>> >>>> There is no-one to tell yet.
>> >>>> We have to wait for cman to decide something needs fencing before 
>> >>>> pacemaker can perform the notification.
>> >>>> 
>> >>> if I get you right i need own fencing agent that doing manual confirmed 
>> >>> fence action with cman+pacemaker configurations, do i?
>> >> No.  Manual fencing confirmations can only work after CMAN asks for the 
>> >> node to be fenced.  You can't tell it in advance.
>> > I'll try to explain my problem again. :)
>> > in my test setup cluster member  was manually powered off by me and fence 
>> > device was powered off too.
>> > crm_mon shows host as offline unclean.
>> > cman shows that host needs fencing and try to do that by fence_pcmk.
>> > Fence agent in pacemaker can't do that because fence device is 
>> > unreacheable.
>> > i do stonith_admin -C for node. After that crm_mon shows host as offline. 
>> > cman tries to do fencing indefinitly.
>> > I think pacemaker doesn't notify cman that fencing was confirmed by 
>> > sysadmin.
>> 
>> 
>> 
>> Code seems to be trying to...
>> Do you see any logs from tengine_stonith_notify after you run stonith_admin?
>> 
>> 
>> 
>> crm_report?
>> _______________________________________________
>> 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://bugs.clusterlabs.org

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
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://bugs.clusterlabs.org

Reply via email to