Hi all, I'm using the nwstats2bb external to monitor my Novell servers. It's going purple about every 30 minutes and then back to green in 1-2 minutes. It was working fine under the old BB. Is anyone else running this external script?

Here is what I put in hobbitlaunch.cfg:

[nwstats2bb] ENVFILE /usr/local/hobbit/server/etc/nwstats2bb.ini NEEDS hobbitd CMD $BBHOME/ext/nwstats2bb_wrap.sh LOGFILE $BBSERVERLOGS/nwstats2bb.log INTERVAL 5m

The nwstats2bb_wrap.sh is this:

#!/bin/sh

bbhostgrep nwstats|while read line do set -- $line

echo $BBHOME/ext/nwstats2bb.pl $2 $1 &

$BBHOME/ext/nwstats2bb.pl $2 $1 & done exit 1

The hobbitlaunch.log file shows this: 2005-02-28 08:00:25 Task nwstats2bb terminated, status 1 2005-02-28 08:05:26 Task nwstats2bb started with PID 31694 2005-02-28 08:05:27 Task nwstats2bb terminated, status 1 2005-02-28 08:15:30 Task nwstats2bb started with PID 31906 2005-02-28 08:15:31 Task nwstats2bb terminated, status 1 2005-02-28 08:20:31 Task nwstats2bb started with PID 32167 2005-02-28 08:20:31 Task nwstats2bb terminated, status 1 2005-02-28 08:25:35 Task nwstats2bb started with PID 32396 2005-02-28 08:25:36 Task nwstats2bb terminated, status 1 2005-02-28 08:30:36 Task nwstats2bb started with PID 32600 2005-02-28 08:30:37 Task nwstats2bb terminated, status 1 2005-02-28 08:35:36 Task nwstats2bb started with PID 341 2005-02-28 08:35:36 Task nwstats2bb terminated, status 1 2005-02-28 08:40:36 Task nwstats2bb started with PID 550 2005-02-28 08:40:36 Task nwstats2bb terminated, status 1 2005-02-28 08:50:40 Task nwstats2bb started with PID 796 2005-02-28 08:50:41 Task nwstats2bb terminated, status 1 2005-02-28 08:55:40 Task nwstats2bb started with PID 1066 2005-02-28 08:55:40 Task nwstats2bb terminated, status 1

Thanks

David Stuffle

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.