Custom script shows purple

30 messages in this thread

list David Morgan · Tue, 27 Apr 2010 15:55:36 -0400 ·

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

   COLUMN=ldap-con      # Does the server have an LDAP conection
   COLOR=green          # By default, everything is OK
   MSG="LDAP Connectivity Check"

   TESTVAL=`/usr/bin/getent group admins | wc -l`

   # Do whatever you need to test for something
   # As an example, go red if /tmp/badstuff exists.
   if [ $TESTVAL -eq 0 ]
   then
      COLOR=red
      MSG="${MSG}

      LDAP Configureation and Connectivity is BORKED UP
      "
   else
      MSG="${MSG}

      LDAP Configureation and Connectivity is OK
      "
   fi

   # Tell Hobbit about it
   $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

   ${MSG}
   "

   exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/ext/getent.sh
        LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
        INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list Scott Ryan · Tue, 27 Apr 2010 21:41:45 +0100 ·

Is the script being executed? Assuming it is, have you configured the
server to only expect the check to be run every 4 hours? If not it
will go purple after 30 minutes every time as that is the default
check timeout.

If the script is not running at all, what do the xymon logs say? If it
has an issue running the script you should see it in the logs. You
could check that the xymon user has the rights to execute the script.

Thanks

▸ quoted from David Morgan


On Tue, Apr 27, 2010 at 8:55 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

--


Scott Ryan
http://bonoboslr.wordpress.com/

list David Morgan · Tue, 27 Apr 2010 16:57:48 -0400 ·

Yes, the script is being executed.  I think it is the server not
knowing that it only runs every four hours.  How can I set the default
for this check to be 4 hours (and leave the rest at 30 mins)?  Or can
you do that?

Dave

▸ quoted from Scott Ryan


On Tue, Apr 27, 2010 at 4:41 PM, Scott Ryan <user-9fb0c480aa2f@xymon.invalid> wrote:

Is the script being executed? Assuming it is, have you configured the
server to only expect the check to be run every 4 hours? If not it
will go purple after 30 minutes every time as that is the default
check timeout.

If the script is not running at all, what do the xymon logs say? If it
has an issue running the script you should see it in the logs. You
could check that the xymon user has the rights to execute the script.

Thanks

On Tue, Apr 27, 2010 at 8:55 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

--
Scott Ryan
http://bonoboslr.wordpress.com/

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list Scott Ryan · Tue, 27 Apr 2010 22:13:24 +0100 ·

The wiki -

http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/FAQ#My_test_only_runs_every_hour._How_do_I_get_it_to_not_go_purple_after_30_minutes_.3F

Then the man page - you need to run

# bb status lifetime

▸ quoted from David Morgan


On Tue, Apr 27, 2010 at 9:57 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

Yes, the script is being executed.  I think it is the server not
knowing that it only runs every four hours.  How can I set the default
for this check to be 4 hours (and leave the rest at 30 mins)?  Or can
you do that?

Dave

On Tue, Apr 27, 2010 at 4:41 PM, Scott Ryan <user-9fb0c480aa2f@xymon.invalid> wrote:

Is the script being executed? Assuming it is, have you configured the
server to only expect the check to be run every 4 hours? If not it
will go purple after 30 minutes every time as that is the default
check timeout.

If the script is not running at all, what do the xymon logs say? If it
has an issue running the script you should see it in the logs. You
could check that the xymon user has the rights to execute the script.

Thanks

On Tue, Apr 27, 2010 at 8:55 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

--
Scott Ryan
http://bonoboslr.wordpress.com/

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

-- 
Scott Ryan
http://bonoboslr.wordpress.com/

list Galen Johnson · Tue, 27 Apr 2010 17:15:15 -0400 ·

IIRC, you have to change your BB command to:
$BB $BBDISP "status+4h $MACHINE.$COLUMN $COLOR `date`

Verify this in the man page for BB.

=G=

▸ quoted from David Morgan

-----Original Message-----
From: David Morgan [mailto:user-4691629dd582@xymon.invalid] 
Sent: Tuesday, April 27, 2010 4:58 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Custom script shows purple

Yes, the script is being executed.  I think it is the server not
knowing that it only runs every four hours.  How can I set the default
for this check to be 4 hours (and leave the rest at 30 mins)?  Or can
you do that?

