probs with cyrmaster process

[suffocator at gmx.de]

Hi list,

another log entry:

If I try to start imapd standalone (execute /kolab/etc/rc imapd start as
root),
I get the following in /kolab/var/imapd/log/master.log:

Apr 11 11:28:35 niobe.matrix.com <error> master[24687]: setrlimit: Unable to
set file descriptors limit to -1: (1) Operation not permitted
Apr 11 11:28:35 niobe.matrix.com <error> master[24687]: retrying with 1024
(current max)
Apr 11 11:28:35 niobe.matrix.com <notice> master[24687]: process started
Apr 11 11:28:35 niobe.matrix.com <debug> master[24692]: about to exec
/kolab/bin/ctl_cyrusdb
Apr 11 11:28:35 niobe.matrix.com <error> master[24687]: process 24692
exited, status 75
Apr 11 11:28:35 niobe.matrix.com <notice> master[24687]: ready for work
Apr 11 11:28:35 niobe.matrix.com <debug> master[24697]: about to exec
/kolab/bin/tls_prune
Apr 11 11:28:35 niobe.matrix.com <debug> master[24698]: about to exec
/kolab/bin/ctl_deliver
Apr 11 11:28:35 niobe.matrix.com <debug> master[24699]: about to exec
/kolab/bin/ctl_cyrusdb
Apr 11 11:28:35 niobe.matrix.com <debug> master[24687]: process 24697
exited, status 1
Apr 11 11:28:35 niobe.matrix.com <debug> master[24687]: process 24698
exited, status 75
Apr 11 11:28:35 niobe.matrix.com <debug> master[24687]: process 24699
exited, status 1

The error mentioned before occurs directly after a fresh install (box from
scratch), here's
the kolab bootstrap log:

[root at niobe zfos]# /kolab/etc/kolab/kolab_bootstrap -b

KOLAB BOOTSTRAP

Please enter Hostname [niobe.matrix.com]:
proceeding with Hostname niobe.matrix.com
Please enter your Maildomain [matrix.com]:
proceeding with Maildomain matrix.com
Generating default configuration:
 base_dn : dc=niobe,dc=matrix,dc=com
 bind_dn : cn=manager,dc=niobe,dc=matrix,dc=com
Please choose a manager password [rax9BeSPcp9aA]:admin
 bind_pw : admin
done modifying /kolab/etc/kolab/kolab.conf

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

prepare LDAP database...
kill running slapd (if any)
OpenPKG: stop: openldap.
OpenPKG: stop: openldap.
temporarily start slapd
no dc=niobe,dc=matrix,dc=com object found, creating one
no kolab config object in ldap, generating a reasonable default
mynetworkinterfaces: 127.0.0.0/8
LDAP setup finished

Create initial config files for postfix, apache, proftpd, cyrus imap,
saslauthd
 running /kolab/etc/kolab/kolab -v -o -lldap://127.0.0.1:389/
NOTE: USE OF THIS SCRIPT IS DEPRECATED. Please use `/kolab/sbin/kolabconf'
in the future.
kolabconf - Kolab Configuration Generator

  Copyright (c) 2003  Code Fusion cc
  Copyright (c) 2003  Tassilo Erlewein, Martin Konold, Achim Frank

This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
OpenPKG: restart: openldap.
OpenPKG: stop: sasl.
/kolab/sbin/apachectl graceful: httpd not running, trying to start
Syntax error on line 25 of /kolab/etc/apache/apache.conf:
SSLCertificateFile: file '/kolab/etc/kolab/cert.pem' not exists or empty
/kolab/sbin/apachectl graceful: httpd could not be started
postfix/postfix-script: fatal: the Postfix mail system is not running
OpenPKG: restart: imapd.
OpenPKG: stop: proftpd.

kill temporary slapd

OpenPKG: stop: openldap.
generate self-signed certificate for hostname niobe.matrix.com... done
New certificate has been installed under /kolab/etc/kolab/
kolab should now be ready to run
please run '/kolab/etc/rc all start'
[root at niobe zfos]# /kolab/etc/rc all start
OpenPKG: start: openldap, sasl, apache, imapd, openpkg, postfix, proftpd
OpenPKG: start: kolab.

Does anybody know why imapd dies and starts again all the time?

Thanks in advance,

Magnus

-- 
support our band!!!
visit http://www.humanbastard.de

support the search for extraterrestrial intelligence!
visit http://setiathome.berkeley.edu

NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/info