Kolab auf SuSE 10.3 erfolgreich installiert - was nun?

Check that the request matches the signature
Signature ok
Certificate Details:
        Serial Number: 1 (0x1)
        Validity
            Not Before: Nov  8 19:32:39 2007 GMT
            Not After : Nov  5 19:32:39 2017 GMT
        Subject:
            commonName                = p667.homelinux.local
        X509v3 extensions:
            X509v3 Basic Constraints:
                CA:FALSE
            Netscape Comment:
                OpenSSL Generated Certificate
            X509v3 Subject Key Identifier:
                2D:84:F5:50:82:20:44:3F:34:83:48:4B:45:48:20:B8:C8:7A:A2:05
            X509v3 Authority Key Identifier:
                DirName:/O=Kolab/OU=Test-CA/CN=p667.homelinux.local
                serial:A7:72:66:85:7E:90:2F:41

Certificate is to be certified until Nov  5 19:32:39 2017 GMT (3650 days)
Sign the certificate? [y/n]:y


1 out of 1 certificate requests certified, commit? [y/n]y
Write out database with 1 new entries
Data Base Updated
Signed certificate is in /etc/kolab/cert.pem
/home/dm
chgrp pki /etc/kolab/key.pem;
chmod 0640 /etc/kolab/key.pem;
chgrp pki /etc/kolab/cert.pem;
chmod 0640 /etc/kolab/cert.pem;
################################################################################
CA and certificate creation complete.

You can install /etc/kolab/ca/cacert.pem on your clients to allow them
to verify the validity of your server certificates.

kolab is now ready to run!
please run '/usr/sbin/kolabsrv rc all start'
Use login=manager and passwd=xxxxxxxxxxxxxxxx when you log into
the webinterface https://p667.homelinux.local/kolab/admin !
p667:/home/dm #
p667:/home/dm # /usr/sbin/kolabsrv rc all start
Starting ldap-server                                                  done
Starting slurpd                                                       done
Starting service saslauthd                                            done
Starting spamd                                                        done
Starting virus-scanner (amavisd-new):                                 done
Check the APACHE_MODULES setting in /etc/sysconfig/apache2.
Apache is already running (/var/run/httpd2.pid)                       done
Starting Clam AntiVirus database update daemon                        done
Starting Clam AntiVirus daemon                                        done
Starting IMAP/POP3 service (cyrus-imapd)                              done
Starting mail service (Postfix)                                       done
Starting kolab groupware server                                       done
p667:/home/

dm@p667:~> cd /srv/www/htdocs/
dm@p667:/srv/www/htdocs> ls -l |grep kolab
drwxr-xr-x  4 root   root   4096 2007-11-08 18:31 kolab

dm@p667:/srv/www/htdocs> cd /srv/www/htdocs/kolab
dm@p667:/srv/www/htdocs/kolab> ls -l
total 12
drwxr-xr-x 12 root root 4096 2007-11-08 18:30 admin
-rw-r--r--  1 root root 1406 2007-11-07 15:57 favicon.ico
drwxr-xr-x  3 root root 4096 2007-11-08 20:14 freebusy
dm@p667:/srv/www/htdocs/kolab> cd /srv/www/htdocs/kolab/admin
dm@p667:/srv/www/htdocs/kolab/admin> ls -l
total 56
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 addressbook
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 administrator
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 distributionlist
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 domainmaintainer
-rw-r--r-- 1 root root 2326 2007-11-07 15:58 index.php
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 kolab
-rw-r--r-- 1 root root  995 2007-11-07 15:58 logout.php
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 maintainer
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 pics
-rw-r--r-- 1 root root  478 2007-11-07 15:58 print.css
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 service
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 sharedfolder
-rw-r--r-- 1 root root 3321 2007-11-07 15:58 style.css
drwxr-xr-x 2 root root 4096 2007-11-08 18:30 user
dm@p667:/srv/www/htdocs/kolab/admin>

An error occurred while loading https://p667.homelinux.local/kolab/admin:
Could not connect to host p667.homelinux.local.

