<html><body>
<p>Dear Mr. Mr.<tt>Andrew Beekhof</tt>,<br>
<br>
<tt>Why errors like below which are related to pacemaker are appearing at 15 minutes interval in our message file of the server.</tt><br>
<br>
<tt>pengine: [3143]: ERROR: create_notification_boundaries: Creating<br>
> > boundaries for mysql-ms-drbd</tt><br>
<br>
Regards,<br>
Gururaj Patil<br>
Systems Department<br>
Business Standard Ltd.<br>
Worli<br>
Mumbai - 400013<br>
India<br>
Ph.+91-22-24971924<br>
<br>
<br>
<img width="16" height="16" src="cid:1__=EABBF249DF855A308f9e8a93df9386@bsmail.in" border="0" alt="Inactive hide details for pacemaker-request---07/27/2011 08:22:12 AM---Send Pacemaker mailing list submissions to pacemaker@os"><font color="#424282">pacemaker-request---07/27/2011 08:22:12 AM---Send Pacemaker mailing list submissions to pacemaker@oss.clusterlabs.org</font><br>
<br>
<font size="2" color="#5F5F5F">From: </font><font size="2">pacemaker-request@oss.clusterlabs.org</font><br>
<font size="2" color="#5F5F5F">To: </font><font size="2">pacemaker@oss.clusterlabs.org</font><br>
<font size="2" color="#5F5F5F">Date: </font><font size="2">07/27/2011 08:22 AM</font><br>
<font size="2" color="#5F5F5F">Subject: </font><font size="2">Pacemaker Digest, Vol 44, Issue 54</font><br>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<tt>Send Pacemaker mailing list submissions to<br>
pacemaker@oss.clusterlabs.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
or, via email, send a message with subject or body 'help' to<br>
pacemaker-request@oss.clusterlabs.org<br>
<br>
You can reach the person managing the list at<br>
pacemaker-owner@oss.clusterlabs.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Pacemaker digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Reload action and stop/start sequence questions<br>
(Andrew Beekhof)<br>
2. Re: Cluster type is: corosync (Andrew Beekhof)<br>
3. Re: Business Standard India - Errors noticed in pacemaker<br>
(Andrew Beekhof)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 27 Jul 2011 12:25:02 +1000<br>
From: Andrew Beekhof <andrew@beekhof.net><br>
To: The Pacemaker cluster resource manager<br>
<pacemaker@oss.clusterlabs.org><br>
Subject: Re: [Pacemaker] Reload action and stop/start sequence<br>
questions<br>
Message-ID:<br>
<CAEDLWG0URPu_VOVzUDZ4RZoEvfeWVdEXQC1y9zQKxd0pGmErXg@mail.gmail.com><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Mon, Jul 11, 2011 at 5:45 PM, Vladislav Bogdanov<br>
<bubble@hoster-ok.com> wrote:<br>
> Hi all,<br>
><br>
> Would somebody (Andrew?) please bring some light on how exactly<br>
> redefinition of resource is supposed to be handled?<br>
><br>
> Below is my (rather perfectionistic) vision on this, please correct me<br>
> if/where I'm wrong:<br>
> * If RA supports 'reload' action then it is called on resource<br>
> definition change (instead of stop/start).<br>
<br>
Only if the attribute changed was NOT marked as "unique" in the metadata.<br>
<br>
> * If 'reload' action fails then usual start/stop sequence is executed.<br>
> This would give a chance to RA to refuse to reload if some key<br>
> properties change, while allowing it to tune some secondary resource<br>
> parameters. Of course, RA should leave resource in a usable state, so<br>
> failure of reload action should indicate RA's denial to do a reload. How<br>
> to differentiate that from real reload failures?<br>
<br>
Either way the resource needs to be restarted. So there is no need<br>
for differentiation.<br>
<br>
> Is there some special<br>
> exit code for that?<br>
> * Dependent resources should not be stopped/started for 'reload' action.<br>
> Of course they are restarted if reload fails and stop/start is executed<br>
> then. (I see that they are restarted now for reload of a resource they<br>
> depend on, is it a bug?)<br>
<br>
More like a limitation. Which is a round-a-bout way of saying "really<br>
hard to fix bug".<br>
You're welcome to create a BZ for it though, maybe one day I'll figure<br>
out how to resolve it.<br>
<br>
> * (wish) Resources should be migrated out of node (if they support live<br>
> migration) for stop/start sequence of resource they depend on.<br>
<br>
Migration can only occur if a resource at the bottom (excluding any<br>
clones) of the resource stack.<br>
In order to migrate any colocation dependancies need to be running at<br>
_both_ the old and the new locations.<br>
<br>
This can only be true for resources that depend on clones.<br>
<br>
> * (wish) Redefinition of clones should be handled in a way which allows<br>
> dependent live-migratable resources to survive (if reload action for<br>
> clone instance either is not supported or fails).<br>
<br>
This doesn't make sense.<br>
If the definition of one clone changes, then they all change and there<br>
is nowhere for dependant resources to migrate to.<br>
<br>
> That is: dependent<br>
> resources which support live migration are first tried to migrate out of<br>
> one node, and are stopped if migration fails. Then clone instance is<br>
> restarted on that node. Then the same procedure applies to next cluster<br>
> node so resources may return back to a first node.<br>
><br>
> If above (at least first three points) is right, then is it possible to<br>
> get a set of previous instance parameters the same way new configuration<br>
> is passed (env vars), or RA should save that information itself in advance?<br>
><br>
> Best,<br>
> Vladislav<br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>
> </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
><br>
> Project Home: </tt><tt><a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></tt><tt><br>
> Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></tt><tt><br>
> Bugs: </tt><tt><a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a></tt><tt><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 27 Jul 2011 12:41:35 +1000<br>
From: Andrew Beekhof <andrew@beekhof.net><br>
To: The Pacemaker cluster resource manager<br>
<pacemaker@oss.clusterlabs.org><br>
Subject: Re: [Pacemaker] Cluster type is: corosync<br>
Message-ID:<br>
<CAEDLWG3rcFDM1ew8eTne5U2R25QL3rkoS5ZFY_oM6OHxZtL0QA@mail.gmail.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Tue, Jul 26, 2011 at 5:12 PM, Proskurin Kirill<br>
<k.proskurin@corp.mail.ru> wrote:<br>
> On 07/26/2011 11:00 AM, Andrew Beekhof wrote:<br>
>><br>
>> On Mon, Jul 25, 2011 at 7:18 PM, Proskurin Kirill<br>
>> <k.proskurin@corp.example.com> ?wrote:<br>
>>><br>
>>> 25.07.2011 10:10, Andrew Beekhof ?????:<br>
>>>><br>
>>>> Which packages are you using?<br>
>>><br>
>>> It is your official source from repository I build.<br>
>><br>
>> Ok. And did you add the pacemaker configuration options to corosync's<br>
>> config file?<br>
><br>
><br>
> I attach our corosync.conf. It is same on all nodes except IP addr.<br>
<br>
You missed a step from:<br>
</tt><tt><a href="http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/s-configure-corosync.html">http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/s-configure-corosync.html</a></tt><tt><br>
<br>
> Pacemaker is black now - no configuration at all.<br>
><br>
> Online nodes:<br>
> [root@mysender1 ~]# crm configure show<br>
> node mysender1.example.com<br>
> node mysender2.example.com<br>
> node mysender3.example.com<br>
> node mysender4.example.com<br>
> node mysender5.example.com<br>
> node mysender6.example.com<br>
> node mysender7.example.com<br>
> property $id="cib-bootstrap-options" \<br>
> ? ? ? ?dc-version="1.1.5-3-01e86afaaa6d4a8c4836f68df80ababd6ca3902f" \<br>
> ? ? ? ?cluster-infrastructure="openais" \<br>
> ? ? ? ?expected-quorum-votes="6"<br>
><br>
><br>
> Offline nodes(Cluster type is: corosync)<br>
> [root@mysender2 ~]# crm configure show<br>
> [root@mysender2 ~]#<br>
><br>
><br>
>><br>
>>> pacemaker-1.1.5<br>
>>> corosync-1.4.0<br>
>>> cluster-glue-1.0.6<br>
>>> openais-1.1.2<br>
>>><br>
>>> All nodes have same rpms.<br>
>>><br>
>>>> On Fri, Jul 22, 2011 at 7:47 PM, Proskurin Kirill<br>
>>>> <k.proskurin@corp.example.com> ? ?wrote:<br>
>>>>><br>
>>>>> Hello again!<br>
>>>>><br>
>>>>> Hope I`m not flooding too much here but I have another problem.<br>
>>>>><br>
>>>>> I install same rpm of corosync, openais, pacemaker, cluster_glue on all<br>
>>>>> nodes. I check it twice.<br>
>>>>><br>
>>>>> And then I start some of they - they can`t connect to cluster and stays<br>
>>>>> offline. In logs I see what they see other nodes and connectivity is<br>
>>>>> ok.<br>
>>>>> But<br>
>>>>> I found the difference:<br>
>>>>><br>
>>>>> Online nodes in cluster have:<br>
>>>>> [root@mysender39 ~]# grep 'Cluster type is' /var/log/corosync.log<br>
>>>>> Jul 22 20:38:58 mysender39.example.com stonith-ng: [3499]: info:<br>
>>>>> get_cluster_type: Cluster type is: 'openais'.<br>
>>>>> Jul 22 20:38:58 mysender39.example.com attrd: [3502]: info:<br>
>>>>> get_cluster_type:<br>
>>>>> Cluster type is: 'openais'.<br>
>>>>> Jul 22 20:38:58 mysender39.example.com cib: [3500]: info:<br>
>>>>> get_cluster_type:<br>
>>>>> Cluster type is: 'openais'.<br>
>>>>> Jul 22 20:38:59 mysender39.example.com crmd: [3504]: info:<br>
>>>>> get_cluster_type:<br>
>>>>> Cluster type is: 'openais'.<br>
>>>>><br>
>>>>> Offline have:<br>
>>>>> [root@mysender2 ~]# grep 'Cluster type is' /var/log/corosync.log<br>
>>>>> Jul 22 13:39:17 mysender2.example.com stonith-ng: [9028]: info:<br>
>>>>> get_cluster_type: Cluster type is: 'corosync'.<br>
>>>>> Jul 22 13:39:17 mysender2.example.com attrd: [9031]: info:<br>
>>>>> get_cluster_type:<br>
>>>>> Cluster type is: 'corosync'.<br>
>>>>> Jul 22 13:39:17 mysender2.example.com cib: [9029]: info:<br>
>>>>> get_cluster_type:<br>
>>>>> Cluster type is: 'corosync'.<br>
>>>>> Jul 22 13:39:18 mysender2.example.com crmd: [9033]: info:<br>
>>>>> get_cluster_type:<br>
>>>>> Cluster type is: 'corosync'.<br>
>>>>><br>
>>>>> What`s wrong and how can I fix it?<br>
><br>
> --<br>
> Best regards,<br>
> Proskurin Kirill<br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>
> </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
><br>
> Project Home: </tt><tt><a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></tt><tt><br>
> Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></tt><tt><br>
> Bugs:<br>
> </tt><tt><a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a></tt><tt><br>
><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 27 Jul 2011 12:48:28 +1000<br>
From: Andrew Beekhof <andrew@beekhof.net><br>
To: The Pacemaker cluster resource manager<br>
<pacemaker@oss.clusterlabs.org><br>
Cc: Prafulla H Patil <prafulla.patil@bsmail.in>, Bandana Roy<br>
<bandana.roy@bsmail.in><br>
Subject: Re: [Pacemaker] Business Standard India - Errors noticed in<br>
pacemaker<br>
Message-ID:<br>
<CAEDLWG2t+hnb9N5DjY3gAm5Xw84JxQTQtrP+un1QK=BFv4pL_g@mail.gmail.com><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
On Tue, Jul 26, 2011 at 5:35 PM, Gururaj B Patil <gururaj.patil@bsmail.in>wrote:<br>
<br>
> Dear Mr.Andrew Beekhof<br>
><br>
> Yes I did try googeling but could not get proper information. In few forums<br>
> I noticed message as below.<br>
><br>
> "That's development logging, which was accidentally bumped to a higher<br>
> log level."<br>
><br>
<br>
What was unclear about this?<br>
<br>
<br>
><br>
><br>
> We are searching again but meanwhile can pacemaker team help on this.<br>
><br>
> Regards,<br>
> Gururaj Patil<br>
><br>
> [image: Inactive hide details for pacemaker-request---07/26/2011 12:47:15<br>
> PM---Send Pacemaker mailing list submissions to pacemaker@os]pacemaker-request---07/26/2011<br>
> 12:47:15 PM---Send Pacemaker mailing list submissions to<br>
> pacemaker@oss.clusterlabs.org<br>
><br>
> From: pacemaker-request@oss.clusterlabs.org<br>
> To: pacemaker@oss.clusterlabs.org<br>
> Date: 07/26/2011 12:47 PM<br>
> Subject: Pacemaker Digest, Vol 44, Issue 50<br>
> ------------------------------<br>
><br>
><br>
><br>
> Send Pacemaker mailing list submissions to<br>
> pacemaker@oss.clusterlabs.org<br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
> or, via email, send a message with subject or body 'help' to<br>
> pacemaker-request@oss.clusterlabs.org<br>
><br>
> You can reach the person managing the list at<br>
> pacemaker-owner@oss.clusterlabs.org<br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of Pacemaker digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. Re: Business Standard India - Errors noticed in pacemaker<br>
> (Andrew Beekhof)<br>
> 2. Re: Cluster type is: corosync (Andrew Beekhof)<br>
> 3. Please teach it about handling of the unmanaged resource in<br>
> environment setting placement-strategy. (Yuusuke IIDA)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Tue, 26 Jul 2011 16:02:30 +1000<br>
> From: Andrew Beekhof <andrew@beekhof.net><br>
> To: The Pacemaker cluster resource manager<br>
> <pacemaker@oss.clusterlabs.org><br>
> Cc: M A Faruqui <m.faruqui@bsmail.in>, Prafulla H Patil<br>
> <prafulla.patil@bsmail.in>, Bandana Roy <bandana.roy@bsmail.in><br>
> Subject: Re: [Pacemaker] Business Standard India - Errors noticed in<br>
> pacemaker<br>
> Message-ID:<br>
> <CAEDLWG0ExctnrJq8KduV8JdC3hZTVSovB7gDnYv4MVpPox_cBw@mail.gmail.com><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> Thought about googling the error?<br>
><br>
> On Mon, Jul 25, 2011 at 9:17 PM, Gururaj B Patil <gururaj.patil@bsmail.in<br>
> >wrote:<br>
><br>
> > To support staff,<br>
> ><br>
> > We in Business Standard Ltd. use pacemaker as clusttering application for<br>
> > one of our website. Two servers are are in clusttering mode.<br>
> ><br>
> > One of the server is web server and another one is mysql db server.<br>
> > Pacemaker handles Mysql clustering at block level.<br>
> ><br>
> > We have noticed same type of notice and warning in the server's message<br>
> > file. Errors are as below.<br>
> ><br>
> ><br>
> ><br>
> -----------------------------------------------------------------------------------------------------------------------------------------------<br>
> > Messages like below appear every 15 minutes<br>
> ><br>
> > sidrbd0 pengine: [3143]: notice: get_failcount: Failcount for sipdu1 on<br>
> > sidrbd0 has expired (limit was 20s)<br>
> ><br>
> > sidrbd0 pengine: [3143]: ERROR: create_notification_boundaries: Creating<br>
> > boundaries for mysql-ms-drbd<br>
> ><br>
> ><br>
> ><br>
> -----------------------------------------------------------------------------------------------------------------------------------------------<br>
> ><br>
> > I have registered for pacemaker mailing list also.<br>
> ><br>
> > Regards,<br>
> > Gururaj Patil<br>
> > Systems Department<br>
> > Business Standard Ltd.<br>
> > H3/4, Paragon center,<br>
> > P.B.Marg,<br>
> > Worli<br>
> > Mumbai - 400013<br>
> > India<br>
> ><br>
> > Ph.+91-22-24971924<br>
> > ------------------------------<br>
> ><br>
> ><br>
> ><br>
> > *Disclaimer:* "This communication/message is for the named addressees<br>
> > only. This transmission may contain information that is privileged,<br>
> > confidential, proprietary or legally privileged, and /or exempt from<br>
> > disclosure under applicable law. If you are not the intended recipient,<br>
> > please immediately notify the sender and destroy the material in its<br>
> > entirety, whether in electronic or hard copy format. You are hereby<br>
> notified<br>
> > that any disclosure, copying, distribution, or use of the information<br>
> > contained herein (including any reliance thereon) is STRICTLY<br>
> PROBHIBITED.<br>
> > You must not, directly or indirectly, use, disclose, distribute, print or<br>
> > copy any part of this message."<br>
> ><br>
> > *WARNING :*"This electronic mail and any attachments are believed to be<br>
> > free of any virus or other defect, the recipient must ensure that it is<br>
> > virus free and no responsibility is accepted by Business Standard Limited<br>
> > and /or its employees as applicable for any loss or damage arising in any<br>
> > way from its use."<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>
> > </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
> ><br>
> > Project Home: </tt><tt><a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></tt><tt><br>
> > Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></tt><tt><br>
> > Bugs:<br>
> ><br>
> </tt><tt><a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a></tt><tt><br>
> ><br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> </tt><tt><a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110726/4d99749e/attachment-0001.html">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110726/4d99749e/attachment-0001.html</a></tt><tt><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Tue, 26 Jul 2011 17:00:56 +1000<br>
> From: Andrew Beekhof <andrew@beekhof.net><br>
> To: Pacemaker@oss.clusterlabs.org<br>
> Subject: Re: [Pacemaker] Cluster type is: corosync<br>
> Message-ID:<br>
> <CAEDLWG1s=AHrdXdWdO0r04410j0+Ygj7VfAz_Yf_0fMDpiNorA@mail.gmail.com><br>
> Content-Type: text/plain; charset=UTF-8<br>
><br>
> On Mon, Jul 25, 2011 at 7:18 PM, Proskurin Kirill<br>
> <k.proskurin@corp.mail.ru> wrote:<br>
> > 25.07.2011 10:10, Andrew Beekhof ?????:<br>
> >><br>
> >> Which packages are you using?<br>
> ><br>
> > It is your official source from repository I build.<br>
><br>
> Ok. And did you add the pacemaker configuration options to corosync's<br>
> config file?<br>
><br>
> > pacemaker-1.1.5<br>
> > corosync-1.4.0<br>
> > cluster-glue-1.0.6<br>
> > openais-1.1.2<br>
> ><br>
> > All nodes have same rpms.<br>
> ><br>
> >> On Fri, Jul 22, 2011 at 7:47 PM, Proskurin Kirill<br>
> >> <k.proskurin@corp.mail.ru> ?wrote:<br>
> >>><br>
> >>> Hello again!<br>
> >>><br>
> >>> Hope I`m not flooding too much here but I have another problem.<br>
> >>><br>
> >>> I install same rpm of corosync, openais, pacemaker, cluster_glue on all<br>
> >>> nodes. I check it twice.<br>
> >>><br>
> >>> And then I start some of they - they can`t connect to cluster and stays<br>
> >>> offline. In logs I see what they see other nodes and connectivity is<br>
> ok.<br>
> >>> But<br>
> >>> I found the difference:<br>
> >>><br>
> >>> Online nodes in cluster have:<br>
> >>> [root@mysender39 ~]# grep 'Cluster type is' /var/log/corosync.log<br>
> >>> Jul 22 20:38:58 mysender39.mail.ru stonith-ng: [3499]: info:<br>
> >>> get_cluster_type: Cluster type is: 'openais'.<br>
> >>> Jul 22 20:38:58 mysender39.mail.ru attrd: [3502]: info:<br>
> get_cluster_type:<br>
> >>> Cluster type is: 'openais'.<br>
> >>> Jul 22 20:38:58 mysender39.mail.ru cib: [3500]: info:<br>
> get_cluster_type:<br>
> >>> Cluster type is: 'openais'.<br>
> >>> Jul 22 20:38:59 mysender39.mail.ru crmd: [3504]: info:<br>
> get_cluster_type:<br>
> >>> Cluster type is: 'openais'.<br>
> >>><br>
> >>> Offline have:<br>
> >>> [root@mysender2 ~]# grep 'Cluster type is' /var/log/corosync.log<br>
> >>> Jul 22 13:39:17 mysender2.mail.ru stonith-ng: [9028]: info:<br>
> >>> get_cluster_type: Cluster type is: 'corosync'.<br>
> >>> Jul 22 13:39:17 mysender2.mail.ru attrd: [9031]: info:<br>
> get_cluster_type:<br>
> >>> Cluster type is: 'corosync'.<br>
> >>> Jul 22 13:39:17 mysender2.mail.ru cib: [9029]: info: get_cluster_type:<br>
> >>> Cluster type is: 'corosync'.<br>
> >>> Jul 22 13:39:18 mysender2.mail.ru crmd: [9033]: info:<br>
> get_cluster_type:<br>
> >>> Cluster type is: 'corosync'.<br>
> >>><br>
> >>> What`s wrong and how can I fix it?<br>
> ><br>
> > --<br>
> > Best regards,<br>
> > Proskurin Kirill<br>
> ><br>
> > _______________________________________________<br>
> > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>
> > </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
> ><br>
> > Project Home: </tt><tt><a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></tt><tt><br>
> > Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></tt><tt><br>
> > Bugs:<br>
> ><br>
> </tt><tt><a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a></tt><tt><br>
> ><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Tue, 26 Jul 2011 16:12:25 +0900<br>
> From: Yuusuke IIDA <iidayuus@intellilink.co.jp><br>
> To: "pacemaker@oss" <pacemaker@oss.clusterlabs.org><br>
> Cc: tanakakza@intellilink.co.jp<br>
> Subject: [Pacemaker] Please teach it about handling of the unmanaged<br>
> resource in environment setting placement-strategy.<br>
> Message-ID: <4E2E68D9.6010308@intellilink.co.jp><br>
> Content-Type: text/plain; charset="iso-2022-jp"<br>
><br>
> Hi, Yan<br>
> Hi, Andrew<br>
><br>
> I used the function of placement-strategy and found movement to be worried<br>
> about.<br>
><br>
> There is node "act3" which the resource that became the unmanaged state<br>
> starts.<br>
><br>
> The resource that started then in node "act1" broke down and moved.<br>
><br>
> I hoped that this inoperative resource moved to node "sby1", but it was not<br>
> carried out.<br>
><br>
> Is the movement that a resource with other capacity moves in the node that<br>
> the<br>
> resource of the unmanaged state meets capacity right as specifications?<br>
><br>
> I want you to revise it to decide placement in consideration of the<br>
> capacity of<br>
> the unmanaged resource.<br>
><br>
> I attach crm_report when a problem happened.<br>
><br>
> Best Regards,<br>
> Yuusuke<br>
> --<br>
> ----------------------------------------<br>
> METRO SYSTEMS CO., LTD<br>
><br>
> Yuusuke Iida<br>
> Mail: iidayuus@intellilink.co.jp<br>
> ----------------------------------------<br>
> -------------- next part --------------<br>
> A non-text attachment was scrubbed...<br>
> Name: pcmk-Tue-26-Jul-2011.tar.bz2<br>
> Type: application/octet-stream<br>
> Size: 164949 bytes<br>
> Desc: not available<br>
> URL: <<br>
> </tt><tt><a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110726/66852f5b/attachment.obj">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110726/66852f5b/attachment.obj</a></tt><tt><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list<br>
> Pacemaker@oss.clusterlabs.org<br>
> </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
><br>
><br>
> End of Pacemaker Digest, Vol 44, Issue 50<br>
> *****************************************<br>
><br>
><br>
> ------------------------------<br>
><br>
><br>
><br>
> *Disclaimer:* "This communication/message is for the named addressees<br>
> only. This transmission may contain information that is privileged,<br>
> confidential, proprietary or legally privileged, and /or exempt from<br>
> disclosure under applicable law. If you are not the intended recipient,<br>
> please immediately notify the sender and destroy the material in its<br>
> entirety, whether in electronic or hard copy format. You are hereby notified<br>
> that any disclosure, copying, distribution, or use of the information<br>
> contained herein (including any reliance thereon) is STRICTLY PROBHIBITED.<br>
> You must not, directly or indirectly, use, disclose, distribute, print or<br>
> copy any part of this message."<br>
><br>
> *WARNING :*"This electronic mail and any attachments are believed to be<br>
> free of any virus or other defect, the recipient must ensure that it is<br>
> virus free and no responsibility is accepted by Business Standard Limited<br>
> and /or its employees as applicable for any loss or damage arising in any<br>
> way from its use."<br>
><br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>
> </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
><br>
> Project Home: </tt><tt><a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a></tt><br>
<tt>> Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a></tt><tt><br>
> Bugs:<br>
> </tt><tt><a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a></tt><tt><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <</tt><tt><a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110727/77cdae26/attachment.html">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110727/77cdae26/attachment.html</a></tt><tt>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: graycol.gif<br>
Type: image/gif<br>
Size: 105 bytes<br>
Desc: not available<br>
URL: <</tt><tt><a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110727/77cdae26/attachment.gif">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110727/77cdae26/attachment.gif</a></tt><tt>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
Pacemaker@oss.clusterlabs.org<br>
</tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
<br>
<br>
End of Pacemaker Digest, Vol 44, Issue 54<br>
*****************************************<br>
</tt><br>
<html>
<br>
<hr style='color:#75261f'>
<img src='http://www.business-standard.com/ads/logo.jpg'><br><br><br>
<b>Disclaimer:</b> "This communication/message is for the named addressees only. This transmission may contain information that is privileged, confidential, proprietary or legally privileged, and /or exempt from disclosure under applicable law. If you are not the intended recipient, please immediately notify the sender and destroy the material in its entirety, whether in electronic or hard copy format. You are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROBHIBITED. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message."<br><br>
<b>WARNING :</b>"This electronic mail and any attachments are believed to be free of any virus or other defect, the recipient must ensure that it is virus free and no responsibility is accepted by Business Standard Limited and /or its employees as applicable for any loss or damage arising in any way from its use."
</html></body></html>