Il 25/06/2012 10:00, kook ha scritto:
Dear Fiorenza:
I have the same problem with you. I checked the newest ethmonitor ra
(ClusterLabs-resource-agents-v3.9.2-0-ge261943.tar). It's same with my sles 11
sp2.
Failed actions:
p_ethmonitor:1_monitor_15000 (node=sles11264-node1, call=15
I resolved the problem. I found this is a bug in ethmonitor agent.
in ethmonitor :
255 # get the link status on $NIC
256 # asks ip about running (up) interfaces, returns the number of matching
interface names that are up
257 get_link_status () {
258$IP2UTIL -o link show up dev "$NIC" | gr
For test. I don't know how to reply this subject.
On Mon, Jun 25, 2012 at 4:00 PM, kook wrote:
> Dear Fiorenza:
>
> I have the same problem with you. I checked the newest ethmonitor ra
> (ClusterLabs-resource-agents-v3.9.2-0-ge261943.tar). It's same with my sles
> 11 sp2.
>
> Failed actio
Dear Fiorenza:
I have the same problem with you. I checked the newest ethmonitor
ra (ClusterLabs-resource-agents-v3.9.2-0-ge261943.tar). It's same with
my sles 11 sp2.
Failed actions:
p_ethmonitor:1_monitor_15000 (node=sles11264-node1, call=1591,
rc=-2, status=Timed Out): unknown exec e
Il 21/03/2012 09:06, Florian Haas ha scritto:
On Tue, Mar 20, 2012 at 4:18 PM, Fiorenza Meini wrote:
Hi there,
has anybody configured successfully the RA specified in the object of the
message?
I got this error: if_eth0_monitor_0 (node=fw1, call=2297, rc=-2,
status=Timed Out): unknown exec err
On Tue, Mar 20, 2012 at 4:18 PM, Fiorenza Meini wrote:
> Hi there,
> has anybody configured successfully the RA specified in the object of the
> message?
>
> I got this error: if_eth0_monitor_0 (node=fw1, call=2297, rc=-2,
> status=Timed Out): unknown exec error
Your ethmonitor RA missed its 50-s
Hi there,
has anybody configured successfully the RA specified in the object of
the message?
I got this error: if_eth0_monitor_0 (node=fw1, call=2297, rc=-2,
status=Timed Out): unknown exec error
The RA definition in CIB is:
primitive if_eth0 ocf:heartbeat:ethmonitor \
params interf
