Centos dirsrv problem with setup-kolab

Thu Nov 15 13:45:19 CET 2012

Hey All, 

I am trying to sort a fresh install of kolab in Centos 6.2 following the instructions http://www.kolab.org/howto/quick-howto-kolab-24-centos-62 and http://docs.kolab.org/en-US/Kolab_Groupware/2.4/html/Community_Installation_Guide/index.html I get as far as setup-kolab and then have the problems detailed below. 

When I run setup-kolab I get as far as the below and then it hangs:- 

[root at mail ~]# setup-kolab 
Could not change the ownership of log file /var/log/kolab/pykolab.log 

Please supply a password for the LDAP administrator user 'admin', used to login 
to the graphical console of 389 Directory server. 

Administrator password [QD-PfFTzpWTLiNO]: 
Confirm Administrator password: 

Please supply a password for the LDAP Directory Manager user, which is the 
administrator user you will be using to at least initially log in to the Web 
Admin, and that Kolab uses to perform administrative tasks. 

Directory Manager password [VS0plkXHk7lhhiP]: 
Confirm Directory Manager password: 
User [nobody]: 
Group [nobody]: 

This setup procedure plans to set up Kolab Groupware for the following domain 
name space. This domain name is obtained from the reverse DNS entry on your 
network interface. Please confirm this is the appropriate domain name space. 

ragein.co.uk [Y/n]: 

The standard root dn we composed for you follows. Please confirm this is the root 
dn you wish to use. 

dc=ragein,dc=co,dc=uk [Y/n]: 

As I have already recieved this error once and rebuilt to ensure I had done things correctly as the guide asks I was also looking for an error in the dirsrv setup detailed below:- 

[root at mail ~]# tail -f /var/log/dirsrv/slapd-mail/errors 
[15/Nov/2012:13:09:08 +0100] - import ragein_co_uk: Finished scanning file "/tmp/ldiftEfRbU.ldif" (9 entries) 
[15/Nov/2012:13:09:09 +0100] - import ragein_co_uk: Workers finished; cleaning up... 
[15/Nov/2012:13:09:09 +0100] - import ragein_co_uk: Workers cleaned up. 
[15/Nov/2012:13:09:09 +0100] - import ragein_co_uk: Cleaning up producer thread... 
[15/Nov/2012:13:09:09 +0100] - import ragein_co_uk: Indexing complete. Post-processing... 
[15/Nov/2012:13:09:09 +0100] - import ragein_co_uk: Generating numSubordinates complete. 
[15/Nov/2012:13:09:09 +0100] - import ragein_co_uk: Flushing caches... 
[15/Nov/2012:13:09:10 +0100] - import ragein_co_uk: Closing files... 
[15/Nov/2012:13:09:10 +0100] - All database threads now stopped 
[15/Nov/2012:13:09:10 +0100] - import ragein_co_uk: Import complete. Processed 9 entries in 2 seconds. (4.50 entries/sec) 
[15/Nov/2012:13:09:23 +0100] - 389-Directory/1.2.10.2 B2012.194.51 starting up 
[15/Nov/2012:13:09:23 +0100] - Failed to create semaphore for stats file (/var/run/dirsrv/slapd-mail.stats). Error 13.(Permission denied) 
[15/Nov/2012:13:19:24 +0100] - 389-Directory/1.2.10.2 B2012.194.51 starting up 
[15/Nov/2012:13:19:24 +0100] - Failed to create semaphore for stats file (/var/run/dirsrv/slapd-mail.stats). Error 13.(Permission denied) 

After leaving setup-kolab for 15 mins to ensure it was really hanging I left it running and tried to start the dir service in another terminal which gave the following output:- 

[root at mail ~]# service dirsrv start 
Starting dirsrv: 
mail... [FAILED] 
*** Warning: 1 instance(s) failed to start 

After trying to start the dir service manually I noticed that setup-kolab had continued on it's own:- 

mail... server already stopped [FAILED] 
*** Error: 1 instance(s) unsuccessfully stopped [FAILED] 
Starting dirsrv: 
mail... [FAILED] 
*** Warning: 1 instance(s) failed to start 

Please supply a Cyrus Administrator password. This password is used by Kolab to 
execute administrative tasks in Cyrus IMAP. You may also need the password 
yourself to troubleshoot Cyrus IMAP and/or perform other administrative tasks 
against Cyrus IMAP directly. 

Cyrus Administrator password [ilqIH-8P77rPRDk]: 
Confirm Cyrus Administrator password: 

Please supply a Kolab Service account password. This account is used by various 
services such as Postfix, and Roundcube, as anonymous binds to the LDAP server 
will not be allowed. 

Kolab Service password [Qq_fPt_yy98Dmj7]: 
Confirm Kolab Service password: 
Traceback (most recent call last): 
File "/usr/sbin/setup-kolab", line 42, in 
setup.run() 
File "/usr/lib/python2.6/site-packages/pykolab/setup/__init__.py", line 42, in run 
components.execute('_'.join(to_execute)) 
File "/usr/lib/python2.6/site-packages/pykolab/setup/components.py", line 143, in execute 
execute(component) 
File "/usr/lib/python2.6/site-packages/pykolab/setup/components.py", line 188, in execute 
components[component_name]['function'](conf.cli_args, kw) 
File "/usr/lib/python2.6/site-packages/pykolab/setup/setup_ldap.py", line 336, in execute 
auth._auth.ldap.add_s(dn, ldif) 
File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 194, in add_s 
msgid = self.add(dn,modlist) 
File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 191, in add 
return self.add_ext(dn,modlist,None,None) 
File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 176, in add_ext 
return self._ldap_call(self._l.add_ext,dn,modlist,RequestControlTuples(serverctrls),RequestControlTuples(clientctrls)) 
File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 99, in _ldap_call 
result = func(*args,**kwargs) 
ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"} 
complete. 

F rom what I can see something is going wrong with the 389 directory service setup but I'm a bit clueless as to what I notice that I get two errors in the log ten minutes apart (below) am I simply just being impatient or is something going screwey ? 

[15/Nov/2012:13:09:23 +0100] - 389-Directory/1.2.10.2 B2012.194.51 starting up 
[15/Nov/2012:13:09:23 +0100] - Failed to create semaphore for stats file (/var/run/dirsrv/slapd-mail.stats). Error 13.(Permission denied) 
[15/Nov/2012:13:19:24 +0100] - 389-Directory/1.2.10.2 B2012.194.51 starting up 
[15/Nov/2012:13:19:24 +0100] - Failed to create semaphore for stats file (/var/run/dirsrv/slapd-mail.stats). Error 13.(Permission denied) 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20121115/d0d4aca2/attachment.html>