Problem upgrading kolab 2.04 to 2.1

Sylvain MEDEOT symedeot at yahoo.fr
Thu Oct 18 12:53:21 CEST 2007


Hi,

I had some problems with my kolab version 2.04 (see thread "Problem with mail structure
from messages) so I decided to test kolab upgrade to 2.1.0.

To so so, I transfered a copy of my kolab 2.04 in a xen domu. It works ok, kolab is
running right. I stopped kolab and decided to start the upgrade following carefully the
instructions in UPGRADING.20-21

It works ok until I run the command kolabconf after having done :

 /kolab/bin/openpkg rc openldap start

I get the following :

kolabconf - Kolab Configuration Generator

  Version: 2.1.0

  Copyright (c) 2004  Klaraelvdalens Datakonsult AB
  Copyright (c) 2003  Code Fusion cc
  Copyright (c) 2003  Tassilo Erlewein, Martin Konold, Achim Frank, erfrakon

This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Error loading configuration. Maybe the LDAP server is not running. Please check the system
log for errors.

I stopped slapd and started it again in debug mode with :

/kolab/libexec/openldap/slapd -h 'ldaps:// ldap://' -d 256

Then I get this when running kolabconf...

conn=4 fd=15 ACCEPT from IP=127.0.0.1:43328 (IP=0.0.0.0:389)
bind: invalid dn (cn=manager,@@@kolab_basedn@@@)
conn=4 op=0 RESULT tag=97 err=34 text=invalid DN
do_search: invalid dn (k=kolab,@@@kolab_basedn@@@)
conn=4 op=1 SEARCH RESULT tag=101 err=34 nentries=0 text=invalid DN
conn=4 op=2 UNBIND
conn=4 fd=15 closed
conn=5 fd=15 ACCEPT from IP=127.0.0.1:43329 (IP=0.0.0.0:389)
do_search: invalid dn (k=kolab,)
conn=5 op=0 SEARCH RESULT tag=101 err=34 nentries=0 text=invalid DN
conn=5 op=1 UNBIND
conn=5 fd=15 closed

So the informations seems not to be merged...

Running nmap on eth0

PORT   STATE SERVICE
22/tcp open  ssh

Running nmap -sS 127.0.0.1

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-10-18 11:42 UTC
Interesting ports on localhost (127.0.0.1):
Not shown: 1678 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
389/tcp open  ldap

and what is strange to me is that only listening on 127.0.0.1.
The file /kolab/var/openldap/slapd.args contains :

/kolab/libexec/openldap/slapd -h ldap://127.0.0.1:389/

How can I tell kolab to run slapd listening on all interfaces (which seems to be the
default usually) ?

I can make lookups successfully on openldap...

conn=0 fd=14 ACCEPT from IP=192.168.200.5:45427 (IP=0.0.0.0:389)
conn=0 op=0 BIND dn="cn=manager,cn=internal,dc=mydomain,dc=fr" method=128
conn=0 op=0 BIND dn="cn=manager,cn=internal,dc=mydomain,dc=fr" mech=SIMPLE ssf=0
conn=0 op=0 RESULT tag=97 err=0 text=
conn=0 op=1 SRCH base="dc=mydomain,dc=fr" scope=2 deref=0 filter="(cn=*)"
conn=0 op=1 SRCH attr=cn sn mail
conn=0 op=1 SEARCH RESULT tag=101 err=0 nentries=315 text=
conn=0 op=2 BIND anonymous mech=implicit ssf=0
conn=0 op=2 BIND dn="cn=manager,cn=internal,dc=mydomain,dc=fr" method=128
conn=0 op=2 BIND dn="cn=manager,cn=internal,dc=mydomain,dc=fr" mech=SIMPLE ssf=0
conn=0 op=2 RESULT tag=97 err=0 text=
conn=0 op=3 SRCH base="dc=mydomain,dc=fr" scope=2 deref=0 filter="(cn=ls*)"
conn=0 op=3 SRCH attr=cn dn member
conn=0 op=3 SEARCH RESULT tag=101 err=0 nentries=34 text=
conn=0 op=4 UNBIND
conn=0 fd=14 closed

Does somebody can point me on what can be wrong with kolabconf ?

Regards,

Sylvain




More information about the users mailing list