[Pacemaker] hangs pending

Andrew Beekhof andrew at beekhof.net
Wed Mar 19 23:07:59 EDT 2014

On 19 Mar 2014, at 4:00 pm, Andrey Groshev <greenx at yandex.ru> wrote:

> 19.03.2014, 03:29, "Andrew Beekhof" <andrew at beekhof.net>:
>> On 19 Mar 2014, at 6:19 am, Andrey Groshev <greenx at yandex.ru> wrote:
>>>  12.03.2014, 02:53, "Andrew Beekhof" <andrew at beekhof.net>:
>>>>  Sorry for the delay, sometimes it takes a while to rebuild the necessary context
>>>  I'm sorry too for the answer delay.
>>>  I switched to using "upstart" for initializing corosync and pacemaker (with respawn).
>>>  Now the behavior of the system has changed and it suits me. (yet :) )
>>>  I must kill crmd/lrmd in infinite loop, then STONITH shoot.
>>>  Else very fast respawn and do nothing.
>>>  Of course, I still found a other way to hang the system.
>>>  This requires only one idiot.
>>>  1. He decides to update pacemaker (and/or erase incomprehensible service).
>>>  2. Then kills the process corosync or simply reboot the server.
>>>  Everything! This node will remain hang in "pending".
>> While trying to shutdown?
>> Our spec files shut pacemaker down prior to upgrades FWIW.
> Not so simple ... we have a national tradition - care and cherish idiots. 
> Therefore, they are clever, quirky and unpredictable. ;)
> He can simply delete files of package, without uninstall. 
> (In reality, it may be just crash of the file system).

Dunno, I think hanging is somewhat reasonable behaviour if parts of pacemaker have been removed :)
It didn't get fenced though?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140320/df9fe985/attachment-0003.sig>

More information about the Pacemaker mailing list