[Pacemaker] Repeating Log entries of ping resource
Andreas Kurz
andreas at hastexo.com
Thu Nov 10 20:44:19 UTC 2011
On 11/10/2011 04:28 PM, Senftleben, Stefan (itsc) wrote:
> Thx, i tried to tune the parameter, but the errors still arrived.
> After restarting the corosysnc-daemon on each node the errors disappeared.
Restarting corosync for changes to take effect? Should really not be
necessary.
>
> The brings me to next question:
> --> How do I activate new configurations, that I have made wir crm-cmd to a resource?
you mean after changing resources in "crm configure"? Well, you
typically run a ptest, check if the result is ok and then you do a
"commit" to write changes to the cib ... but whenever you try to exit
the crm shell with pending changes you should get a warning message ...
Regards,
Andreas
--
Need help with Pacemaker?
http://www.hastexo.com/now
>
> Regards,
> Stefan
>
>
> -----Ursprüngliche Nachricht-----
> Von: Andreas Kurz [mailto:andreas at hastexo.com]
> Gesendet: Donnerstag, 10. November 2011 13:41
> An: pacemaker at oss.clusterlabs.org
> Betreff: Re: [Pacemaker] Repeating Log entries of ping resource
>
> On 11/10/2011 01:26 PM, Senftleben, Stefan (itsc) wrote:
>> Okay, need I have to tune something to get rid oft he log entries?
>
> increase the interval or tune the timeout/retry settings for your ping
> resources ... I guess the defaults in your ping RA version don't fit
> when using such a short interval if one ping-node is not available and
> thus timeouts several times.
>
> Regards,
> Andreas
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 286 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111110/5d4e85f8/attachment-0004.sig>
More information about the Pacemaker
mailing list