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

[Jeroen van Meeuwen]

On Tuesday, September 25, 2012 09:37:09 PM 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.
> 

Right - that may resolve the issue for your deployment but it will still fail 
on a standard Debian installation (permission errors), which we can't sensibly 
change through packaging or application fixes.

So, I was shipping a patch in the Debian packages for pykolab, that would 
cause setup-kolab to use 'setup-ds' rather than 'setup-ds-admin', but Paul 
decided to drop it (#1040[1], [2])

[1] https://bugzilla.kolabsys.com/show_bug.cgi?id=1040
[2] 
http://git.kolabsys.com/apt/pykolab/commit/?id=ed1370beb1024261fdcb2d6e97c97e186daac863

> 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
> 

I reckon the default user/group account for the directory server was patched 
(in the debian packaging) to be 'dirsrv', not 'nobody'.

Kind regards,

Jeroen van Meeuwen

--
Systems Architect

Kolab Systems AG
Zürich, Switzerland

e: vanmeeuwen at kolabsys.com
t: +41 43 501 66 91
m: +44 74 2516 3817
w: http://kolabsys.com

pgp: 0x9342BF08
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20120926/980c87aa/attachment.sig>