LDAP Issues from 20060926 Overlay

[jayk]

I did a layman -S to sync the overlay and did an emerge -uavD world which brought in the 20060926 version kolab ebuilds. After they were merged, I did etc-update and used the new config files as I had not modified anything in the templates. I logged into the webadmin OK and made a small change and kaboom, my ldap server tanked.

I was kicked out of the webadmin with an error message at the top that said it couldn't connect to the ldap server.

I tried multiple things, including running db4.2_recover in the openldap-data directory, deleting the openldap-data directory and re-merging openldap and then bootstrapping to get a new database, even doing emerge -e kolabd to re-merge a good deal of the tree involved in requirements for kolab--still slapd refused to start. An interesting thing was that after deleting the database and re-merging openldap, slapd would start during the bootstrap to setup the kolab database, but once kolab was bootstrapped, slapd would no longer start.

I ended up putting a >=kolabpackage-20060926 for the four kolab packages in /etc/portage/package.mask and downgrading to the 20060829 versions which then boostrapped and worked perfectly.

There seems to be something in the new versions that affects the ldap server in a very negative way.

Thanks,
Jason

[Gunnar Wrobel]

Yes indeed. I'm sorry for the mess. I did simply include the upstream CVS changes from the kolab project and there was another problem in there. I'll fix that today and issue another bug upstream.

And there will also be a change in the development scheme. The current dev packages will get masked until new changes have run through complete internal testing. This should reduce the likelihood of hickups like this one.

Cheers,

Gunnar

[jayk]

No problem. I'm not running it production yet anyway, so it wasn't that big of a deal.

Thanks,
Jason