<br><br><div class="gmail_quote">On Tue, Jul 26, 2011 at 5:35 PM, Gururaj B Patil <span dir="ltr"><<a href="mailto:gururaj.patil@bsmail.in">gururaj.patil@bsmail.in</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<p>Dear Mr.<tt>Andrew Beekhof</tt><br>
<br>
Yes I did try googeling but could not get proper information. In few forums I noticed message as below.<br>
<br>
"<font color="#222222" face="Georgia">That's development logging, which was accidentally bumped to a higher<br>
log level." </font></p></div></blockquote><div><br></div><div>What was unclear about this?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>
<p><br>
<br>
<font color="#222222" face="Georgia">We are searching again but meanwhile can pacemaker team help on this.</font><br>
<br>
<font color="#222222" face="Georgia">Regards,</font><br>
<font color="#222222" face="Georgia">Gururaj Patil</font><br>
<br>
<img width="16" height="16" src="cid:1__=EABBF24ADFBB3CA18f9e8a93df9386@bsmail.in" border="0" alt="Inactive hide details for pacemaker-request---07/26/2011 12:47:15 PM---Send Pacemaker mailing list submissions to pacemaker@os"><font color="#424282">pacemaker-request---07/26/2011 12:47:15 PM---Send Pacemaker mailing list submissions to <a href="mailto:pacemaker@oss.clusterlabs.org" target="_blank">pacemaker@oss.clusterlabs.org</a></font><br>
<br>
<font size="2" color="#5F5F5F">From: </font><font size="2"><a href="mailto:pacemaker-request@oss.clusterlabs.org" target="_blank">pacemaker-request@oss.clusterlabs.org</a></font><br>
<font size="2" color="#5F5F5F">To: </font><font size="2"><a href="mailto:pacemaker@oss.clusterlabs.org" target="_blank">pacemaker@oss.clusterlabs.org</a></font><br>
<font size="2" color="#5F5F5F">Date: </font><font size="2">07/26/2011 12:47 PM</font><br>
<font size="2" color="#5F5F5F">Subject: </font><font size="2">Pacemaker Digest, Vol 44, Issue 50</font><br>
</p><hr width="100%" size="2" align="left" noshade style="color:#8091A5"><br>
<br>
<br>
<tt>Send Pacemaker mailing list submissions to<br>
<a href="mailto:pacemaker@oss.clusterlabs.org" target="_blank">pacemaker@oss.clusterlabs.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:pacemaker-request@oss.clusterlabs.org" target="_blank">pacemaker-request@oss.clusterlabs.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:pacemaker-owner@oss.clusterlabs.org" target="_blank">pacemaker-owner@oss.clusterlabs.org</a><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 <<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>><br>
To: The Pacemaker cluster resource manager<br>
<<a href="mailto:pacemaker@oss.clusterlabs.org" target="_blank">pacemaker@oss.clusterlabs.org</a>><br>
Cc: M A Faruqui <<a href="mailto:m.faruqui@bsmail.in" target="_blank">m.faruqui@bsmail.in</a>>, Prafulla H Patil<br>
<<a href="mailto:prafulla.patil@bsmail.in" target="_blank">prafulla.patil@bsmail.in</a>>, Bandana Roy <<a href="mailto:bandana.roy@bsmail.in" target="_blank">bandana.roy@bsmail.in</a>><br>
Subject: Re: [Pacemaker] Business Standard India - Errors noticed in<br>
pacemaker<br>
Message-ID:<br>
<<a href="mailto:CAEDLWG0ExctnrJq8KduV8JdC3hZTVSovB7gDnYv4MVpPox_cBw@mail.gmail.com" target="_blank">CAEDLWG0ExctnrJq8KduV8JdC3hZTVSovB7gDnYv4MVpPox_cBw@mail.gmail.com</a>><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 <<a href="mailto:gururaj.patil@bsmail.in" target="_blank">gururaj.patil@bsmail.in</a>>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>
> 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>
> 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.<a href="tel:%2B91-22-24971924" value="+912224971924" target="_blank">+91-22-24971924</a><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: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
> </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
><br>
> Project Home: </tt><tt><a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a></tt><tt><br>
> Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">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" target="_blank">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/20110726/4d99749e/attachment-0001.html" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110726/4d99749e/attachment-0001.html</a></tt><tt>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 26 Jul 2011 17:00:56 +1000<br>
From: Andrew Beekhof <<a href="mailto:andrew@beekhof.net" target="_blank">andrew@beekhof.net</a>><br>
To: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
Subject: Re: [Pacemaker] Cluster type is: corosync<br>
Message-ID:<br>
<CAEDLWG1s=<a href="mailto:AHrdXdWdO0r04410j0%2BYgj7VfAz_Yf_0fMDpiNorA@mail.gmail.com" target="_blank">AHrdXdWdO0r04410j0+Ygj7VfAz_Yf_0fMDpiNorA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Mon, Jul 25, 2011 at 7:18 PM, Proskurin Kirill<br>
<<a href="mailto:k.proskurin@corp.mail.ru" target="_blank">k.proskurin@corp.mail.ru</a>> wrote:<br>
> <a href="tel:25.07.2011%2010" value="+12507201110" target="_blank">25.07.2011 10</a>: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>
>> <<a href="mailto:k.proskurin@corp.mail.ru" target="_blank">k.proskurin@corp.mail.ru</a>> ?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 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 <a href="http://mysender39.mail.ru" target="_blank">mysender39.mail.ru</a> stonith-ng: [3499]: info:<br>
>>> get_cluster_type: Cluster type is: 'openais'.<br>
>>> Jul 22 20:38:58 <a href="http://mysender39.mail.ru" target="_blank">mysender39.mail.ru</a> attrd: [3502]: info: get_cluster_type:<br>
>>> Cluster type is: 'openais'.<br>
>>> Jul 22 20:38:58 <a href="http://mysender39.mail.ru" target="_blank">mysender39.mail.ru</a> cib: [3500]: info: get_cluster_type:<br>
>>> Cluster type is: 'openais'.<br>
>>> Jul 22 20:38:59 <a href="http://mysender39.mail.ru" target="_blank">mysender39.mail.ru</a> crmd: [3504]: info: 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 <a href="http://mysender2.mail.ru" target="_blank">mysender2.mail.ru</a> stonith-ng: [9028]: info:<br>
>>> get_cluster_type: Cluster type is: 'corosync'.<br>
>>> Jul 22 13:39:17 <a href="http://mysender2.mail.ru" target="_blank">mysender2.mail.ru</a> attrd: [9031]: info: get_cluster_type:<br>
>>> Cluster type is: 'corosync'.<br>
>>> Jul 22 13:39:17 <a href="http://mysender2.mail.ru" target="_blank">mysender2.mail.ru</a> cib: [9029]: info: get_cluster_type:<br>
>>> Cluster type is: 'corosync'.<br>
>>> Jul 22 13:39:18 <a href="http://mysender2.mail.ru" target="_blank">mysender2.mail.ru</a> crmd: [9033]: info: 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: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
> </tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
><br>
> Project Home: </tt><tt><a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a></tt><tt><br>
> Getting started: </tt><tt><a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">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" target="_blank">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 <<a href="mailto:iidayuus@intellilink.co.jp" target="_blank">iidayuus@intellilink.co.jp</a>><br>
To: "pacemaker@oss" <<a href="mailto:pacemaker@oss.clusterlabs.org" target="_blank">pacemaker@oss.clusterlabs.org</a>><br>
Cc: <a href="mailto:tanakakza@intellilink.co.jp" target="_blank">tanakakza@intellilink.co.jp</a><br>
Subject: [Pacemaker] Please teach it about handling of the unmanaged<br>
resource in environment setting placement-strategy.<br>
Message-ID: <<a href="mailto:4E2E68D9.6010308@intellilink.co.jp" target="_blank">4E2E68D9.6010308@intellilink.co.jp</a>><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 about.<br>
<br>
There is node "act3" which the resource that became the unmanaged state 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 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 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: <a href="mailto:iidayuus@intellilink.co.jp" target="_blank">iidayuus@intellilink.co.jp</a><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: <</tt><tt><a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110726/66852f5b/attachment.obj" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110726/66852f5b/attachment.obj</a></tt><tt>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
</tt><tt><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></tt><tt><br>
<br>
<br>
End of Pacemaker Digest, Vol 44, Issue 50<br>
*****************************************<br>
</tt><br>
<br>
<hr style="color:#75261f">
<img><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."
<p></p></div>
<br>_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker" target="_blank">http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker</a><br>
<br></blockquote></div><br>