Dave

On Tue, Apr 27, 2010 at 4:41 PM, Scott Ryan <user-9fb0c480aa2f@xymon.invalid> wrote:

Is the script being executed? Assuming it is, have you configured the
server to only expect the check to be run every 4 hours? If not it
will go purple after 30 minutes every time as that is the default
check timeout.

If the script is not running at all, what do the xymon logs say? If it
has an issue running the script you should see it in the logs. You
could check that the xymon user has the rights to execute the script.

Thanks

On Tue, Apr 27, 2010 at 8:55 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

--
Scott Ryan
http://bonoboslr.wordpress.com/

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list TJ Yang · Tue, 27 Apr 2010 16:42:55 -0500 ·

On Tue, Apr 27, 2010 at 4:13 PM, Scott Ryan <user-9fb0c480aa2f@xymon.invalid> wrote:

The wiki -

http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/FAQ#My_test_only_runs_every_hour._How_do_I_get_it_to_not_go_purple_after_30_minutes_.3F

I updated this URL with more detail information.

▸ quoted from Galen Johnson

Then the man page - you need to run

# bb status lifetime

On Tue, Apr 27, 2010 at 9:57 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

Yes, the script is being executed.  I think it is the server not
knowing that it only runs every four hours.  How can I set the default
for this check to be 4 hours (and leave the rest at 30 mins)?  Or can
you do that?

Dave

On Tue, Apr 27, 2010 at 4:41 PM, Scott Ryan <user-9fb0c480aa2f@xymon.invalid> wrote:

Is the script being executed? Assuming it is, have you configured the
server to only expect the check to be run every 4 hours? If not it
will go purple after 30 minutes every time as that is the default
check timeout.

If the script is not running at all, what do the xymon logs say? If it
has an issue running the script you should see it in the logs. You
could check that the xymon user has the rights to execute the script.

Thanks

On Tue, Apr 27, 2010 at 8:55 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

--
Scott Ryan
http://bonoboslr.wordpress.com/

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

--
Scott Ryan
http://bonoboslr.wordpress.com/

--


T.J. Yang

list Richard Finegold · Tue, 27 Apr 2010 15:57:17 -0700 ·

LIFETIME=4h is inadequate for something that tries to runs every 4h:
It will go purple if cron isn't exact or if a test varies in timing or
fails or if communication is (temporarily) lost.

NB the default of 5 minute execution intervals and 30 minute LIFETIME
forgives 5 misses. Philosophically, LIFETIME should be tied to how
many misses are acceptable: I(M+1), where I = interval and M =
acceptable misses. If it isn't tied to acceptable misses then purple
becomes less meaningful for notifications (false positives might
occur).

If communication and cron were perfectly reliable then Xymon
presumably wouldn't be used. :)

▸ quoted from David Morgan


On Tue, Apr 27, 2010 at 13:57, David Morgan <user-4691629dd582@xymon.invalid> wrote:

Yes, the script is being executed.  I think it is the server not
knowing that it only runs every four hours.  How can I set the default
for this check to be 4 hours (and leave the rest at 30 mins)?  Or can
you do that?

list Jerald Sheets · Tue, 27 Apr 2010 21:24:26 -0400 ·

Hobbit has a built in LDAP test if I remember correctly.  Was it not serving your needs?

--jms

▸ quoted from David Morgan



On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list David Morgan · Tue, 27 Apr 2010 22:00:18 -0400 ·

Not really, this is in addition to that test.

Dave

▸ quoted from Jerald Sheets


Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list David Morgan · Wed, 28 Apr 2010 07:15:26 -0400 ·

Ok so owing that I need to put in some "cushion"

I should probobly use

$BB $BBDISP "status+8h $MACHINE.ldap-con green `date`"

Where ldap-con is the test name, and green is the status I want it to 
remain to....I THINK.

Which file (assuming that this is done on the client) should I put this 
into?  I would like this setting to remain persistant.

Dave

▸ quoted from Galen Johnson


Galen Johnson wrote:

IIRC, you have to change your BB command to:
$BB $BBDISP "status+4h $MACHINE.$COLUMN $COLOR `date`

Verify this in the man page for BB.

=G=

-----Original Message-----
From: David Morgan [mailto:user-4691629dd582@xymon.invalid] 
Sent: Tuesday, April 27, 2010 4:58 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Custom script shows purple

