[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: commit: ldap/servers/slapd/back-ldap monitor.c Makefile.in init.c
Pierangelo Masarati wrote:
Howard Chu wrote:
Hm, test034-translucent is failing now, complaining at register time.
The local slapd.2.log:
@(#) $OpenLDAP: slapd 2.X (Sep 14 2006 11:59:20) $
hyc@mandolin:/home/hyc/OD/hobj/servers/slapd
bdb_db_open: Warning - No DB_CONFIG file found in directory
./testrun/db.2.a: (2)
Expect poor performance for suffix o=translucent.
monitor_back_register_entry_parent(""): base="cn=databases,cn=monitor"
scope=3
filter="(&(monitoredInfo=ldap)(!(monitorOverlay=ldap))(namingContexts:distinguishedNameMatch:=o=translucent))":
unable to find entry
backend_startup_one: bi_db_open failed! (-1)
backend_startup_one: bi_db_open failed! (-1)
slapd stopped.
connections_destroy: nothing to destroy.
I'll see if I can sort it out...
I already fixed that once; apparently I'm either still missing some
commits, or we have something different. Note that back-ldap here
should not inherit
monitoring stuff from the underlying database; specific monitoring
should be disabled (that was my intention) since it's not working the
way it should right now.
Oh, maybe a false alarm then. I have some revised filter code in my tree
at the moment, it's probably broken somewhere. (Was working on ITS#3707
features...) I'll try again with a clean source tree.
Basically, the reason I'm appending an entry below that of the database,
instead of adding to the database's entry, is because in some cases,
e.g. slapo-chain(5), we want more than one target, with specific URI,
stuff and cached connections, to be monitored simultaneously. That's
why "cn=Connections" is the default RDN, but slapo-chain(5), for
instance, customizes the RDN of the children entries it adds.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/