[Pacemaker] Repeating Log entries of ping resource

[Senftleben, Stefan (itsc)]

Thx, i tried to tune the parameter, but the errors still arrived.
After restarting the corosysnc-daemon on each node the errors disappeared.

The brings me to next question:
--> How do I activate new configurations, that I have made wir crm-cmd to a resource? 

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

-- 
Need help with Pacemaker?
http://www.hastexo.com/now

> 
> thx and regards
> Stefan
> 
> -----Ursprüngliche Nachricht-----
> Von: Andreas Kurz [mailto:andreas at hastexo.com] 
> Gesendet: Donnerstag, 10. November 2011 12:53
> An: pacemaker at oss.clusterlabs.org
> Betreff: Re: [Pacemaker] Repeating Log entries of ping resource
> 
> hello,
> 
> On 11/10/2011 11:35 AM, Senftleben, Stefan (itsc) wrote:
>> Hello again,
>>
>> on a two node active passive cluster runs a clone of ping resources.
>>
>> In the corosync.log following entries reappear in short time phrases. Is this an error?
> 
> as the logs explain, it's an info ;-)
> 
>>
>> Regards,
>>
>> Stefan.
>>
>>
>> log entries:
>>
>> Nov 10 11:29:38 lxds07 lrmd: [5478]: info: perform_op:2883: postponing all ops on resource pri_ping:1 by 1000 ms
>> Nov 10 11:29:38 lxds07 lrmd: [5478]: info: perform_op:2873: operation monitor[30] on ocf::ping::pri_ping:1 for client 5481, its parameters: CRM_meta_clone=[1] host_list=[192.168.12.1 192.168.12.2 192.168.12.13] CRM_meta_clone_max=[2] dampen=[20s] CRM_meta_globally_unique=[false] crm_feature_set=[3.0.1] multiplier=[1000] CRM_meta_name=[monitor] CRM_meta_start_delay=[0] CRM_meta_timeout=[60000] CRM_meta_interval=[5000]  for rsc is already running.
>>
>>
>> config of resource:
> 
> nice, but not the resource responsible for above messages ... the
> messages say that the monitor needs longer than the interval specified
> to run so the next monitor for the clone 1 of resource pri_ping has to wait.
> 
> Regards,
> Andreas
>