On Tue, Feb 19, 2008 at 04:56:23PM +0000, Richard A Nelson wrote: > Package: slapd > Version: 2.4.7-5 > Severity: important
> Recently, SASL moved from db4.2 to db4.6, while slapd is still built > against 4.2 - and as a result, slapd is flooding the logs with this: > slapd[24852]: SASL [conn=7156] Error: unable to open Berkeley db > /etc/sasldb2: Invalid argument No, I don't believe this is the source of the error. There are no handles being passed between libsasl and slapd that would cause the wrong libdb to be used when accessing this file, only libsasl itself will access this file directly; and both versions of libdb have symbol versioning which ensures that libsasl uses the correct libdb when opening this database. Do you have an /etc/sasldb2 that you intend to use with slapd? By default SASL will try to use this database when not otherwise configured; I don't recall what error message it spits out in that case, and don't have that in front of me at the moment. If you do have an /etc/sasldb2 that works with other apps but not with slapd, then we'll have to dig deeper for the cause, since upgrading slapd to db4.6 should not be required and is not really appropriate right now. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
