[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 <simobimou (at) hotmail.com> 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.
>
> Do you have any idea about this !?
>
> Regards,
>
>
>
>
>
> ------------------------------
> From: mailinglist0 (at) skurfer.com
> 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/>
>
>