Error installing Kolab on Centos 6.2
Javier Romero
xavinux at gmail.com
Wed Jul 25 16:42:56 CEST 2012
*Dear Sir:*
Thanks for your answer.
I´ve run the setup again with the -d 9 option and these are the results:
=======================================================================
*setup-kolab -d 9
WARNING: The Fully Qualified Domain Name or FQDN for this system is
incorrect. Falling back to 'localdomain'.
2012-07-25 11:04:47,005 pykolab.setup DEBUG [1877]: No component selected,
continuing for all components
2012-07-25 11:04:47,031 pykolab.conf DEBUG [1877]: Setting
kolab_default_locale to 'en_US' (from defaults)
2012-07-25 11:04:47,032 pykolab.conf DEBUG [1877]: Setting mail_attributes
to ['mail', 'alias'] (from defaults)
2012-07-25 11:04:47,032 pykolab.conf DEBUG [1877]: Setting
mailserver_attribute to 'mailhost' (from defaults)
2012-07-25 11:04:47,032 pykolab.conf DEBUG [1877]: Setting loglevel to 50
(from defaults)
2012-07-25 11:04:47,033 pykolab.conf DEBUG [1877]: Setting
imap_virtual_domains to 'userid' (from defaults)
2012-07-25 11:04:47,033 pykolab.conf DEBUG [1877]: Setting
cyrus_annotations_retry_interval to 1 (from defaults)
2012-07-25 11:04:47,033 pykolab.conf DEBUG [1877]: Setting
ldap_unique_attribute to 'nsuniqueid' (from defaults)
2012-07-25 11:04:47,033 pykolab.conf DEBUG [1877]: Setting
address_search_attrs to ['mail', 'alias'] (from defaults)
2012-07-25 11:04:47,034 pykolab.conf DEBUG [1877]: Setting config_file to
'/etc/kolab/kolab.conf' (from the default values for CLI options)
2012-07-25 11:04:47,034 pykolab.conf DEBUG [1877]: Setting loglevel to
'CRITICAL' (from the default values for CLI options)
2012-07-25 11:04:47,034 pykolab.conf DEBUG [1877]: Setting answer_yes to
False (from the default values for CLI options)
2012-07-25 11:04:47,035 pykolab.conf DEBUG [1877]: Setting quiet to False
(from the default values for CLI options)
2012-07-25 11:04:47,035 pykolab.conf DEBUG [1877]: Setting fqdn to
'hostname' (from the default values for CLI options)
2012-07-25 11:04:47,035 pykolab.conf DEBUG [1877]: Setting debuglevel to 0
(from the default values for CLI options)
2012-07-25 11:04:47,035 pykolab.conf DEBUG [1877]: Setting logfile to
'/var/log/kolabd/kolabd.log' (from the default values for CLI options)
2012-07-25 11:04:47,036 pykolab.conf DEBUG [1877]: Setting options from
configuration file
2012-07-25 11:04:47,039 pykolab.conf DEBUG [1877]: Reading configuration
file /etc/kolab/kolab.conf
2012-07-25 11:04:47,046 pykolab.conf DEBUG [1877]: Setting config_file to
'/etc/kolab/kolab.conf' (from CLI, verified)
2012-07-25 11:04:47,046 pykolab.conf DEBUG [1877]: Setting loglevel to
'CRITICAL' (from CLI, not checked)
2012-07-25 11:04:47,047 pykolab.conf DEBUG [1877]: Setting answer_yes to
False (from CLI, not checked)
2012-07-25 11:04:47,047 pykolab.conf DEBUG [1877]: Setting quiet to False
(from CLI, not checked)
2012-07-25 11:04:47,047 pykolab.conf DEBUG [1877]: Setting fqdn to
'hostname' (from CLI, not checked)
2012-07-25 11:04:47,048 pykolab.conf DEBUG [1877]: Setting debuglevel to 9
(from CLI, verified)
2012-07-25 11:04:47,048 pykolab.conf DEBUG [1877]: Setting logfile to
'/var/log/kolabd/kolabd.log' (from CLI, not checked)
Please supply a password for the LDAP administrator user 'admin', used to
login
to the graphical console of 389 Directory server.
Administrator password []:
Confirm Administrator password:
Please supply a password for the LDAP Directory Manager user, which is the
administrator user you will be using to at least initially log in to the Web
Admin, and that Kolab uses to perform administrative tasks.
Directory Manager password []:
Confirm Directory Manager password:
User [nobody]: username
Group [nobody]: groupname
This setup procedure plans to set up Kolab Groupware for the following
domain
name space. This domain name is obtained from the reverse DNS entry on your
network interface. Please confirm this is the appropriate domain name space.
[Y/n]: Y
The standard root dn we composed for you follows. Please confirm this is
the root
dn you wish to use.
dc= [Y/n]: Y
2012-07-25 11:05:06,136 pykolab.setup INFO Setting up 389 Directory Server
2012-07-25 11:05:06,635 pykolab.setup DEBUG [1877]: Setup DS stdout:
2012-07-25 11:05:06,635 pykolab.setup DEBUG [1877]: Creating directory
server . . .
The port number '389' is not available for use. This may be due to an
invalid port number, or the port already being in use by another
program, or low port restriction. Please choose another value for
ServerPort. Error: $!
Error: Could not create directory server instance 'hostname'.
Exiting . . .
Log file is '/tmp/setupDIZhXS.log'
2012-07-25 11:05:06,636 pykolab.setup DEBUG [1877]: Setup DS stderr:
2012-07-25 11:05:06,636 pykolab.setup DEBUG [1877]:
Shutting down dirsrv:
hostname... [ OK ]
Starting dirsrv:
hostname... [ OK ]*
=======================================================================
And this is my iptables configuration as given in the tutorial I follow:
==================================================
*# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 25 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 110 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 143 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 465 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 587 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 636 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 993 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 995 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT*
====================================================
Ports requiered have been opened in the Firewall.
No other progrma is using port *389
*Still can´t make LDAP protocol work correctly with Kolab on my Centos 6.2
Thanks again for your help Sir.
Best regards,
Xavi
2012/7/25 Jeroen van Meeuwen <vanmeeuwen at kolabsys.com>
> **
>
> On Tuesday, July 24, 2012 03:26:36 PM Javier Romero wrote:
>
> > Dear Sirs:
>
> > I receive an error when trying to install Kolab on a Centos 6 Server.
>
> > When I run the "setup-kolab" command and after giving all Passwords
>
> > required and domain name for configuration, this error appears:
>
> >
>
> > IOError: [Errno 2] No such file or directory:
>
> > '/etc/dirsrv/slapd-hostname/schema/99kolab2.ldif'
>
> >
>
>
>
> This seems to indicate the setup of the LDAP directory server failed.
>
>
>
> You can run setup-kolab with -d 9 to get more verbose errors.
>
>
>
> Kind regards,
>
>
>
> Jeroen van Meeuwen
>
>
>
> --
>
> Systems Architect, Kolab Systems AG
>
>
>
> e: vanmeeuwen at kolabsys.com
>
> m: +44 74 2516 3817
>
> w: http://www.kolabsys.com
>
>
>
> pgp: 9342 BF08
>
--
*http://www.porloschicos.com/*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20120725/79c67c8d/attachment.html>
More information about the users
mailing list