Yes, the script is being executed.  I think it is the server not
knowing that it only runs every four hours.  How can I set the default
for this check to be 4 hours (and leave the rest at 30 mins)?  Or can
you do that?

Dave

On Tue, Apr 27, 2010 at 4:41 PM, Scott Ryan <user-9fb0c480aa2f@xymon.invalid> wrote:

Is the script being executed? Assuming it is, have you configured the
server to only expect the check to be run every 4 hours? If not it
will go purple after 30 minutes every time as that is the default
check timeout.

If the script is not running at all, what do the xymon logs say? If it
has an issue running the script you should see it in the logs. You
could check that the xymon user has the rights to execute the script.

Thanks

On Tue, Apr 27, 2010 at 8:55 PM, David Morgan <user-4691629dd582@xymon.invalid> wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

--
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

--
Scott Ryan
http://bonoboslr.wordpress.com/

list Peter Brandt · Wed, 28 Apr 2010 07:19:11 -0400 ·

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards;
 [peter at peterlinux Downloads]$ rpm -i hobbit-4.2.0-1.s390.rpm
error: Failed dependencies:
	liblber.so.199 is needed by hobbit-4.2.0-1.s390
	libldap.so.199 is needed by hobbit-4.2.0-1.s390
	librrd.so.0 is needed by hobbit-4.2.0-1.s390 [peter at peterlinux
Downloads]$ 


Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX

list Iain M Conochie · Wed, 28 Apr 2010 12:23:13 +0100 ·

<snip>

   # Tell Hobbit about it
   $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

You really need to put in status+5h instead of status for a 4 hour 
script. This tells the hobbit server not to expire the message for 5 hours.

regards
Iain

▸ quoted from David Morgan

   ${MSG}
   "

   exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/ext/getent.sh
        LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
        INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

list David Morgan · Wed, 28 Apr 2010 07:39:29 -0400 ·

*face palm*  Duh!  It's in our custom script.  I am a doofus....

▸ quoted from Iain M Conochie


Iain M Conochie wrote:

<snip>

   # Tell Hobbit about it
   $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

You really need to put in status+5h instead of status for a 4 hour 
script. This tells the hobbit server not to expire the message for 5 
hours.

regards
Iain

   ${MSG}
   "

   exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/ext/getent.sh
        LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
        INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

list David Morgan · Wed, 28 Apr 2010 07:49:38 -0400 ·


We wanted to test the connectivity from the LDAP clients (running a 
xymon agent) to the LDAP server and report their connectivity status.

It appears (at least from what I read) that the LDAP module is a test 
from the Hobbit/XYmon Server to the LDAP server.

▸ quoted from David Morgan


Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

  COLUMN=ldap-con      # Does the server have an LDAP conection
  COLOR=green          # By default, everything is OK
  MSG="LDAP Connectivity Check"

  TESTVAL=`/usr/bin/getent group admins | wc -l`

  # Do whatever you need to test for something
  # As an example, go red if /tmp/badstuff exists.
  if [ $TESTVAL -eq 0 ]
  then
     COLOR=red
     MSG="${MSG}

     LDAP Configureation and Connectivity is BORKED UP
     "
  else
     MSG="${MSG}

     LDAP Configureation and Connectivity is OK
     "
  fi

  # Tell Hobbit about it
  $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

  ${MSG}
  "

  exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
       ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
       CMD $HOBBITCLIENTHOME/ext/getent.sh
       LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
       INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list Jerald Sheets · Wed, 28 Apr 2010 07:53:38 -0400 ·

Yeah, that's it's usage.

So, I guess from time to time the clients have issues hitting the server?  
Never thought to test in that direction.  

--j

▸ quoted from David Morgan



On Apr 28, 2010, at 7:49 AM, David Morgan wrote:

We wanted to test the connectivity from the LDAP clients (running a xymon agent) to the LDAP server and report their connectivity status.

It appears (at least from what I read) that the LDAP module is a test from the Hobbit/XYmon Server to the LDAP server.

Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

 # Tell Hobbit about it
 $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

 ${MSG}
 "

 exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
      ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
      CMD $HOBBITCLIENTHOME/ext/getent.sh
      LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
      INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list David Morgan · Wed, 28 Apr 2010 08:06:24 -0400 ·

