• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Was anybody able to setup Kolab 16 under Plesk 12.5 on Centos 7???

Now i had time to try and to make sure that there is as less missconfiguration from default i started from scratch.
- fresh install of the vserver
- installed mariadb 10.1.4
- installed plesk, letsencrypt addon, made my subdomain kolab.domain.de and generated a letsencrypt certificate
- installed
yum install make plesk-php56-devel gcc glibc-devel libmemcached- devel zlib-devel
/opt/plesk/php/5.6/bin/pecl install raphf-1.1.2
gives following warning(s)
Code:
     WARNING: php_bin /opt/plesk/php/5.6/bin/php appears to have a suffix /5.6/bin/ph p, but config variable php_suffix does not match

     configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.


/opt/plesk/php/5.6/bin/pecl install propro-1.0.2
gives following warning(s)
Code:
     WARNING: php_bin /opt/plesk/php/5.6/bin/php appears to have a suffix /5.6/bin/ph p, but config variable php_suffix does not match

     configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.


added to php.ini in plesk so that the modules in the right order
;;;;;;;;;;;;;;;;;;;;;;
; Dynamic Extensions ;
;;;;;;;;;;;;;;;;;;;;;;
extension=raphf.so
extension=propro.so
extension=http.so

/opt/plesk/php/5.6/bin/pecl install pecl_http-2.5.6
gives following warning(s)
Code:
     WARNING: php_bin /opt/plesk/php/5.6/bin/php appears to have a suffix /5.6/bin/ph p, but config variable php_suffix does not match

     configure: WARNING: You will need re2c 0.13.4 or later if you want to regenerate PHP parsers.

     configure: WARNING: continuing without libevent support

- installed /opt/plesk/php/5.6/bin/pear remote-info HTTP_Request2
- installed kolab
gives following error
Code:
  ERROR: SQLSTATE[HY000] [1045] Access denied for user 'roundcube'@'localhost' (using password: YES)Error 500: Error connecting to database: SQLSTATE[HY000] [1045 ] Access denied for user 'roundcube'@'localhost' (using password: YES)


- setup-kolab

In the setup process, there is the following part in which i choosed the given user and group. This might be wrong for setup under Plesk?!
Code:
Please choose the system user and group the service should use to run under.
These should be existing, unprivileged, local system POSIX accounts with no
shell.

User [nobody]:
Group [nobody]:


The last part of the setup process gives the following output:
Code:
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
Removed symlink /etc/systemd/system/multi-user.target.wants/saslauthd.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/kolab-saslauthd .service to /usr/lib/systemd/system/kolab-saslauthd.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/cyrus-imapd.ser vice to /usr/lib/systemd/system/cyrus-imapd.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/kolabd.service to /usr/lib/systemd/system/kolabd.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/mongod.service to /usr/lib/systemd/system/mongod.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/manticore.servi ce to /usr/lib/systemd/system/manticore.service.

and journalctl -xe shows the following
Code:
[error] CRASH REPORT Process <0.88.0> with 0 neighbours exited with reason: no match of right hand value {error,eaddrinuse} in kolab_guam_listener:init/1 line 44 in gen
[error] Supervisor kolab_guam_sup had child imap started with kolab_guam_listener:start_link(imap, [{port,143},{imap_server,imaps},{rules,[{filter_groupware,[]}]},{tls_
[error] CRASH REPORT Process <0.85.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,imap,{{badmatch,{error,eaddrinuse}},[{kolab_guam_listener,
{"Kernel pid terminated",application_controller,"{application_start_failure,kolab_guam,{{shutdown,{failed_to_start_child,imap,{{badmatch,{error,eaddrinuse}},[{kolab_guam_listener,in
Crash dump was written to: erl_crash.dump
Kernel pid terminated (application_controller) ({application_start_failure,kolab_guam,{{shutdown,{failed_to_start_child,imap,{{badmatch,{error,eaddrinuse}},[{kolab_guam_listener,ini
Exec: /opt/kolab_guam/erts-6.3/bin/erlexec  -noinput +Bd -boot /opt/kolab_guam/releases/0.7.2/kolab_guam -config /opt/kolab_guam/releases/0.7.2/sys.config -args_file /opt/kolab_guam
Root: /opt/kolab_guam

:(
 
Hi saschadd,

again, I would like to point to the fact, that this forum is for "Plesk related" - subjects... the forum users may still suggest, or inform you about non-related Plesk issues/problems/errors, but it will be really hard to get help for unique, third party components issues/problems/errors, especially, if the components are not tested for Plesk usage. Consider to use bug-trackers from the third party component supplier, if you experience issues with your thir party components.

 
Back
Top