Hi, 2010/10/8 Soren Stoutner <sorenstout...@gmail.com>: > Subject: kolabd: Problem Upgrading Older Kolab Server to Newest Slapd > Package: kolabd > Version: 2.2.4-20100624-4 OK, latest one.
> Severity: important > .. > When I attempt to upgrade a Kolab server that has been in production for > several years, Upgrading from which version? (kolab was not in lenny). > I receive this error. > > r...@mail:/etc/default# dpkg --configure -a > Setting up slapd (2.4.23-6) ... > Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.17-2.1... done. > Moving old database directories to /var/backups: > Loading from /var/backups/slapd-2.4.17-2.1: > - directory dc=stoutner,dc=org... failed. > > Loading the database from the LDIF dump failed with the following > error while running slapadd: > /etc/ldap/slapd.conf: line 76: <replica> keyword is obsolete (ignored) > <= str2entry: str2ad(IMPPREFS): attribute type undefined > slapadd: could not parse entry (line=198) The problem comes from IMPPREFS. Storing Horde prefs in LDAP is deprecated by the Kolab project since 2.2.1 (see https://issues.kolab.org/issue3567). You should remove all those *Prefs attributes before the update. You can also re-add the Horde schema in the slapd.conf (and template). The recommended way is to remove all prefs from LDAP. Users will need to set those again. There is a script for this in §6 of http://hg.kolab.org/server/file/5f73a1437a1d/1st.README (you should adapt it to native packages). > I understand that this is a bug in slapd. I have filed a bug report at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599235 > but I have not yet had any response. Probably not. The bug comes from the kolabd package which removed the horde schema some time ago without providing a migration path. This was done in kolabd 2.2.1-20090304-1: "don't install horde schema anymore as horde now use flat files for preferences". > I am guessing that there is something > in my > /etc/ldap/slapd.conf file that it doesn't like, probably something that is > not commonly used outside of Kolab installations. Yes, and also not common in recent Kolab installations. > I tried looking at line 198 but couldn't find anything suspicious. I was > wondering if you know what is causing it to fail > and if there is a config change I can make that will allow it to succeed. This is line 198 of the slap dump, not the config file. > > My /etc/ldap/slapd.conf file is below: ... I won't provide a migration script for your case, but I will add a NEWS entry for other administrators. Regards -- Mathieu Parent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org