See all the fun stuff one can do with Xymon?

▸ quoted from Jerald Sheets


Jerald Sheets wrote:

Yeah, that's it's usage.

So, I guess from time to time the clients have issues hitting the server?  

Never thought to test in that direction.  


--j


On Apr 28, 2010, at 7:49 AM, David Morgan wrote:

We wanted to test the connectivity from the LDAP clients (running a xymon agent) to the LDAP server and report their connectivity status.

It appears (at least from what I read) that the LDAP module is a test from the Hobbit/XYmon Server to the LDAP server.

Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

 # Tell Hobbit about it
 $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

 ${MSG}
 "

 exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
      ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
      CMD $HOBBITCLIENTHOME/ext/getent.sh
      LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
      INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list Jerald Sheets · Wed, 28 Apr 2010 08:10:39 -0400 ·

Well, you could argue that if network connectivity is preventing auth, you're going to have a lot bigger problems that figuring out if one host can't see "gloryland" from the back warehouse at the shipping dock.  The CEO won't be logging in, and will be sitting on your desk.

The only time I think it'd be helpful in our situation would be if I had multiple network segments authenticating into a central zone that is part of a VLAN with everything else, thus just asking for potential auth problems.  
You start authenticating across network boundaries or VLANs, you're just asking for trouble.

▸ quoted from David Morgan



--j

On Apr 28, 2010, at 8:06 AM, David Morgan wrote:

See all the fun stuff one can do with Xymon?

Jerald Sheets wrote:

Yeah, that's it's usage.

So, I guess from time to time the clients have issues hitting the server?  Never thought to test in that direction.  
--j


On Apr 28, 2010, at 7:49 AM, David Morgan wrote:

We wanted to test the connectivity from the LDAP clients (running a xymon agent) to the LDAP server and report their connectivity status.

It appears (at least from what I read) that the LDAP module is a test from the Hobbit/XYmon Server to the LDAP server.

Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

COLUMN=ldap-con      # Does the server have an LDAP conection
COLOR=green          # By default, everything is OK
MSG="LDAP Connectivity Check"

TESTVAL=`/usr/bin/getent group admins | wc -l`

# Do whatever you need to test for something
# As an example, go red if /tmp/badstuff exists.
if [ $TESTVAL -eq 0 ]
then
   COLOR=red
   MSG="${MSG}

   LDAP Configureation and Connectivity is BORKED UP
   "
else
   MSG="${MSG}

   LDAP Configureation and Connectivity is OK
   "
fi

# Tell Hobbit about it
$BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

${MSG}
"

exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
     ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
     CMD $HOBBITCLIENTHOME/ext/getent.sh
     LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
     INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

list Xymon User in Richmond · Wed, 28 Apr 2010 08:21:01 -0400 ·

[Insert top-posting rant boilerplate here]

Makes utter sense.  In the real world, client ability to use the LDAP is
what matters from a service standpoint, and a failure of it will present
as failure of other services unless the underlying dependency is known and
tested, and hopefully DEPENDS-ed in Xymon.  I've seen many such failures
from robots or new systems administrators applying inappropriate policies
like password expiration to service accounts, so I think client-side
checks are appropriate.

▸ quoted from Jerald Sheets


On Wed, April 28, 2010 07:53, Jerald Sheets wrote:

Yeah, that's it's usage.

So, I guess from time to time the clients have issues hitting the server?

Never thought to test in that direction.


--j


On Apr 28, 2010, at 7:49 AM, David Morgan wrote:

We wanted to test the connectivity from the LDAP clients (running a
xymon agent) to the LDAP server and report their connectivity status.

It appears (at least from what I read) that the LDAP module is a test
from the Hobbit/XYmon Server to the LDAP server.

Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not
serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

#%2

list dOCtoR MADneSs · Wed, 28 Apr 2010 14:41:59 +0200 ·

On Wed, 28 Apr 2010 08:06:24 -0400, David Morgan <user-4691629dd582@xymon.invalid>

▸ quoted from Xymon User in Richmond

wrote:

See all the fun stuff one can do with Xymon?

Jerald Sheets wrote:

Yeah, that's it's usage.

So, I guess from time to time the clients have issues hitting the
server?

Never thought to test in that direction.  


--j


