On Thu, Sep 18, 2008 at 22:47, Tavanyar, Simon
<[EMAIL PROTECTED]> wrote:
> I'm running 2.1.0 in a two-node cluster. I get this warning for no
> apparent reason (false positive I suspect).

Unlikely but possible.  Although 2.1.0 is getting pretty old now...
I'd highly suggest an upgrade.

Did you change the target role?  What does your config look like?

> It is not reproducible, but
> intermittent.  Once it occurs, restarting the resource does not clear
> it, it shows up the next time pengine runs.
>
>
>
> Example:
>
> Sep 16 07:12:40 8213 node0 pengine: [16454]: WARN:
> check_action_definition: Parameters to ClusterAddr_monitor_0 on node1
> changed: recorded d53473e6dd1a4c3f15188816a27b27fb vs. calculated (all)
> 6c746e406275f3c825da73a7f3fa8cd4
>
> Sep 16 07:12:43 8280 node0 pengine: [16454]: WARN:
> check_action_definition: Parameters to ClusterAddr_monitor_0 on node1
> changed: recorded d53473e6dd1a4c3f15188816a27b27fb vs. calculated (all)
> ab90eac14c61bb1cbef0fffdd551d936
>
> Sep 16 07:13:39 8622 node0 pengine: [16454]: WARN:
> check_action_definition: Parameters to ClusterAddr_monitor_0 on node1
> changed: recorded ab90eac14c61bb1cbef0fffdd551d936 vs. calculated (all)
> 5a22abe799939bed62f15a6b06fe5da8
>
> Sep 16 07:19:10 8989 node0 pengine: [16454]: WARN:
> check_action_definition: Parameters to ClusterAddr_monitor_0 on node0
> changed: recorded ab90eac14c61bb1cbef0fffdd551d936 vs. calculated (all)
> 5a22abe799939bed62f15a6b06fe5da8
>
>
>
>
>
> Has there been a fix since 2.1.0 related to this warning? I find hints
> of it in the mailer, but the links are expired. I could not find
> anything related in Bugzilla.
>
>
>
> Where should I start looking for a probable cause?

Logs with "debug 1" set in ha.cf.  I think we log the input that the
digest was created from.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to