Your message dated Sat, 12 Jul 2008 02:33:51 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#466569: slapd: Needs a newer libdb, now that sasl is
using 4.6
has caused the Debian Bug report #466569,
regarding slapd: Needs a newer libdb, now that sasl is using 4.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
466569: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466569
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
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
-- System Information:
Debian Release: lenny/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'),
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24.2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages slapd depends on:
ii adduser 3.105 add and remove users and groups
ii coreutils 6.10-3 The GNU core utilities
ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy
ii libc6 2.7-8 GNU C Library: Shared libraries
ii libdb4.2 4.2.52+dfsg-4 Berkeley v4.2 Database Libraries [
ii libgnutls26 2.2.1-3 the GNU TLS library - runtime libr
ii libldap-2.4-2 2.4.7-5 OpenLDAP libraries
ii libltdl3 1.5.26-1 A system independent dlopen wrappe
ii libperl5.8 5.8.8-12 Shared Perl library
ii libsasl2-2 2.1.22.dfsg1-18 Cyrus SASL - authentication abstra
ii libslp1 1.2.1-7.1 OpenSLP libraries
ii libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra
ii perl [libmime-base64-per 5.8.8-12 Larry Wall's Practical Extraction
ii psmisc 22.6-1 Utilities that use the proc filesy
ii unixodbc 2.2.11-16 ODBC tools libraries
Versions of packages slapd recommends:
ii libsasl2-modules 2.1.22.dfsg1-18 Cyrus SASL - pluggable authenticat
-- debconf information:
slapd/tlsciphersuite:
slapd/fix_directory: true
shared/organization: cavein.org
slapd/upgrade_slapcat_failure:
slapd/backend: BDB
slapd/allow_ldap_v2: false
* slapd/no_configuration: true
slapd/move_old_database: true
slapd/suffix_change: false
slapd/slave_databases_require_updateref:
slapd/dump_database_destdir: /var/backups/slapd-VERSION
slapd/autoconf_modules: true
slapd/domain: cavein.org
slapd/password_mismatch:
slapd/invalid_config: true
slapd/slurpd_obsolete:
slapd/upgrade_slapadd_failure:
slapd/dump_database: when needed
slapd/migrate_ldbm_to_bdb: false
slapd/purge_database: false
--- End Message ---
--- Begin Message ---
On Wed, Jul 02, 2008 at 06:58:26PM -0700, Richard A Nelson wrote:
> On Sat, 28 Jun 2008, Steve Langasek wrote:
>> Hi Richard,
> Hey again, sorry we keep meeting this way
:-)
>>> Ok, I'll do some more checking on the systems exhibiting the message and
>>> make sure smtp auth is actually working - and if so, I'll just ignore
>>> the messages.
>> Were you able to confirm that smtp auth was still working? Should we close
>> this report, or do we still have a bug here of SASL for some reason logging
>> these messages at too high a priority?
> SMTP auth is indeed working - sorry for loosing track of all these
> issues... I'd suggest closing this
Ok. FWIW, I've tried to reproduce this problem here, and I cannot. In
unstable, with a freshly-created /etc/sasldb2 using the db4.6-based
sasl2-bin, and the current db4.2-linked slapd, not only do I not get any log
messages about invalid arguments, but I'm able to authenticate ldap
connections just fine against /etc/sasldb2 if I use pwcheck_method: auxprop.
So I agree that this report should be closed now. Good luck figuring out
why sasldb is being so noisy for you :/
--
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]
--- End Message ---
