badtest option for ldap

8 messages in this thread

list Simo Hmami · Wed, 19 Jan 2011 10:53:23 +0000 ·

Hi,
It seems that the "badtest" option is not working for all the network tests, it works fine for the http but not for ldap.I'm using xymon 4.2.3Did any one manage to get it work for ldap ?
Sincerely,

list Rob McBroom · Wed, 19 Jan 2011 09:10:18 -0500 ·

On Jan 19, 2011, at 5:53 AM, simo hmami wrote:

It seems that the "badtest" option is not working for all the network tests, it works fine for the http but not for ldap.
I'm using xymon 4.2.3
Did any one manage to get it work for ldap ?


I've had it enabled for a while. I'm using “badldaps:1:2:5” and I'm pretty sure it's working. I see some alerts on the “ol” test (which monitors regular LDAP on 389) and then some alerts on “ldaps” that come a few minutes later. However, I mainly just didn't want to be alerted during daily log rotation, which is predictable, so I've been using DOWNTIME to silence the alerts. I'm not really depending on badldaps at this point.

By the way, I highly recommend Buchan Milne's script for monitoring LDAP…

http://staff.telkomsa.net/~bgmilne/xymon/ol/

-- 
Rob McBroom
<http://www.skurfer.com/>;

list Simo Hmami · Thu, 20 Jan 2011 10:51:08 +0000 ·

Thank you for your answer
you are right0.0.0.0 hostname # ldap badldap:1,2,5 works fine 
but 0.0.0.0 hostname # ldap://somehost:someprot/dn  ldaplogin=login:pwd badldap:1,2,5doesn't work, it goes red immediately when there is an error.
Do you have any idea about this !?
Regards,

From: user-371ba9bb5b75@xymon.invalid
Date: Wed, 19 Jan 2011 09:10:18 -0500
To: xymon at xymon.com
Subject: Re: [xymon] badtest option for ldap

On Jan 19, 2011, at 5:53 AM, simo hmami wrote:It seems that the "badtest" option is not working for all the network tests, it works fine for the http but not for ldap.I'm using xymon 4.2.3Did any one manage to get it work for ldap ?

▸ quoted from Rob McBroom

I've had it enabled for a while. I'm using “badldaps:1:2:5” and I'm pretty sure it's working. I see some alerts on the “ol” test (which monitors regular LDAP on 389) and then some alerts on “ldaps” that come a few minutes later. However, I mainly just didn't want to be alerted during daily log rotation, which is predictable, so I've been using DOWNTIME to silence the alerts. I'm not really depending on badldaps at this point.
By the way, I highly recommend Buchan Milne's script for monitoring LDAP…
http://staff.telkomsa.net/~bgmilne/xymon/ol/

-- 
Rob McBroom
<http://www.skurfer.com/>;

list Larry Barber · Thu, 20 Jan 2011 09:41:14 -0600 ·

You should be using colons instead of commas: badldap:1:2:5 .

Thanks,
Larry Barber

On Thu, Jan 20, 2011 at 4:51 AM, simo hmami <user-33c2c6af3912@xymon.invalid> wrote:

Thank you for your answer

you are right
0.0.0.0 hostname # ldap badldap:1,2,5
works fine

but
0.0.0.0 hostname # ldap://somehost:someprot/dn  ldaplogin=login:pwd
badldap:1,2,5
doesn't work, it goes red immediately when there is an error.

▸ quoted from Simo Hmami

Do you have any idea about this !?

Regards,

From: user-371ba9bb5b75@xymon.invalid
Date: Wed, 19 Jan 2011 09:10:18 -0500
To: xymon at xymon.com
Subject: Re: [xymon] badtest option for ldap

On Jan 19, 2011, at 5:53 AM, simo hmami wrote:

It seems that the "badtest" option is not working for all the network
tests, it works fine for the http but not for ldap.
I'm using xymon 4.2.3
Did any one manage to get it work for ldap ?

I've had it enabled for a while. I'm using “badldaps:1:2:5” and I'm pretty
sure it's working. I see some alerts on the “ol” test (which monitors
regular LDAP on 389) and then some alerts on “ldaps” that come a few minutes
later. However, I mainly just didn't want to be alerted during daily log
rotation, which is predictable, so I've been using DOWNTIME to silence the
alerts. I'm not really depending on badldaps at this point.

By the way, I highly recommend Buchan Milne's script for monitoring LDAP…


http://staff.telkomsa.net/~bgmilne/xymon/ol/<http://staff.telkomsa.net/%7Ebgmilne/xymon/ol/>;