On Apr 28, 2010, at 7:49 AM, David Morgan wrote:

We wanted to test the connectivity from the LDAP clients (running a
xymon agent) to the LDAP server and report their connectivity status.

It appears (at least from what I read) that the LDAP module is a test
from the Hobbit/XYmon Server to the LDAP server.

Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not
serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

 # Tell Hobbit about it
 $BB $BBDISP "status $MACHINE.$COLUMN $COLOR `date`

 ${MSG}
 "

 exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
      ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
      CMD $HOBBITCLIENTHOME/ext/getent.sh
      LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
      INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

Hi,

Could you share your script on xymonton ?

Regards,
Damien

list David Morgan · Wed, 28 Apr 2010 08:50:55 -0400 ·

Script and config (fixed with the correct BB line)

▸ quoted from dOCtoR MADneSs


% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

 # Tell Hobbit about it


 $BB $BBDISP "status+9h $MACHINE.$COLUMN $COLOR `date`

▸ quoted from dOCtoR MADneSs


 ${MSG}
 "

 exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
      ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
      CMD $HOBBITCLIENTHOME/ext/getent.sh


      LOGFILE $HOB$HOBBITCLIENTHOME/logs/ldap.log
      INTERVAL 4h

▸ quoted from dOCtoR MADneSs



user-d54077869176@xymon.invalid wrote:

On Wed, 28 Apr 2010 08:06:24 -0400, David Morgan <user-4691629dd582@xymon.invalid>
wrote:

See all the fun stuff one can do with Xymon?

Jerald Sheets wrote:

Yeah, that's it's usage.

So, I guess from time to time the clients have issues hitting the
server?

Never thought to test in that direction.  


--j


On Apr 28, 2010, at 7:49 AM, David Morgan wrote:

We wanted to test the connectivity from the LDAP clients (running a
xymon agent) to the LDAP server and report their connectivity status.

It appears (at least from what I read) that the LDAP module is a test
from the Hobbit/XYmon Server to the LDAP server.

Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it not
serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

 # Tell Hobbit about it


 $BB $BBDISP "status+9h $MACHINE.$COLUMN $COLOR `date`

▸ quoted from dOCtoR MADneSs


 ${MSG}
 "

 exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
      ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
      CMD $HOBBITCLIENTHOME/ext/getent.sh
      LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
      INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the 4
hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

Hi,

Could you share your script on xymonton ?

Regards,
Damien

list Josh Luthman · Wed, 28 Apr 2010 09:30:25 -0400 ·

Just compile the source.  I've a step by step guide.   Look for
install hobbit centos.

▸ quoted from Peter Brandt


On 4/28/10, Peter Brandt <user-b33d348a35c9@xymon.invalid> wrote:

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards;
 [peter at peterlinux Downloads]$ rpm -i hobbit-4.2.0-1.s390.rpm
error: Failed dependencies:
	liblber.so.199 is needed by hobbit-4.2.0-1.s390
	libldap.so.199 is needed by hobbit-4.2.0-1.s390
	librrd.so.0 is needed by hobbit-4.2.0-1.s390 [peter at peterlinux
Downloads]$


Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX

--


Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

“Success is not final, failure is not fatal: it is the courage to
continue that counts.”
--- Winston Churchill

list dOCtoR MADneSs · Wed, 28 Apr 2010 16:58:58 +0200 ·

On Wed, 28 Apr 2010 08:50:55 -0400, David Morgan <user-4691629dd582@xymon.invalid>

▸ quoted from David Morgan

wrote:

Script and config (fixed with the correct BB line)

% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

 # Tell Hobbit about it
 $BB $BBDISP "status+9h $MACHINE.$COLUMN $COLOR `date`

 ${MSG}
 "

 exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected to
the MGS LDAP Server
[ldap-con]
      ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
      CMD $HOBBITCLIENTHOME/ext/getent.sh
      LOGFILE $HOB$HOBBITCLIENTHOME/logs/ldap.log
      INTERVAL 4h


user-d54077869176@xymon.invalid wrote:

On Wed, 28 Apr 2010 08:06:24 -0400, David Morgan <user-4691629dd582@xymon.invalid>
wrote:

See all the fun stuff one can do with Xymon?

Jerald Sheets wrote:

Yeah, that's it's usage.

