[SOLVED] Re: 3.0 on Debian Wheezy: setup-kolab failing because of not running 389

Johannes Graumann <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab
Message-ID <20120926125117.3596E19C2162__13025.860003154$1348663894$gmane$org@h1906259.stratoserver.net>
Johannes Graumann wrote:

> Jeroen van Meeuwen wrote:
> 
>> On Tuesday, September 25, 2012 04:07:19 PM Johannes Graumann wrote:
>>> So I keep digging into this and have been exploring what the responsible
>>> 
>>> > /usr/lib/python2.7/dist-packages/pykolab/setup/setup_ldap.py
>>> 
>>> is actually doing.
>>> 
>>> First off I find that "/usr/sbin/setup-ds-admin.pl" seems to be called
>>> "/usr/sbin/setup-ds-admin" here, so
>>> 
>>> > 225c225
>>> > <     setup_ds_admin = "/usr/sbin/setup-ds-admin.pl"
>>> > ---
>>> > 
>>> > >     setup_ds_admin = "/usr/sbin/setup-ds-admin"
>>> 
>>> might be in order.
>>> 
>> 
>> It's actually the '-admin' part of 'setup-ds-admin' that causes the
>> process to require the semaphore to be created.
>> 
>> Using just 'setup-ds' does succeed for me.
> 
> The semaphore issue is solved (see other part of this thread) by making
> sure /dev/shm is actually mounted as tmpfs ... the error described above
> is independent of the semaphore isse.
> The central parts are:
> 
>> Could not import LDIF file '/tmp/ldifUN9JLt.ldif'.  Error: 65280. 
>> Output:
> importing data ...
>> [25/Sep/2012:11:50:56 +0000] - mkdir_p /var/lib/dirsrv/slapd-kolab: error
> -5966 (Access Denied.)
>> [25/Sep/2012:11:50:56 +0000] - Can't start because the database directory
> "/var/lib/dirsrv/slapd-kolab/db" either doesn't exist, or is not
> accessible
>> [25/Sep/2012:11:50:56 +0000] - ERROR: Failed to init database (error -1:
> Unknown error: -1)
>> 
>> Error: Could not create directory server instance 'kolab'.
>> Exiting . . .
>> Log file is '/tmp/setupIdMLnz.log'
> 
> '/tmp/ldifUN9JLt.ldif' does not exist and 'ls -la /var/lib/dirsrv/' gives
>>drwxrwx---  5 nobody nobody 4096 Sep 25 11:50 slapd-kolab

The magic incantation to overcome this particular hurdle was:
PROMPT> addgroup nobody
PROMPT> adduser nobody nobody
PROMPT> chown -R nobody:nobody /var/lib/dirsrv/

Shoudl I file a bugreport against setup-kolab/pykolab requesting a ownership 
test of /var/lib/dirsrv/ before changing the user to "nobody"?

Sincerely, Joh
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.