I must admit, I hit the wall. Exchange server has anonymous LDAP access disabled (as I understand as a result of some security patch) and ldap.monitor requires anonymous access.
So, ldap.monitor is not suitable for monitoring patched Exchange server. On Tue, Dec 18, 2001 at 12:22:30PM -0800, Konstantin 'Kastus' Shchuka wrote: > On Tue, Dec 18, 2001 at 07:53:32AM -0600, Bugg, Ed wrote: > > We never depened on the ldap service but I thought it would be a nifty thing > > to try so I was able to get it running with this watch statement... > > > > I figure checking for the admin userid should be good enough of a search > > that will always return, and checking for the objectclass 'Top' should > > always return as well... be warned thought as I just found out ojectclass > > does not equate to objectClass. > > > > watch exchange_servers > > service ldap > > description LDAP Mail Gateway Availibity > > interval 5m > > monitor ldap.monitor -base="o=ABCBS" -filter="uid=admin" > > -attribute=objectClass -value=Top > > exclude_hosts terra > > depend SELF:ping > > period _WORK_HOURS_ > > alert mail.alert [EMAIL PROTECTED] > > period _ANYTIME_ > > alert qpage.alert bugge > > alertevery 1h > > > > Still no luck. I'm trying from command line: > > mon.d/ldap.monitor -base="o=CORP" -filter="uid=admin" -attribute=objectClass >-value=Top postman-int > > and getting : > > postman-int:389 > postman-int returned no entries > > I also tried uid=administrator and my own account, kastus, with the same result. > > I know LDAP is running on host postman-int, I can connect to the port 389, > but something is wrong with base, filter, and attribute parameters. > > mon is version 0.99.2, Exchange is 5.5sp4 -- Konstantin 'Kastus' Shchuka Unix System Administrator ePocrates Inc. tel 650.232.4886 fax 650.592.6995
