[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.
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