[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: commit: ldap/servers/slapd/back-ldap monitor.c Makefile.in init.c



Howard Chu wrote:
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.
No, the error is in there, it slipped in again. The private back-ldap inherits monitoring on from the underlying database, but it cannot find the registration point. Right now, I think the right approach consists in making this error non-blocking, so that no monitoring is registered. I need to find a cleaner way to detect where to register (e.g. eliminate the additional filtering on the database type...)

p.



Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office:   +39.02.23998309
Mobile:   +39.333.4963172
Email:    pierangelo.masarati@sys-net.it
------------------------------------------