Re: Kolab 3.0 on Debian Wheezy: More Issues

Jeroen van Meeuwen <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab,gmane.comp.kde.kolab.devel
Message-ID <[email protected]>
On Thursday, September 27, 2012 02:25:10 PM Johannes Graumann wrote:
> Hi,
> 
> Jeroen van Meeuwen wrote:
> > On Wednesday, September 26, 2012 04:26:31 PM Johannes Graumann wrote:
> >> Hello,
> >> 
> >> Please find attached the output of my most recent attempt to run
> >> PROMPT> setup-kolab --yes -d 9|tee setup-kolab.log
> >> 
> >> Here are my comments:
> >> 1) The '--yes' argument to "setup-kolab" (see "--help") seems broken -
> >> the program keeps asking for passwords and verification of domain names,
> >> etc. Can you reproduce this? Should I report this as a bug against
> >> pykolab/setup- kolab?
> > 
> > --yes should only work for yes/no questions (or
> > pykolab.utils.ask_confirmation()). I reckon it doesn't work for the domain
> > / root_dn questions, which should be relatively easy to fix.
> 
> For the kind of testing I'm doing it would really be helpfull to have an
> additional switch to just blow through the script accepting all the default
> strings
> 

Running setup-kolab with -c /path/to/config does serve part of this, as long 
as /path/to/config is not the default /etc/kolab/kolab.conf.

It'll take primary_domain, base_dn, admin, cn=Directory Manager and service 
passwords, but not for example MySQL root/kolab/roundcube passwords.

I suppose what we want is something of;

  # setup-kolab --accept-defaults --yes

> >> 2) Line 1-4, 6-9, 445-456
> >> 
> >> > Could not change the ownership of log file /var/log/kolab/pykolab.log
> >> 
> >> I have run
> >> PROMPT> mkdir /var/log/kolab/ && touch /var/log/kolab/pykolab.log &&
> >> chmod - R 777/var/log/kolab/
> >> to try and remedy this - to no avail. How crucial is it and what user
> >> actually is trying to execute the 'chown'?
> > 
> > We have an existing bug:
> >   https://bugzilla.kolabsys.com/show_bug.cgi?id=1037
> > 
> > The directory is supposed to be owned by the kolab user that Kolab daemons
> > set their uid/gid to when started by root.
> > 
> > setup-kolab though starts as root, and does not set its ruid/rgid to
> > kolab:kolab, and so attempts to correct the ownership of the log file
> > /var/log/kolab/pykolab.log to the kolab:kolab user/group.
> 
> So why the error? Because at this stage kolab/kolab don't exist yet?
> 

I reckon the debian package indeed does not create the kolab user nor the 
kolab group.

I think I have fixed it in a new pykolab package (0.5.5-2).

> >> 4) Line 422
> >> 
> >> > 2012-09-26 13:02:41,479 pykolab.setup WARNING Could not find the Kolab
> >> > schema file
> >> 
> >> This seems serious and may cause the ultimate error below (7)). Note that
> >> in the development wheezy repository kolab is not directly dependent on
> >> kolab- schema, which has to be manually pulled in (I filed a bug for
> >> that) - may that be related?
> > 
> > It is serious, and indeed causes 7).
> > 
> >> 5) Line 423
> >> 
> >> > 2012-09-26 13:02:41,479 pykolab.setup ERROR Could not start and
> >> > configure to start on boot, the directory server service.
> >> 
> >> Also potentially bad. What is it actually trying to/supposed to do? What
> >> file to edit?
> > 
> > At this part of the routine the necessary "service dirsrv restart" and
> > "chkconfig dirsrv on" equivalent should be executed. Near line ~286 of
> > pykolab/setup/setup_ldap.py is where this happens.
> 
> https://issues.kolab.org/show_bug.cgi?id=1052 with a proposed patch ...
> 

A git format-patch would greatly help, if you feel like cloning the 
repository[1] - together with comment #2 from Torsten.

[1] http://git.kolab.org/pykolab

> >> 6) Line 457
> >> 
> >> > 2012-09-26 13:02:57,324 pykolab.auth WARNING Python LDAP library does
> >> > not support persistent search
> >> 
> >> Is this significant?
> > 
> > It is somewhat significant - what version of python-ldap is installed?
> 
> The installed version is 2.4.10-1.
> 

That should just support persistent search, but regrettably Debian does not 
ship pyasn1_modules (which is required). Logged as #1057, #1058.

Kind regards,

Jeroen van Meeuwen

--
Systems Architect

Kolab Systems AG
Zürich, Switzerland

e: [email protected]
t: +41 43 501 66 91
m: +44 74 2516 3817
w: http://kolabsys.com

pgp: 0x9342BF08

_______________________________________________
Kolab-devel mailing list
[email protected]
https://www.intevation.de/mailman/listinfo/kolab-devel
signature.asc (application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEABECAAYFAlBlpOwACgkQKN6f2pNCvwjvjgCfcXFrvF0W/l7TIvB/CFIeU+6a
c70An29ZwB6dwbZWuXnbFmoV9V+Z+0wm
=7Y3P
-----END PGP SIGNATURE-----
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.