--
Rob McBroom
<http://www.skurfer.com/>;

list Simo Hmami · Thu, 20 Jan 2011 16:44:13 +0000 ·


Yes of course im using a colons ,  it was just a mistake
the conf im using is : 0.0.0.0 hostname # ldap://somehost:someprot/dn  ldaplogin=login:pwd badldap:1:2:5but unfortunatly it doesn't seem to be working!!
Regards,

▸ quoted from Larry Barber

Date: Thu, 20 Jan 2011 09:41:14 -0600
From: user-6ef9c2864140@xymon.invalid
To: xymon at xymon.com
Subject: Re: [xymon] badtest option for ldap

You should be using colons instead of commas: badldap:1:2:5 . 

Thanks,
Larry Barber

On Thu, Jan 20, 2011 at 4:51 AM, simo hmami <user-33c2c6af3912@xymon.invalid> wrote:

Thank you for your answer
you are right0.0.0.0 hostname # ldap badldap:1,2,5 works fine 
but 0.0.0.0 hostname # ldap://somehost:someprot/dn  ldaplogin=login:pwd badldap:1,2,5
doesn't work, it goes red immediately when there is an error.
Do you have any idea about this !?
Regards,

From: user-371ba9bb5b75@xymon.invalid
Date: Wed, 19 Jan 2011 09:10:18 -0500
To: xymon at xymon.com

Subject: Re: [xymon] badtest option for ldap

On Jan 19, 2011, at 5:53 AM, simo hmami wrote:
It seems that the "badtest" option is not working for all the network tests, it works fine for the http but not for ldap.
I'm using xymon 4.2.3Did any one manage to get it work for ldap ?
I've had it enabled for a while. I'm using “badldaps:1:2:5” and I'm pretty sure it's working. I see some alerts on the “ol” test (which monitors regular LDAP on 389) and then some alerts on “ldaps” that come a few minutes later. However, I mainly just didn't want to be alerted during daily log rotation, which is predictable, so I've been using DOWNTIME to silence the alerts. I'm not really depending on badldaps at this point.

By the way, I highly recommend Buchan Milne's script for monitoring LDAP…
http://staff.telkomsa.net/~bgmilne/xymon/ol/

-- 
Rob McBroom
<http://www.skurfer.com/>;

list Xymon User in Richmond · Thu, 20 Jan 2011 11:56:31 -0500 ·

▸ quoted from Simo Hmami

On Thu, January 20, 2011 11:44, simo hmami wrote:


Yes of course im using a colons ,  it was just a mistake
the conf im using is : 0.0.0.0 hostname # ldap://somehost:someprot/dn
ldaplogin=login:pwd badldap:1:2:5but unfortunatly it doesn't seem to be
working!!
Regards,

It's not clear to me from the manpage whether ldaplogin might be treated
as a separate test.  Have you tried "badldaplogin"?

list Henrik Størner · Sun, 23 Jan 2011 11:25:31 +0000 (UTC) ·

Hi Simo,


In <user-ca4c524687d4@xymon.invalid> simo hmami <user-33c2c6af3912@xymon.invalid> writes:

    0.0.0.0 hostname # ldap badldap:1:2:5 
works fine but
    0.0.0.0 hostname # ldap://somehost:someprot/dn badldap:1:2:5
doesn't work

I couldn't get it to work myself, until I had a close look at the code.

Turns out that for LDAP URL's you have to use "badldapurl:1:2:5" instead. 
And no, this isn't documented anywhere - it will be now.


Regards,
Henrik

list Simo Hmami · Mon, 24 Jan 2011 11:28:25 +0000 ·

Hi, Great it works fine, Thank you very much Henrik
Regards,

▸ quoted from Henrik Størner

To: xymon at xymon.com
From: user-ce4a2c883f75@xymon.invalid
Date: Sun, 23 Jan 2011 11:25:31 +0000
Subject: Re: [xymon] badtest option for ldap

Hi Simo,


In <user-ca4c524687d4@xymon.invalid> simo hmami <user-33c2c6af3912@xymon.invalid> writes:

    0.0.0.0 hostname # ldap badldap:1:2:5 > works fine but
    0.0.0.0 hostname # ldap://somehost:someprot/dn badldap:1:2:5
doesn't work

I couldn't get it to work myself, until I had a close look at the code.

Turns out that for LDAP URL's you have to use "badldapurl:1:2:5" instead. And no, this isn't documented anywhere - it will be now.


Regards,
Henrik

badtest option for ldap 🔗 link

badtest option for ldap