kolabd-20070510 and overlay "refint"

[Shvayakov]

Hi, all

New installation kolab:

Code:

System uname: 2.6.20-hardened-r2 x86_64 Intel(R) Xeon(TM) CPU 3.40GHz
Gentoo Base System release 1.12.9
Timestamp of tree: Fri, 01 Jun 2007 07:30:01 +0000

sys-libs/glibc-2.5-r3  USE="hardened multilib nls nptl -build -debug -glibc-compat20 -glibc-omitfp -nptlonly -profile (-selinux)"
net-mail/kolabd-20070510  USE="horde spam -legacy -mailman -webdav"
net-nds/openldap-2.3.35-r1  USE="berkdb crypt gdbm overlays perl readline samba slp ssl tcpd -debug -ipv6 -kerberos -minimal -odbc -sasl (-selinux) -smbkrb5passwd"

I get the following error when I try kolab_bootstrap -b

Code:

Enter fully qualified hostname of slave kolab server e.g. thishost.domain.tld [empty when done]:
prepare LDAP database...
temporarily starting slapd
Could not start temporary slapd:  at /usr/share/kolabd/scripts/kolab_bootstrap line 488.

I take command from 488 line and add for debugging "-d 1"

Code:

/usr/lib/openldap/slapd -h ldap://127.0.0.1:389/ -f /etc/openldap/slapd.conf -u ldap -g ldap -d 1

and in debug output:

Code:

overlay "refint" not found
slapd destroy: freeing system resources.
slapd stopped.

[Gunnar Wrobel]

Hm, yes openldap-2.3.35-r1 has been marked stable within portage yesterday. Sorry, I did not yet have the time to check for the impact on the kolab server. And since I am gone on vacation for the next two weeks I have to admit that I won't have any chance to fix the configuration during the next two weeks.

I will mask openldap-2.3.35-r1 within the overlay for now. That should force you back to the older version. If you insist on using the newer version you can probably also remove the "refint" line from the slapd.conf.template in /etc/kolab/templates.

Cheers,

Gunnar

[Gunnar Wrobel]

Masked. And thanks for the note!

[jayk]

Hi Gunnar,

I don't see the openldap mask in the kolab2/profiles/package.mask file. Unfortunately, my server update just finished and upgraded openldap and I have some breakage. I will downgrade and see how that goes. Just to let you know that the mask doesn't appear to be there.

Thanks,
Jason

[jayk]

Correction, it appears to be there. My apologies. I'm not sure why my system ignored the mask. Maybe something with Paludis?

Thanks,
Jason

[jayk]

I did a little digging and it appears that Paludis looks at the profiles/package.mask file and only applies it to the repository that it is in. In this case then, the packages masked there are not applied to the main portage tree, but only the kolab2 overlay. I will have to make sure I check the package.mask file and mirror it in my locally masked packages before I upgrade I guess.

Thanks,
Jason

[Gunnar Wrobel]

Thanks for the note. Indeed it makes sense to disallow cross-repository masking. But from time to time I will have to do this if I'm lagging behind the main portage tree. I cannot always be in sync

But concerning the OpenLDAP problem I will try to provide an update to the configuration soon. It should actually be easy.