On Thu, 2007-03-22 at 11:00 +0100, Mark Hlawatschek wrote:
> Hi Lon,
>
> as this issue is not solved with patch attached in bz#222484, do you have any
> ideas what is going wrong here?
This is definitely something that should end up in bugzilla, if it isn't
already (it might be; I didn't check yet).
It looks like what's going on is that we bring up the IP, but when we do
a "ping-self" test, it's failing (even though somehow the link-check is
succeeding?). We can, I suppose, do this test after bringing up the IP
address to prevent the "start" from succeeding (e.g. attached patch
should do this).
However, I'm not sure it will help. In your logs, it says that
10.226.3.80 started successfully - however, it didn't even *mention*
10.0.46.46 in the start phase for whatever reason (but it does in the
status phase).
* Could you tell me your netmasks of your 10.x.x.x addresses on bond0
and bond1?
-- Lon
Index: ip.sh
===================================================================
RCS file: /cvs/cluster/cluster/rgmanager/src/resources/ip.sh,v
retrieving revision 1.5.2.16
diff -u -r1.5.2.16 ip.sh
--- ip.sh 13 Dec 2006 18:19:57 -0000 1.5.2.16
+++ ip.sh 22 Mar 2007 21:08:51 -0000
@@ -887,6 +887,11 @@
if [ $? -ne 0 ]; then
exit $OCF_ERR_GENERIC
fi
+ export OCF_CHECK_LEVEL=10
+ ip_op ${OCF_RESKEY_family} status ${OCF_RESKEY_address}
+ if [ $? -ne 0 ]; then
+ exit $OCF_ERR_GENERIC
+ fi
if [ $NFS_TRICKS -eq 0 ]; then
if [ "$OCF_RESKEY_nfslock" = "yes" ] || \
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
