Kolab installation issues

Liam Kirsher liamk at numenet.com
Sun Dec 8 23:32:38 CET 2013


Additional information --

I was able to get ldap running by using setup-ds.  I tested it
successfully with ldapsearch:
/usr/lib/mozldap/ldapsearch -D "cn=Directory Manager" -w xxxxxx -b
"dc=mydomain,dc=com" -s sub "(objectclass=*)"

However, I'm still getting that error (traceback below) when trying to
start /etc/init.d/kolab-server.
I went in and changed line 235 like this, removing the extra list

    for primary_domain in list(set(domains.values()[0])):

and that worked!  Should I file this as a bug?

I still can't log in though.  The webadmin error log shows
> [08-Dec-2013 14:15:42 -0800](1o87t42ci4s6g1h80gii4e8443): [ERROR]
> (api) Bind failed for dn=uid=kolab-service,ou=Special
> Users,dc=numenet,dc=com: No such object
> [08-Dec-2013 14:15:42 -0800](1o87t42ci4s6g1h80gii4e8443): [ERROR]
> (api) Bind failed for dn=uid=kolab-service,ou=Special
> Users,dc=numenet,dc=com: No such object
Doing an ldapsearch I can see that Directory Manager is there. So, any
idea what's going on here?  Why is the Bind failing?

> /usr/lib/mozldap/ldapsearch -D "cn=Directory Manager" -w xxxx -b
> "dc=numenet,dc=com" -s sub "(objectclass=*)"
> version: 1
> dn: dc=numenet,dc=com
> objectClass: top
> objectClass: domain
> dc: numenet
>
> dn: cn=Directory Administrators,dc=numenet,dc=com
> objectClass: top
> objectClass: groupofuniquenames
> cn: Directory Administrators
> uniqueMember: cn=Directory Manager
>
> dn: ou=Groups,dc=numenet,dc=com
> objectClass: top
> objectClass: organizationalunit
> ou: Groups
>
> dn: ou=People,dc=numenet,dc=com
> objectClass: top
> objectClass: organizationalunit
> ou: People
>
> dn: ou=Special Users,dc=numenet,dc=com
> objectClass: top
> objectClass: organizationalUnit
> ou: Special Users
> description: Special Administrative Accounts
>
> dn: cn=Accounting Managers,ou=Groups,dc=numenet,dc=com
> objectClass: top
> objectClass: groupOfUniqueNames
> cn: Accounting Managers
> ou: groups
> description: People who can manage accounting entries
> uniqueMember: cn=Directory Manager
>
> dn: cn=HR Managers,ou=Groups,dc=numenet,dc=com
> objectClass: top
> objectClass: groupOfUniqueNames
> cn: HR Managers
> ou: groups
> description: People who can manage HR entries
> uniqueMember: cn=Directory Manager
>
> dn: cn=QA Managers,ou=Groups,dc=numenet,dc=com
> objectClass: top
> objectClass: groupOfUniqueNames
> cn: QA Managers
> ou: groups
> description: People who can manage QA entries
> uniqueMember: cn=Directory Manager
>
> dn: cn=PD Managers,ou=Groups,dc=numenet,dc=com
> objectClass: top
> objectClass: groupOfUniqueNames
> cn: PD Managers
> ou: groups
> description: People who can manage engineer entries
> uniqueMember: cn=Directory Manager


On 12/08/2013 12:24 AM, Liam Kirsher wrote:
> Hi --
>
> I have installed Kolab 3.1 on a new Debian 7.2 virtual machine.
> This mostly went pretty smoothly.  I installed from the Kolab repo. (I
> wrote a Chef recipe to facilitate this -- setting up the apt repos,
> removing the default exim stuff that was causing problems...)
>
> I tried to log in to the web interface with
>
>     cn="Directory Manager"
>
> However, I didn't know the password since it had been installed
> automatically.  I tried the default one in /etc/kolab/kolab.conf but
> that didn't work.
> On further examination, it seems I cannot start the kolab-server:
>
>> service kolab-server start
>> root at debian:/etc/init.d# Traceback (most recent call last):
>>   File "/usr/lib/python2.7/dist-packages/kolabd/__init__.py", line
>> 183, in run
>>     self.do_sync()
>>   File "/usr/lib/python2.7/dist-packages/kolabd/__init__.py", line
>> 235, in do_sync
>>     for primary_domain in list(set(domains.values())):
>> TypeError: unhashable type: 'list'
> Also, I'm not finding an ldap process running on port 389 (or
> anywhere, for that matter).
> Starting it fails:
>> root at debian:/etc/init.d# service dirsrv start
>> [info] no dirsrv instances configured so not starting 389 DS.
>> root at debian:/etc/init.d# service dirsrv-admin start
>> [info] No /etc/dirsrv/admin-serv/adm.conf file is present.
> Possibly related to
> https://lists.kolab.org/pipermail/devel/2012-September/013623.html ?
>
> So, where do I start to debug this?
>
> Any help appreciated!
>
> Liam
>
>
>
> -- 
> Liam Kirsher
> PGP: http://liam.numenet.com/pgp/
>
>
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users

-- 
Liam Kirsher
PGP: http://liam.numenet.com/pgp/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20131208/f5180a77/attachment.html>


More information about the users mailing list