p667:/home/dm # tail -f /var/log/apache2/error.log
tail: cannot open `/var/log/apache2/error.log' for reading: No such file or directory
tail: no files remaining
p667:/home/dm #

xy.homelinux.bla

homelinux.local

http://xy.homelinux.bla/kolab/admin

[Fri Nov 09 19:06:40 2007] [error] [client 127.0.0.2] access to /srv/www/htdocs/kolab/admin failed, reason: SSL connection required

p667:/home/dm # /usr/share/kolab/scripts/kolab_bootstrap -b

KOLAB BOOTSTRAP

Check for running webserver on port 80
Check for running webserver on port 443
Check for running imap server on port 143
Check for running imap server on port 220
Check for running imap server on port 585
Check for running imap server on port 993
Check for running pop3 server on port 109
Check for running pop3 server on port 110
Check for running pop3 server on port 473
Check for running pop3 server on port 995
Check for running smtp server on port 25
Check for running smtp server on port 465
Check for running ftp server on port 21
Check for running Amavis Virus Scanner Interface on port 10024
Check for running Kolab daemon on port 9999
Check for running OpenLDAP server on port 636
Check for running OpenLDAP server on port 389
Check for running Sieve server on port 2000
Excellent all required Ports are available!

Found existing configuration

Bootstrapping Kolab will overwrite old configuration

Continue [n] (y/n): y
Creating backup of old configuration (LDAP, kolab.conf and certificates)
creating backup of LDAP repository
creating backup of CA data
Cleaning up LDAP
Please enter Hostname including Domain Name (e.g. thishost.domain.tld) [p667.homelinux.local]:
Proceeding with Hostname p667.homelinux.local
Do you want to set up (1) a master Kolab server or (2) a slave [1] (1/2):
Proceeding with master server setup

Please enter your Maildomain - if you do not know your mail domain use the fqdn from above [homelinux.local]:
proceeding with Maildomain homelinux.local
Kolab primary email addresses will be of the type user@homelinux.local
Generating default configuration:
Top level DN for Kolab [dc=homelinux,dc=local]:
 base_dn : dc=homelinux,dc=local
 bind_dn : cn=manager,cn=internal,dc=homelinux,dc=local
Please choose a manager password [aDCBZmLBr9uz6fkO]:
 bind_pw : aDCBZmLBr9uz6fkO
done modifying /etc/kolab/kolab.conf

IMPORTANT NOTE:
use login=manager and passwd=aDCBZmLBr9uz6fkO when you log into the webinterface!

Enter fully qualified hostname of slave kolab server e.g. thishost.domain.tld [empty when done]:
prepare LDAP database...
temporarily starting slapd
chown: cannot access `/var/lib/ldap/*': No such file or directory
Waiting for OpenLDAP to start
no dc=homelinux,dc=local object found, creating one
mynetworkinterfaces: 127.0.0.0/8
LDAP setup finished

Create initial config files for postfix, apache, cyrus imap, saslauthd
running /usr/sbin/kolabconf -n

kill temporary slapd

Shutting down ldap-server                                             done
Creating RSA keypair for resource password encryption
/usr/bin/openssl genrsa -out /etc/kolab/res_priv.pem 1024
Generating RSA private key, 1024 bit long modulus
..........++++++
...............++++++
e is 65537 (0x10001)
/usr/bin/openssl rsa -in /etc/kolab/res_priv.pem -pubout -out /etc/kolab/res_pub.pem
writing RSA key
chown root:root /etc/kolab/res_pub.pem /etc/kolab/res_priv.pem
Kolab can create and manage a certificate authority that can be
used to create SSL certificates for use within the Kolab environment.
You can choose to skip this section if you already have certificates
for the Kolab server.
Do you want to create CA and certificates [y] (y/n):
Now we need to create a cerificate authority (CA) for Kolab and a server
certificate. You will be prompted for a passphrase for the CA.
################################################################################
/usr/share/kolab/scripts/kolab_ca.sh -newca p667.homelinux.local
Enter organization name [Kolab]:
Enter organizational unit [Test-CA]:
Using subject O=Kolab,OU=Test-CA,CN=p667.homelinux.local
Using dn
CA certificate filename (or enter to create)

Making CA certificate ...
Generating a 1024 bit RSA private key
........++++++
.....................++++++
writing new private key to '/etc/kolab/ca/private/cakey.pem'
Enter PEM pass phrase:
Verifying - Enter PEM pass phrase:
-----
/home/dm
/usr/share/kolab/scripts/kolab_ca.sh -newkey p667.homelinux.local /etc/kolab/key.pem
Using dn
Generating RSA private key, 1024 bit long modulus
...................................++++++
..........++++++
e is 65537 (0x10001)
writing RSA key
/home/dm
/usr/share/kolab/scripts/kolab_ca.sh -newreq p667.homelinux.local /etc/kolab/key.pem /etc/kolab/newreq.pem
Using dn
Request is in /etc/kolab/newreq.pem and private key is in /etc/kolab/key.pem
/home/dm
/usr/share/kolab/scripts/kolab_ca.sh -sign /etc/kolab/newreq.pem /etc/kolab/cert.pem
Using dn
Using configuration from /etc/kolab/kolab-ssl.cnf
Enter pass phrase for /etc/kolab/ca/private/cakey.pem:
Check that the request matches the signature
Signature ok
Certificate Details:
        Serial Number: 1 (0x1)
        Validity
            Not Before: Nov  8 19:32:39 2007 GMT
            Not After : Nov  5 19:32:39 2017 GMT
        Subject:
            commonName                = p667.homelinux.local
        X509v3 extensions:
            X509v3 Basic Constraints:
                CA:FALSE
            Netscape Comment:
                OpenSSL Generated Certificate
            X509v3 Subject Key Identifier:
                2D:84:F5:50:82:20:44:3F:34:83:48:4B:45:48:20:B8:C8:7A:A2:05
            X509v3 Authority Key Identifier:
                DirName:/O=Kolab/OU=Test-CA/CN=p667.homelinux.local
                serial:A7:72:66:85:7E:90:2F:41

Certificate is to be certified until Nov  5 19:32:39 2017 GMT (3650 days)
Sign the certificate? [y/n]:y


1 out of 1 certificate requests certified, commit? [y/n]y
Write out database with 1 new entries
Data Base Updated
Signed certificate is in /etc/kolab/cert.pem
/home/dm
chgrp pki /etc/kolab/key.pem;
chmod 0640 /etc/kolab/key.pem;
chgrp pki /etc/kolab/cert.pem;
chmod 0640 /etc/kolab/cert.pem;
################################################################################
CA and certificate creation complete.

You can install /etc/kolab/ca/cacert.pem on your clients to allow them
to verify the validity of your server certificates.

kolab is now ready to run!
please run '/usr/sbin/kolabsrv rc all start'
Use login=manager and passwd=aDCBZmLBr9uz6fkO when you log into
the webinterface https://p667.homelinux.local/kolab/admin !
p667:/home/dm #