Mathieu,<br><br><div class="im">On Sat, Oct 9, 2010 at 10:45 AM, Mathieu Parent <span dir="ltr"><<a href="mailto:math.parent@gmail.com" target="_blank">math.parent@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
> When I attempt to upgrade a Kolab server that has been in production for<br>
> several years,<br>
<br>
Upgrading from which version? (kolab was not in lenny).<br>
<br></blockquote></div><div><br>This server runs a constantly updated version of testing. Kolab was initially installed probably two years ago.<br> </div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The problem comes from IMPPREFS. Storing Horde prefs in LDAP is<br>
deprecated by the Kolab project since 2.2.1 (see<br>
<a href="https://issues.kolab.org/issue3567" target="_blank">https://issues.kolab.org/issue3567</a>).<br>
You should remove all those *Prefs attributes before the update. You<br>
can also re-add the Horde schema in the slapd.conf (and template).<br>
The recommended way is to remove all prefs from LDAP. Users will need<br>
to set those again.<br>
There is a script for this in §6 of<br>
<a href="http://hg.kolab.org/server/file/5f73a1437a1d/1st.README" target="_blank">http://hg.kolab.org/server/file/5f73a1437a1d/1st.README</a> (you should<br>
adapt it to native packages).<br>
<br></blockquote></div><br>Thanks for these instructions. This was the missing piece of information I wasn't able to find by myself.<br><br>I followed the instructions and removed all of the Horde information. When attempting to upgrade I now<br>
receive a new error that I can't seem to figure out.<br><br>root@mail:/etc/ldap# apt-get install slapd<br>Reading package lists... Done<br>Building dependency tree <br>Reading state information... Done<br>The following packages will be upgraded:<br>
slapd<br>1 upgraded, 0 newly installed, 0 to remove and 75 not upgraded.<br>Need to get 0B/1,586kB of archives.<br>After this operation, 45.1kB disk space will be freed.<br>Preconfiguring packages ...<br>(Reading database ... 162158 files and directories currently installed.)<br>
Preparing to replace slapd 2.4.17-2.1 (using .../slapd_2.4.23-6_amd64.deb) ...<br>Stopping OpenLDAP: slapd.<br> Dumping to /var/backups/slapd-2.4.17-2.1: <br>
- directory dc=stoutner,dc=org... slapcat: Symbol
`ldap_int_global_options' has different size in shared object, consider
re-linking<br>
str2entry: invalid value for attributeType objectClass #0 (syntax 1.3.6.1.4.1.1466.115.121.1.38)<br>root_dse_read_file: could not parse entry (file="/etc/kolab/rootDSE.ldif" line=3)<br>olcRootDSE: value #0: <olcRootDSE> could not read file /etc/kolab/rootDSE.ldif<br>
config error processing cn=config: <olcRootDSE> could not read file<br>slapcat: bad configuration directory!<br>failed.<br>dpkg: error processing /var/cache/apt/archives/slapd_2.4.23-6_amd64.deb (--unpack):<br> subprocess new pre-installation script returned error exit status 1<br>
configured to not write apport reports<br> Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.23-6... done.<br>Starting OpenLDAP: slapd.<br>Errors were encountered while processing:<br>
/var/cache/apt/archives/slapd_2.4.23-6_amd64.deb<br>E: Sub-process /usr/bin/dpkg returned an error code (1)<br><br>The contents of /etc/kolab/rootDSE.ldif is simply:<br><br>dn:<br>objectClass: kolab<br><br>Note that there is no line 3. I found one reference to this error relating to an OpenSUSE installation, but I'm not sure<br>
how it applies to Debian. <a href="http://www.kolab.org/pipermail/kolab-users/2009-May/009964.html" target="_blank">http://www.kolab.org/pipermail/kolab-users/2009-May/009964.html</a><br><br>Soren