Re: [hobbit] msgcache hobbitfetch problems

[Steinar M. Skúlason <steinarms (at) gmail.com>]

On Mon, Feb 8, 2010 at 5:36 PM, Daniel McDonald <
dan.mcdonald (at) austinenergy.com> wrote:

> On 2/8/10 10:37 AM, "Steinar M. Skúlason" <steinarms (at) gmail.com> wrote:
>
> > Hi,
> >
> > I'm having problems with "msgcache" on the client machines and
> "hobbitfetch"
> > on the server machine.
> > It works for a short period and then get's stuck and all my client side
> checks
> > end up with status purple.
>
> Yup.  Been doing that for a long time here.  I sent a bunch of corefiles to
> Henrik about it, and he tried a bunch of patches.  Eventually, we just
> wrote
> a routine that restarts hobbitfetch whenever a host turns purple.
>
> --
> Daniel J McDonald, CCIE # 2495, CISSP # 78281
>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe (at) hswn.dk
>
>
>
Ok, good to hear that I am not the only one.
I wrote a ugly routine that restarts hobbitfetch if there is no new entry in
the logfile


#!/bin/bash

#This is to see if any progress has been made within the hobbitfetch
utility.
TMP_FILE=/tmp/tmp.hobbitfetch.last
LAST_LINE=`tail -1 /usr/lib/xymon/server/log/hobbitfetch.log|awk '{print $1
$2}'`
PREV_LINE=`cat /tmp/tmp.hobbitfetch.last`
echo $LAST_LINE > $TMP_FILE

if [ "$LAST_LINE" == "$PREV_LINE" ]; then
  echo "Nothing has happend .... killing hobbitfetch!"
  PID=`ps -ef|grep hobbitfetch|awk '{print $2}'`
  kill -9 $PID
fi

Best Regards,
Steinar M.