So, I guess from time to time the clients have issues hitting the
server?

Never thought to test in that direction.  


--j


On Apr 28, 2010, at 7:49 AM, David Morgan wrote:

We wanted to test the connectivity from the LDAP clients (running a
xymon agent) to the LDAP server and report their connectivity
status.

It appears (at least from what I read) that the LDAP module is a
test
from the Hobbit/XYmon Server to the LDAP server.

Dave

Jerald Sheets wrote:

Hobbit has a built in LDAP test if I remember correctly.  Was it
not
serving your needs?

--jms


On Apr 27, 2010, at 3:55 PM, David Morgan wrote:

We have a custom client side script that we wrote to test ldap
connectivity  (See below)

% cat getent.sh

#!/bin/sh

 COLUMN=ldap-con      # Does the server have an LDAP conection
 COLOR=green          # By default, everything is OK
 MSG="LDAP Connectivity Check"

 TESTVAL=`/usr/bin/getent group admins | wc -l`

 # Do whatever you need to test for something
 # As an example, go red if /tmp/badstuff exists.
 if [ $TESTVAL -eq 0 ]
 then
    COLOR=red
    MSG="${MSG}

    LDAP Configureation and Connectivity is BORKED UP
    "
 else
    MSG="${MSG}

    LDAP Configureation and Connectivity is OK
    "
 fi

 # Tell Hobbit about it
 $BB $BBDISP "status+9h $MACHINE.$COLUMN $COLOR `date`

 ${MSG}
 "

 exit 0


And the following is our clientlocal.sh portion for this script:

# LDAP Check - This command makes sure that this box is connected
to
the MGS LDAP Server
[ldap-con]
      ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
      CMD $HOBBITCLIENTHOME/ext/getent.sh
      LOGFILE $HOBBITCLIENTHOME/logs/ldap.log
      INTERVAL 4h

As can be seen, we have it running every 4 hours.  The status
check
should be green, however, it goes to purple.  Is there a way (and
where/how) to change the default timeout for this, as I think the

hour time is making it puke.

Both these scripts are on the client side.

-- 
David S. Morgan CISSP, CCNP
aka: user-4691629dd582@xymon.invalid

"When the Winds of Change Blow Hard Enough,
the Most trivial of things can turn into deadly projectiles"

Hi,

Could you share your script on xymonton ?

Regards,
Damien

Thank you for the code, but I think it should be very nice to share on
xymonton, in order to allow any other ppl to use your script, instead of
rewriting one from scratch. It should also allow you to be contacted if
bugs or code optimization have been found

list Peter Brandt · Wed, 28 Apr 2010 11:28:44 -0400 ·

Thanks Josh; I am new to Hobbit, where would the guide you mentioned be published?

Regards;

▸ quoted from Josh Luthman



Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX


Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public record request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing.

▸ quoted from Josh Luthman

-----Original Message-----
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid] 
Sent: Wednesday, April 28, 2010 9:30 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Dependencies when installing

Just compile the source.  I've a step by step guide.   Look for
install hobbit centos.

On 4/28/10, Peter Brandt <user-b33d348a35c9@xymon.invalid> wrote:

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards;
 [peter at peterlinux Downloads]$ rpm -i hobbit-4.2.0-1.s390.rpm
error: Failed dependencies:
	liblber.so.199 is needed by hobbit-4.2.0-1.s390
	libldap.so.199 is needed by hobbit-4.2.0-1.s390
	librrd.so.0 is needed by hobbit-4.2.0-1.s390 [peter at peterlinux
Downloads]$


Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX

-- 
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

"Success is not final, failure is not fatal: it is the courage to
continue that counts."
--- Winston Churchill

list Josh Luthman · Wed, 28 Apr 2010 11:34:28 -0400 ·

http://tinyurl.com/2w4r5n3

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

“Success is not final, failure is not fatal: it is the courage to continue
that counts.”
--- Winston Churchill


On Wed, Apr 28, 2010 at 11:28 AM, Peter Brandt <user-b33d348a35c9@xymon.invalid> wrote:

Thanks Josh; I am new to Hobbit, where would the guide you mentioned be
published?

Regards;


Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX

Under Florida law, e-mail addresses are public records. If you do not want
your e-mail address released in response to a public record request, do not
send electronic mail to this entity. Instead, contact this office by phone
or in writing.


