Re: [Pacemaker] monitor operation is not resumed

Hi David, I reported it in Bugzilla. Please confirm it. * http://bugs.clusterlabs.org/show_bug.cgi?id=5063 Best Regards, Kazunori INOUE (12.05.07 23:45), David Vossel wrote: - Original Message - From: "Kazunori INOUE" To: "pacemaker@oss" Sent: Monday, May 7, 2012 4:52:58 AM Subject: [

[Pacemaker] crm node online NODE-2 hangs

From NODE-2 I run: crm node online NODE-2 It hangs, actually I got a timeout with this error: Error setting standby=off ... Remote node did not respond crm_mon from NODE-2 identifies NODE-2 as OFFLINE (with no resources) crm_mon from NODE-3 identifies NODE-2 as ONLINE as managing resources fro

Re: [Pacemaker] monitor operation is not resumed

- Original Message - > From: "Kazunori INOUE" > To: "pacemaker@oss" > Sent: Monday, May 7, 2012 4:52:58 AM > Subject: [Pacemaker] monitor operation is not resumed > > Hi, > > I am using Pacemaker-1.1. > - pacemaker : db5e16736cc2682fbf37f81cd47be7d17d5a2364 > - glue : 2686:66d5f0c1

[Pacemaker] monitor operation is not resumed

Hi, I am using Pacemaker-1.1. - pacemaker : db5e16736cc2682fbf37f81cd47be7d17d5a2364 - glue : 2686:66d5f0c135c9 A monitor is not resumed even if I changed enabled="false" into enabled="true". * 0. monitor is performed periodically. # crm configure show node $id="1" vm1 node $id="2" vm2

[Pacemaker] STONITH is not performed after stonithd reboots

Hi, On the Pacemkaer-1.1 + Corosync stack, although stonithd reboots after an abnormal end, STONITH is not performed after that. I am using the newest devel. - pacemaker : db5e16736cc2682fbf37f81cd47be7d17d5a2364 - corosync : 88dd3e1eeacd64701d665f10acbc40f3795dd32f - glue : 2686:66d5f0c135

[Pacemaker] Question about crmsh

Hello, We are checking the feature of Pacemaker-1.1. Since fencing topology(*) is a new feature, we pay attention and use it. * https://github.com/ClusterLabs/pacemaker/blob/master/xml/fencing.rng So when is 'fencing topology' implemented in crmsh? Best regards, Kazunori INOUE

[Pacemaker] Question about config

Hi, On the Pacemkaer-1.1 + Corosync stack, is it specification not to read 'service' directive (use_logd option)? * https://github.com/ClusterLabs/pacemaker/blob/db5e16736cc2682fbf37f81cd47be7d17d5a2364/mcp/corosync.c#L520 Is it a future policy to set these options in /etc/sysconfig/pacemaker? a

[Pacemaker] Question about behavior when pacemakerd was terminated

Hi, I am using Pacemaker-1.1 (devel: db5e167). When stonith-enabled is "false", and pacemakerd is terminated abnormally, the states differ by whether a node is DC. - (1-a) pacemakerd of DC node was terminated -> OFFLINE - (1-b) pacemakerd of non-DC node was terminated -> UNCLEAN (offline) Is