On 26 Nov 2013, at 12:39 am, Andrey Groshev <gre...@yandex.ru> wrote:
>> ...snip... >>> Make next test: >>> #stonith_admin --reboot=dev-cluster2-node2 >>> Node reboot, but resource don't start. >>> In crm_mon status - Node dev-cluster2-node2 (172793105): pending. >>> And it will be hung. >> >> That is *probably* a race - the node reboots too fast, or still >> communicates for a bit after the fence has supposedly completed (if it's >> not a reboot -nf, but a mere reboot). We have had problems here in the >> past. >> >> You may want to file a proper bug report with crm_report included, and >> preferably corosync/pacemaker debugging enabled. > > It was found that he hangs not forever. > Triggered timeout - in 20 minutes. > crm_report archive - http://send2me.ru/pen2.tar.bz2 > Of course in the logs many type entries: > > pgsql:1: Breaking dependency loop at msPostgresql > > But where does this relationship after a timeout, I do not understand. Can you rephrase your question? I'm not 100% sure I understand what you're asking.
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