Your message dated Tue, 6 May 2014 14:09:24 -0700 with message-id <camxh3qbekg24uyvqtsfr8sr95+hyti+v_uytca4av62kcqg...@mail.gmail.com> and subject line Re: slapd lenny->squeeze upgrade failure: still affected? has caused the Debian Bug report #608248, regarding Updating to slapd 2.4.23-7 fails 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.) -- 608248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608248 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: slapd Version: 2.4.11-1+lenny2 Severity: important Hi, I have problem with upgrading LDAP database to new version of slapd, with this error: Installing new version of config file /etc/init.d/slapd ... Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.11-1+lenny2... done. Moving old database directories to /var/backups: - directory dc=zshk,dc=cz... done. Loading from /var/backups/slapd-2.4.11-1+lenny2: - directory dc=zshk,dc=cz... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: Error, entries missing! entry 368: sambaDomainName=zshk,dc=zshk,dc=cz dpkg: error processing slapd (--configure): subprocess installed post-installation script returned error exit status 1 I don't know what is wrong. I use LDAP for samba and some other (web, moodle) authentication. Best regards, Martin Sin. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages slapd depends on: ii adduser 3.112+nmu2 add and remove users and groups ii coreutils 8.5-1 GNU core utilities ii debconf [debconf-2.0] 1.5.36 Debian configuration management sy ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libdb4.2 4.2.52+dfsg-5 Berkeley v4.2 Database Libraries [ ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libldap-2.4-2 2.4.11-1+lenny2 OpenLDAP libraries ii libltdl3 1.5.26-4+lenny1 A system independent dlopen wrappe ii libperl5.10 5.10.1-16 shared Perl library ii libsasl2-2 2.1.23.dfsg1-6 Cyrus SASL - authentication abstra ii libslp1 1.2.1-7.8 OpenSLP libraries ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii perl [libmime-base64-per 5.10.1-16 Larry Wall's Practical Extraction ii psmisc 22.11-1 utilities that use the proc file s ii unixodbc 2.2.14p2-1 ODBC tools libraries Versions of packages slapd recommends: ii libsasl2-modules 2.1.23.dfsg1-6 Cyrus SASL - pluggable authenticat Versions of packages slapd suggests: ii ldap-utils 2.4.11-1+lenny2 OpenLDAP utilities -- Configuration Files: /etc/default/slapd changed: SLAPD_CONF= SLAPD_USER="openldap" SLAPD_GROUP="openldap" SLAPD_PIDFILE= SLAPD_SERVICES="ldap:/// ldaps:///" SLAPD_SENTINEL_FILE=/etc/ldap/noslapd SLAPD_OPTIONS="" -- debconf information: slapd/tlsciphersuite: * shared/organization: zshk.cz slapd/upgrade_slapcat_failure: * slapd/backend: HDB * slapd/allow_ldap_v2: false * slapd/no_configuration: false * slapd/move_old_database: true slapd/suffix_change: false slapd/dump_database_destdir: /var/backups/slapd-VERSION * slapd/domain: zshk.cz slapd/password_mismatch: slapd/invalid_config: true slapd/slurpd_obsolete: slapd/dump_database: when needed slapd/migrate_ldbm_to_bdb: false * slapd/purge_database: false
--- End Message ---
--- Begin Message ---On Tue, May 6, 2014 at 1:39 PM, Martin Šín <[email protected]> wrote: > I could not stand it and tried it and it seems fine. For a complete > verification I will try on another virtual machine, but for now, I > cannot really see problem. Upgrade looks fine. Great! :) I take that to mean that your upgrade is OK now and the bug can be closed. If I'm wrong and you still have the same problem, you can always reopen it. thanks, Ryan
--- End Message ---
