Package: slapd Version: 2.4.28-1.1 Severity: important Dear Maintainer,
I've installed slapd, and reconfigured it to use the back-sql backend, using PostgreSQL 9.1 as the RDBMS. The schema I am using is the one provided in the upstream tarball (used by the slapd automatic tests). After moving aside the /etc/ldap/slapd.d directory and providing a full and valid configuration in /etc/ldap/slapd.conf, the slapd server segfaults, without anything relevant in the logs, and also without a core dump (ulimit -c is set to unlimited). Running '/usr/sbin/slapd -Tt' also causes a segmentation fault, and this time a core dump is created. When running this core through gdb, it appears as if there's an endless recursion going on while parsing the configuration file. The stack trace for the active thread contains 622 frames. The outcome is that the back-sql backend is not usable since slapd can't be started with this backend. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages slapd depends on: ii adduser 3.113+nmu1 ii coreutils 8.13-3.1 ii debconf [debconf-2.0] 1.5.42 ii libc6 2.13-27 ii libdb5.1 5.1.29-1 ii libgcrypt11 1.5.0-3 ii libgnutls26 2.12.18-1 ii libldap-2.4-2 2.4.28-1.1 ii libltdl7 2.4.2-1 ii libodbc1 2.2.14p2-5 ii libperl5.14 5.14.2-9 ii libsasl2-2 2.1.25.dfsg1-4 ii libslp1 1.2.1-9 ii libwrap0 7.6.q-23 ii lsb-base 3.2+Debian31 ii multiarch-support 2.13-27 ii perl [libmime-base64-perl] 5.14.2-9 ii psmisc 22.16-1 Versions of packages slapd recommends: ii libsasl2-modules 2.1.25.dfsg1-4 Versions of packages slapd suggests: ii ldap-utils 2.4.28-1.1 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