-----Original Message-----
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid]
Sent: Wednesday, April 28, 2010 9:30 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Dependencies when installing

Just compile the source.  I've a step by step guide.   Look for
install hobbit centos.

On 4/28/10, Peter Brandt <user-b33d348a35c9@xymon.invalid> wrote:

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards;
 [peter at peterlinux Downloads]$ rpm -i hobbit-4.2.0-1.s390.rpm
error: Failed dependencies:
      liblber.so.199 is needed by hobbit-4.2.0-1.s390
      libldap.so.199 is needed by hobbit-4.2.0-1.s390
      librrd.so.0 is needed by hobbit-4.2.0-1.s390 [peter at peterlinux
Downloads]$


Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX

--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

"Success is not final, failure is not fatal: it is the courage to
continue that counts."
--- Winston Churchill

list Galen Johnson · Wed, 28 Apr 2010 13:11:15 -0400 ·

Josh, would you mind dropping that with a brief description on the Xymonton FAQ page?

Thanks

=G=

▸ quoted from Josh Luthman

From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid]
Sent: Wednesday, April 28, 2010 11:34 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Dependencies when installing

http://tinyurl.com/2w4r5n3

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

"Success is not final, failure is not fatal: it is the courage to continue that counts."
--- Winston Churchill

On Wed, Apr 28, 2010 at 11:28 AM, Peter Brandt <user-b33d348a35c9@xymon.invalid<mailto:user-b33d348a35c9@xymon.invalid>> wrote:
Thanks Josh; I am new to Hobbit, where would the guide you mentioned be published?

Regards;

Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX

Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public record request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing.

-----Original Message-----
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid<mailto:user-4c45a83f15cb@xymon.invalid>]
Sent: Wednesday, April 28, 2010 9:30 AM
To: user-ae9b8668bcde@xymon.invalid<mailto:user-ae9b8668bcde@xymon.invalid>
Subject: Re: [hobbit] Dependencies when installing

Just compile the source.  I've a step by step guide.   Look for
install hobbit centos.

On 4/28/10, Peter Brandt <user-b33d348a35c9@xymon.invalid<mailto:user-b33d348a35c9@xymon.invalid>> wrote:

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards;
 [peter at peterlinux Downloads]$ rpm -i hobbit-4.2.0-1.s390.rpm
error: Failed dependencies:
      liblber.so.199 is needed by hobbit-4.2.0-1.s390
      libldap.so.199 is needed by hobbit-4.2.0-1.s390
      librrd.so.0 is needed by hobbit-4.2.0-1.s390 [peter at peterlinux
Downloads]$


Peter Brandt - System Administrator
Palm Beach County Library System
XXXX Summit Boulevard
West Palm Beach, FL, 33406
Library (Main Number): +X.XXX.XXX.XXXX
Direct line:+X.XXX.XXX.XXXX
Fax +X.XXX.XXX.XXXX

--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

"Success is not final, failure is not fatal: it is the courage to
continue that counts."
--- Winston Churchill

list Ralph Mitchell · Wed, 28 Apr 2010 18:04:44 -0400 ·

▸ quoted from Peter Brandt

On Wed, Apr 28, 2010 at 7:19 AM, Peter Brandt <user-b33d348a35c9@xymon.invalid> wrote:

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards;
 [peter at peterlinux Downloads]$ rpm -i hobbit-4.2.0-1.s390.rpm
error: Failed dependencies:
       liblber.so.199 is needed by hobbit-4.2.0-1.s390
       libldap.so.199 is needed by hobbit-4.2.0-1.s390
       librrd.so.0 is needed by hobbit-4.2.0-1.s390

The first two libraries are part of LDAP and the other is rrdtool.  I
couldn't tell you the exact rpms to load as I don't have any kind of RedHat
installation, but I suspect you'll want something like
openldap-devel.xxx.rpm & rrdtool-devel.xxx.rpm

Ralph Mitchell

list Xymon User in Richmond · Wed, 28 Apr 2010 19:28:39 -0400 ·

▸ quoted from Ralph Mitchell

On Wed, April 28, 2010 18:04, Ralph Mitchell wrote:

