[Linux-cluster] Problem with ping as an heuristic with qdiskd

[emmanuel segura]

I know the cluster agent /usr/share/cluster/ip.sh cannot check the gateway

I resolved this problem with one script in my service group, so when the
script fail the resource switch

========================================================
 <script file="/usr/share/cluster/neighbour_RMAN.bash"
name="neigh_gtw_rman"/>
========================================================
script
========================================================
#!/bin/bash



NEIGHBOUR=xx.xxx.xxx.x

LC_ALL=C
LANG=C
PATH=/bin:/sbin:/usr/bin:/usr/sbin
export LC_ALL LANG PATH

. $(dirname $0)/ocf-shellfuncs


case $1 in
start)
        exit $OCF_SUCCESS
        ;;
stop)
        exit $OCF_SUCCESS
        ;;
status|monitor)
        /bin/ping -c 5 -w 6 -t 4 $NEIGHBOUR
        if [ $? -ne 0 ];
        then
                ocf_log warn "Damn, failed to ping $NEIGHBOUR"
                exit $OCF_ERR_GENERIC
        fi

        ocf_log debug "Ping to $NEIGHBOUR succeeded :]"
        exit $OCF_SUCCESS
        ;;
restart)
        exit $OCF_SUCCESS
        ;;
*)
        echo "usage: $0 [start|stop|status|restart|meta-data]"
        exit $OCF_ERR_ARGS
        ;;
esac
=====================================================

Il giorno 12 marzo 2012 12:26, Gianluca Cecchi
<gianluca.cecchi at gmail.com>ha scritto:

> On Fri, 9 Mar 2012 17:29:06 +0100 emmanuel segura wrote:
> > i'll try to be more clear
> > i work on redhat cluster from 2 years and i seen this topic so much times
>
> Sorry, I didn't want to offend anyone.
> I have been working on rhcs (and other companions from other OSes) for
> many years too...
>
> > I think it's normal my services switch if have the public network  down
> on the node where
> > the resource group was running,But But But with ping as heuristic you
> get a node fence
>
> AFAIK rhcs is not able to switch service if the server looses its
> connectivity.
> Better: the /usr/share/cluster/ip.sh resource definition contains the
> parameter monitor_link, but it is only for dead link on the nic..
> And I have to manage rhcs...
>
> So in my opinion if you want to test gateway reachability (that means
> production lan where you deliver a cluster service) you are at the
> moment forced to use heuristic or write your own resource to add to
> the ones composing the service and so causing a service switch in case
> of problems with this custom resource...
> but I could be wrong in my assumption...
>
> Cheers,
>
> Gianluca
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>



-- 
esta es mi vida e me la vivo hasta que dios quiera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20120312/b43ac420/attachment.htm>