I attempted to run an upgrade from kolabd-20070216-r3 to kolabd-2.1. This pulled in openldap-2.3.35 which was previously repository masked. Once merged, I did an etc-update to bring in any new config files, but stupidly, I restarted slapd before running kolabconf. Consequently slapd would not start and kolabconf would not run. I restored my old openldap configs, but the 2.3.35 version of slapd still would not start with these.
I have another kolab server and I only upgrade one at a time so I always have a reference machine that is working in case I run into trouble. I copied the kolab2 repository from it so that I could revert to the kolabd-20070510 build which had an rdepend of >=openldap-2.3.30. This way I could downgrade openldap. With my restored config files, the 2.3.30-r2 version of slapd would start, but kolabconf still fails. My server components seem to be operating after some config file restoration (resmgr, etc.), but I can't do a kolabconf.
Here is the error I get in /var/log/messages:
Jul 5 07:29:21 mainsrv kolabconf: C Error: Unable to bind to DN `cn=manager,@@@kolab_basedn@@@'
Jul 5 07:29:21 mainsrv kolabconf: C Error: Unable to find kolab object `k=kolab,@@@kolab_basedn@@@'
Here is the output of kolabconf -d (This looks very wrong):
base_dn : @@@kolab_basedn@@@
bind_dn : cn=manager,@@@kolab_basedn@@@
bind_pw : @@@kolab_passwd@@@
bind_pw_hash : {SSHA}dSsQI5tJDkIiR9+PzXzusyZ4XmEWN/yS
conn_refresh_period : 60
cyrus-admins : manager
cyrus-autocreatequota : 100000
cyrus-imap : TRUE
cyrus-imaps : TRUE
cyrus-pop3 : FALSE
cyrus-pop3s : TRUE
cyrus-sieve : TRUE
cyrus_admin : manager
cyrus_admin_pw : @@@kolab_passwd@@@
debug : 0
directory_mode : slurpd
dirserv_home_server : mainsrv
dirserv_mailbox_password :
dirserv_mailbox_server :
dirserv_mailbox_user :
dirserv_poll_period : 120
fqdn : mainsrv
fqdnhostname : @@@fqdnhostname@@@
group_bind_dn : cn=manager,@@@kolab_basedn@@@
group_bind_pw : @@@kolab_passwd@@@
group_directory_mode : slurpd
group_dn_list : @@@kolab_basedn@@@
group_field_deleted : kolabdeleteflag
group_field_guid : entryUUID
group_field_modified : modifytimestamp
group_ldap_ip : 127.0.0.1
group_ldap_port : 389
group_ldap_uri : ldap://127.0.0.1:389
group_object_class : kolabgroupofnames
gyard_deletion_period : 10080
is_master : @@@is_master@@@
kolab_dn : k=kolab,@@@kolab_basedn@@@
kolab_gid : 441
kolab_n_gid : 443
kolab_n_uid : 109
kolab_r_gid : 442
kolab_r_uid : 108
kolab_uid : 107
ldap_ip : 127.0.0.1
ldap_master_uri : @@@ldap_master_uri@@@
ldap_port : 389
ldap_uri : ldap://127.0.0.1:389
log_level : 2
maildefer_header :
maildefer_listen : 127.0.0.1:10024
maildefer_size :
maildefer_talk : 127.0.0.1:10025
php_dn : cn=nobody,@@@kolab_basedn@@@
php_pw : @@@nobody_pw@@@
postfix-mydestination : $mydomain
prefix : /
proftpd-ftp : FALSE
proftpd-userPassword :
sf_bind_dn : cn=manager,@@@kolab_basedn@@@
sf_bind_pw : @@@kolab_passwd@@@
sf_directory_mode : slurpd
sf_dn_list : @@@kolab_basedn@@@
sf_field_deleted : kolabdeleteflag
sf_field_guid : entryUUID
sf_field_modified : modifytimestamp
sf_field_quota : cyrus-userquota
sf_ldap_ip : 127.0.0.1
sf_ldap_port : 389
sf_ldap_uri : ldap://127.0.0.1:389
sf_object_class : kolabsharedfolder
slurpd_accept_addr : 127.0.0.1
slurpd_addr : 127.0.0.1
slurpd_port : 9999
uid : freebusy
userPassword : freebusy
user_bind_dn : cn=manager,@@@kolab_basedn@@@
user_bind_pw : @@@kolab_passwd@@@
user_directory_mode : slurpd
user_dn_list : @@@kolab_basedn@@@
user_field_deleted : kolabdeleteflag
user_field_guid : entryUUID
user_field_modified : modifytimestamp
user_field_quota : cyrus-userquota
user_ldap_ip : 127.0.0.1
user_ldap_port : 389
user_ldap_uri : ldap://127.0.0.1:389
user_object_class : inetOrgPerson
Any suggestions of where to go from here are welcome.
Thanks,
Jason
