HTTPMonitor_cURL_ProbeTimeout

While it has no bearing on the issue of why no traffic is sent with your current configuration, I did see one anomaly with getting the node to go back to UP once the monitor changed the status to FORCEDOWN. I've modified the code to force a DOWN pool member back up if it was previously forced DOWN and is now ready to be marked back up.

 

 

Here's the script body refelecting that change for your version (codeshare has been updated as well):

 

IP=`echo ${1} | sed 's/::ffff://'`
PORT=${2}
PIDFILE="/var/run/`basename ${0}`.${IP}_${PORT}.pid"
if [ -f $PIDFILE ]
then
   kill -9 `cat $PIDFILE` > /dev/null 2>&1
fi
echo "$$" > $PIDFILE
curl -fNs -m ${P_TIMEOUT} http://${IP}:${CAUCHOPORT}${URI} | grep -i "${RECV}" 2>&1 > /dev/null
if [ $? -eq 0 ]
then
    /bin/bigpipe pool myPool member 10.10.10.100:8080 show | grep "forced down" 2>&1 > /dev/null
    if [ $? -eq 0 ]
    then
        /bin/bigpipe pool ${POOL} member ${IP}:${PORT} up 2>&1 > /dev/null
    fi
    echo "UP"
else
    /bin/bigpipe pool ${POOL} member ${IP}:${PORT} down 2>&1 > /dev/null
fi
rm -f $PIDFILE
exit

 

 

/deb