Re: [Kolab-devel] Fresh Kolab 3.2 installation on CentOS 6.5

Thomas Reitelbach <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab
Message-ID <[email protected]>
NeXuS <nexus_network23 <at> web.de> writes:

> 
> 
> Hello,
> Install fresh CentOS 6.5 minimal
> changed selinux and iptables settings and get repos for Kolab 3.2.
> first call from setup-kolab says:
> pykolab.conf ERROR Could not change permissions on 
> /var/log/kolab/pykolab.log: OSERROR(2, 'No such file or directory')
> break execution with STRG+C
> If you don't break the setup prozess than you ran into follwing error 
> and this breaks the complete installation:
> kolab-saslauthd starten: Traceback (most recent call last): File 
> "/usr/lib/python2.6/site-packages/saslauthd/__init__.py", line 194, in 
> run self.do_saslauthd() File 
> "/usr/lib/python2.6/site-packages/saslauthd/__init__.py", line 244, in 
> do_saslauthd s.bind('/var/run/saslauthd/mux') File "<string>", line 1, 
> in bind error: [Errno 13] Permission denied
> second call from setup-kolab don't show the error again.
> After installation amavisd.conf file is empty. amavisd beenden und 
> starten FEHLGESCHLAGEN
> drop_priv: No such username:
> httpd/error.log
> PHP Warning: Module 'kolabformat' already loaded in Unknown on line 0
> PHP Notice: Constant swig_runtime_data_type_pointer already in Unknown 
> on line 0
> Created new user can login into roundcube but has no existing Mailbox.
> The other logfiles show nothing.
> Any ideas?

No idea, but i can confirm that i run into the same problem.

The first warning does not seem harmful, since the logfile is created and
exists afterwards (pykolab.conf ERROR Could not change permissions on 
> /var/log/kolab/pykolab.log: OSERROR(2, 'No such file or directory'))

The amavisd message is a problem, after "setup-kolab" the amavisd.conf is
empty, which prevents amavis from starting.

Any ideas how to solve this?

Cheers
Thomas
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.