[Kolab-devel] Kolab3 on Mageia update

[Thomas Spuhler]

On Sunday, December 16, 2012 08:11:00 AM Jeroen van Meeuwen (Kolab Systems) wrote:
> On 2012-12-16 01:58, Thomas Spuhler wrote:
> > I would really appreciate some hints. (BTW, there is an old kolab2
> > installed on this system)
> > 
> > Confirm Kolab Service password:
> > 
> > Traceback (most recent call last):
> >   (...snip...)
> >   File
> > 
> > "/usr/lib/python2.7/site-packages/pykolab/setup/setup_ldap.py", line
> > 398, in execute
> > 
> >   (...snip...)
> > 
> > ldap.INVALID_DN_SYNTAX: {'info': 'invalid DN', 'desc': 'Invalid DN
> > syntax'}
> 
> What setup-kolab is attempting to do here is add the 'cyrus-admin'
> account to LDAP (using ou=Special Users).
> 
> You can examine the DN it is attempting to use at [1], which is:
> 
>    dn = 'uid=%s,ou=Special Users,%s' % (conf.get('cyrus-imap',
> 'admin_login'), _input['rootdn'])
> 
> Because of the LDAP error suggesting an invalid DN syntax, I suspect
> that
> 
>    conf.get('cyrus-imap', 'admin_login')
> 
> is not resolving to an actual string, the DN therefore becoming
> "uid=,ou=Special Users,dc=example,dc=org" - this would be an invalid DN
> syntax.
> 
> You mentioned there is currently also kolab2 installed on the system,
> so I would check /etc/kolab/kolab.conf (if that is the configuration
> file you are using, it is normally shipped as part of the pykolab
> package, and this is the default location for pykolab to load the
> configuration from), and see if it is of the Kolab 3 format, it indeed
> has a 'cyrus-imap' INI section, and 'admin_login' is indeed a key (by
> default, with value 'cyrus-admin').
> 
> You may want to repeat a setup-kolab run with '-d 9', which will be
> very verbose, and exposes what commands are actually being executed
> against the LDAP server (through protocol tracing).
> 
> Kind regards,
> 
> Jeroen van Meeuwen
> 
> [1]
> http://git.kolab.org/pykolab/tree/pykolab/setup/setup_ldap.py?h=pykolab-0.5
> #n383

I found in the latest tarball the kolab3-schema and kolab3-ldif
I think the problem lies with ldap.

Now my questions is where should those two files be installed?
one of the spec files I found puts them into the docs directory which doesn't make much sense to me.
Can you please explain this?

-- 
Best regards
Thomas Spuhler