Custom script shows purple
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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
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 <captkras at gmail.com> 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
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 <scottlryan at gmail.com> 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 <captkras at gmail.com> 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
The wiki -
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/FAQ#My_...
Then the man page - you need to run
bb status lifetime
On Tue, Apr 27, 2010 at 9:57 PM, David Morgan <captkras at gmail.com> 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 <scottlryan at gmail.com> 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 <captkras at gmail.com> 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
On Tue, Apr 27, 2010 at 4:13 PM, Scott Ryan <scottlryan at gmail.com> wrote:
The wiki -
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/FAQ#My_...
I updated this URL with more detail information.
Then the man page - you need to run
bb status lifetime
On Tue, Apr 27, 2010 at 9:57 PM, David Morgan <captkras at gmail.com> 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 <scottlryan at gmail.com> 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 <captkras at gmail.com> 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- T.J. Yang
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:captkras at gmail.com] Sent: Tuesday, April 27, 2010 4:58 PM To: hobbit at hswn.dk 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 <scottlryan at gmail.com> 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 <captkras at gmail.com> 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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
Galen Johnson wrote:
IIRC, you have to change your BB command to: $BB $BBDISP "status+4h $MACHINE.$COLUMN $COLOR
dateVerify this in the man page for BB.
=G=
-----Original Message----- From: David Morgan [mailto:captkras at gmail.com] Sent: Tuesday, April 27, 2010 4:58 PM To: hobbit at hswn.dk 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 <scottlryan at gmail.com> 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 <captkras at gmail.com> 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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Scott Ryan http://bonoboslr.wordpress.com/
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819
Just compile the source. I've a step by step guide. Look for install hobbit centos.
On 4/28/10, Peter Brandt <peter at pbclibrary.org> 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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
“Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill
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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819 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:josh at imaginenetworksllc.com] Sent: Wednesday, April 28, 2010 9:30 AM To: hobbit at hswn.dk 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 <peter at pbclibrary.org> 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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"Success is not final, failure is not fatal: it is the courage to continue that counts." --- Winston Churchill
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
“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 <peter at pbclibrary.org> 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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819
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:josh at imaginenetworksllc.com] Sent: Wednesday, April 28, 2010 9:30 AM To: hobbit at hswn.dk 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 <peter at pbclibrary.org> 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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"Success is not final, failure is not fatal: it is the courage to continue that counts." --- Winston Churchill
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Josh, would you mind dropping that with a brief description on the Xymonton FAQ page?
Thanks
=G=
From: Josh Luthman [mailto:josh at imaginenetworksllc.com] Sent: Wednesday, April 28, 2010 11:34 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Dependencies when installing
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"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 <peter at pbclibrary.org<mailto:peter at pbclibrary.org>> 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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819
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:josh at imaginenetworksllc.com<mailto:josh at imaginenetworksllc.com>] Sent: Wednesday, April 28, 2010 9:30 AM To: hobbit at hswn.dk<mailto:hobbit at hswn.dk> 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 <peter at pbclibrary.org<mailto:peter at pbclibrary.org>> 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 3650 Summit Boulevard West Palm Beach, FL, 33406 Library (Main Number): +1.561.233.2600 Direct line:+1.561.233.2752 Fax +1.561.688.9819
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk<mailto:hobbit-unsubscribe at hswn.dk>
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
"Success is not final, failure is not fatal: it is the courage to continue that counts." --- Winston Churchill
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk<mailto:hobbit-unsubscribe at hswn.dk>
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk<mailto:hobbit-unsubscribe at hswn.dk>
On Wed, Apr 28, 2010 at 7:19 AM, Peter Brandt <peter at pbclibrary.org> 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
On Wed, April 28, 2010 18:04, Ralph Mitchell wrote:
On Wed, Apr 28, 2010 at 7:19 AM, Peter Brandt <peter at pbclibrary.org> 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.
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-
-----Original Message----- From: Xymon User in Richmond [mailto:hobbit at epperson.homelinux.net] Sent: Wednesday, April 28, 2010 7:29 PM To: hobbit at hswn.dk 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 <peter at pbclibrary.org> 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.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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. :)
On Tue, Apr 27, 2010 at 13:57, David Morgan <captkras at gmail.com> 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?
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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Not really, this is in addition to that test.
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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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.
--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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Wed, 28 Apr 2010 08:06:24 -0400, David Morgan <captkras at gmail.com> 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 -lDo 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: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Hi,
Could you share your script on xymonton ?
Regards, Damien
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
doctor at makelofine.org wrote:
On Wed, 28 Apr 2010 08:06:24 -0400, David Morgan <captkras at gmail.com> 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 -lDo 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 4 hour time is making it puke.
Both these scripts are on the client side.
-- David S. Morgan CISSP, CCNP aka: captkras at gmail.com
"When the Winds of Change Blow Hard Enough, the Most trivial of things can turn into deadly projectiles"
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Hi,
Could you share your script on xymonton ?
Regards, Damien
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Wed, 28 Apr 2010 08:50:55 -0400, David Morgan <captkras at gmail.com> 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 -lDo 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
doctor at makelofine.org wrote:
On Wed, 28 Apr 2010 08:06:24 -0400, David Morgan <captkras at gmail.com> 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 $COLORdate> > ${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: captkras at gmail.com > > "When the Winds of Change Blow Hard Enough, > the Most trivial of things can turn into deadly projectiles" > > To unsubscribe from the hobbit list, send an e-mail to > hobbit-unsubscribe at hswn.dk > > >
>
>
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dkTo unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Hi,
Could you share your script on xymonton ?
Regards, Damien
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
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
<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.
*face palm* Duh! It's in our custom script. I am a doofus....
Iain M Conochie wrote:
<snip>
Tell Hobbit about it
$BB $BBDISP "status $MACHINE.$COLUMN $COLOR
dateYou 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.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Iain, are you sending status+6m for your 5 minute scripts?
On Wed, Apr 28, 2010 at 04:23, Iain M Conochie <iain at shihad.org> 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
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
On Wed, Apr 28, 2010 at 04:23, Iain M Conochie <iain at shihad.org> 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
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (12)
-
captkras＠gmail.com
-
doctor＠makelofine.org
-
Galen.Johnson＠sas.com
-
goldfndr＠gmail.com
-
hobbit＠epperson.homelinux.net
-
iain＠shihad.org
-
josh＠imaginenetworksllc.com
-
peter＠pbclibrary.org
-
questy＠gmail.com
-
ralphmitchell＠gmail.com
-
scottlryan＠gmail.com
-
tjyang2001＠gmail.com