ldapyellowfail tag
list Allan Spencer
Hey guys, Just been playing around with some LDAP tests recently to diagnose some issues on a customers LDAP we're hosting and occasionally it decides it doesn't want to respond to LDAP..or cant find the uid I'm searching for. I noticed theres a ldapyellowfail tag which I tried putting in so I got email but not paged about it but it doesn't seem to work for me I still get red messages. I'd prefer to be able to add this instead of doing a separate alert rule so any suggestions would be good.I know the ldaplogin works fine as I'm using this on another host that doesnt allow anonymous binds I've got this in my hosts file 192.168.1.202 dr202.cs.int # NK:conn ldap://dr202.cs.int:389/o=cls?uid=nadmin1 ldapyellowfail Cheers Allan
list Allan Spencer
▸
ZanDAhaR wrote:
Hey guys, Just been playing around with some LDAP tests recently to diagnose some issues on a customers LDAP we're hosting and occasionally it decides it doesn't want to respond to LDAP..or cant find the uid I'm searching for. I noticed theres a ldapyellowfail tag which I tried putting in so I got email but not paged about it but it doesn't seem to work for me I still get red messages. I'd prefer to be able to add this instead of doing a separate alert rule so any suggestions would be good.I know the ldaplogin works fine as I'm using this on another host that doesnt allow anonymous binds I've got this in my hosts file 192.168.1.202 dr202.cs.int # NK:conn ldap://dr202.cs.int:389/o=cls?uid=nadmin1 ldapyellowfail Cheers Allan
Sorry just reposting this seeing as I think it got lost amongst a few other emails and the new release Still getting red messages for ldap failures. I know I could add LDAP into the server.cfg file for the tests not to page red on but there are some that we DO want to get red msgs about Allan
list Henrik Størner
▸
On Mon, Jun 05, 2006 at 09:27:50AM +1000, ZanDAhaR wrote:
I noticed theres a ldapyellowfail tag which I tried putting in so I got email but not paged about it but it doesn't seem to work for me I still get red messages. I'd prefer to be able to add this instead of doing a separate alert rule so any suggestions would be good.I know the ldaplogin works fine as I'm using this on another host that doesnt allow anonymous binds
I checked up on this, and the "ldapyellowfail" option only applies to the result of the LDAP *query* - if Hobbit cannot connect to the LDAP server at all (i.e. it gets a "connection refused" or a timeout when trying to bind to the LDAP server), then you'll get a red status. The bb-hosts man-page does say so, although I'll admit it could be made a bit clearer. If that's not what you want, then you could use a "badldap:0:99999:99999" setting instead. Regards, Henrik