On Wed, Apr 28, 2010 at 7:19 AM, Peter Brandt <user-b33d348a35c9@xymon.invalid>
wrote:

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards; [peter at peterlinux Downloads]$ rpm -i
hobbit-4.2.0-1.s390.rpm error: Failed dependencies: liblber.so.199 is
needed by hobbit-4.2.0-1.s390 libldap.so.199 is needed by
hobbit-4.2.0-1.s390 librrd.so.0 is needed by hobbit-4.2.0-1.s390

The first two libraries are part of LDAP and the other is rrdtool.  I
couldn't tell you the exact rpms to load as I don't have any kind of
RedHat installation, but I suspect you'll want something like
openldap-devel.xxx.rpm & rrdtool-devel.xxx.rpm

You need openldap-devel and rrdtool-devel, but in older versions not in
the F12 repos.  Much as I favor rpm-based software installation on
rpm-based distros, Josh Luthman's earlier advice to compile from source is
going to be your easiest path.  If you do choose to hunt down and install
the correct rpm versions of the dependencies, you'll need to put exclude=
lines for them in your yum.conf to avoid yum errors.

From the name of the rpm, it looks like you're installing for a System
390?  That looks odd.

list Richard Finegold · Thu, 29 Apr 2010 17:13:15 -0700 ·

Iain, are you sending status+6m for your 5 minute scripts?

▸ quoted from Iain M Conochie


On Wed, Apr 28, 2010 at 04:23, Iain M Conochie <user-c784e16a5170@xymon.invalid> wrote:

<snip>
You really need to put in status+5h instead of status for a 4 hour script.
This tells the hobbit server not to expire the message for 5 hours.

regards
Iain

list Iain M Conochie · Fri, 30 Apr 2010 11:13:18 +0100 ·

Richard Finegold wrote:

Iain, are you sending status+6m for your 5 minute scripts?

Nope. They default to time out after 20 minutes.

So a 5 minute script times out in quadruple the time it is supposed to run in.

You will need to add a greater time than the runtime to ensure no purple messages.

As I do not know if this will correctly parse decimals then i felt a default of script run time +1 would be adequate

Iain

▸ quoted from Iain M Conochie

On Wed, Apr 28, 2010 at 04:23, Iain M Conochie <user-c784e16a5170@xymon.invalid> wrote:

<snip>
You really need to put in status+5h instead of status for a 4 hour script.
This tells the hobbit server not to expire the message for 5 hours.

regards
Iain

list Peter Brandt · Sat, 1 May 2010 14:35:37 -0400 ·

I am getting the rpm from the page http://hobbitmon.sourceforge.net/

Is this not the best starting place for a new hobbit user?


 Regards;

-peter-

▸ quoted from Xymon User in Richmond


 

-----Original Message-----
From: Xymon User in Richmond [mailto:user-24d6f8323faa@xymon.invalid] 
Sent: Wednesday, April 28, 2010 7:29 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Dependencies when installing

On Wed, April 28, 2010 18:04, Ralph Mitchell wrote:

On Wed, Apr 28, 2010 at 7:19 AM, Peter Brandt <user-b33d348a35c9@xymon.invalid>
wrote:

Hello, when installing I am seeing the following errors and yum finds
nothing to do.

I am on Fedora 12, can you offer any advice?

Thank you and regards; [peter at peterlinux Downloads]$ rpm -i
hobbit-4.2.0-1.s390.rpm error: Failed dependencies: liblber.so.199 is
needed by hobbit-4.2.0-1.s390 libldap.so.199 is needed by
hobbit-4.2.0-1.s390 librrd.so.0 is needed by hobbit-4.2.0-1.s390

The first two libraries are part of LDAP and the other is rrdtool.  I
couldn't tell you the exact rpms to load as I don't have any kind of
RedHat installation, but I suspect you'll want something like
openldap-devel.xxx.rpm & rrdtool-devel.xxx.rpm

You need openldap-devel and rrdtool-devel, but in older versions not in
the F12 repos.  Much as I favor rpm-based software installation on
rpm-based distros, Josh Luthman's earlier advice to compile from source is
going to be your easiest path.  If you do choose to hunt down and install
the correct rpm versions of the dependencies, you'll need to put exclude=
lines for them in your yum.conf to avoid yum errors.

From the name of the rpm, it looks like you're installing for a System
390?  That looks odd.

Custom script shows purple 🔗 link

Custom script shows purple