Page MenuHomePhorge

Kolab Winterfell Installation bug report on Debian Jessie
Open, NormalPublic


Installed Kollab Winterfell on a Debian Jessie (with kde desktop) and found some problems:
1- guam certificate location on Debian Jessie /etc/guam/sys.config is wrongly configured and all imap operations fail
1.1 - There is NOT
But on Debian Jessie it is at

2 - Misleading messages on setup-kolab
2.1 - Mysql packages are previously installed during " apt-get install kolab " and mysql root password is set up at that point. During setup-kolab, the dialog

What MySQL server are we setting up?

  • 1: Existing MySQL server (with root password already set).
  • 2: New MySQL server (needs to be initialized).

Choice: 1

Is not so clear, and one could proceed first installation with choice 1 causing problems ahead. Maybe , "previously installed kolab and roundcubee databases on mysql server with root password already set"?

3 - One MUST HAVE to install using UTC or weird problems will happen on calendar.
3.1 - Events are created but not shown. Collisions could occur without displaying.
3.2 - A workaround is mannually editing up /etc/php5/apache2/php.ini
3.3 - I do not know collateral effects of this manual edition yet.

4 - web administration interface for creating new users
4.1 It is not alerted on docs that one have to wait up to 10 minutes for ldap synchronization to cyrus mailboxes or new user will not have mailboxes.
4.2 - A work around for immediate syncronization is running "kolab sync" on command line, but is not clearly documentated for newbies.

  1. For some reason, winterfell on Debian shows 4 skins for user choise, and SKIN "KOLAB" without preview will "unrecoverably crash user account" for practical effects, Maybe having to edit ldap and database entries.

5.2 For some reason, winterfell on CentOS 7 only shows valid chamaleon and larry skins.

  1. One of the new Apache modules cause Apache 2.4 on Debian Jessie to enter 100% cpu on RELOAD during installation or uninstallation.

6.1 - You have to stop and start Apache. Or even sigkill. Still not identified the rogue module.

  1. Unable to load emails.

7.1 Kolab winterfell on Debian 8.5 Jessie does not show emails. After clicking on one email, it hangs on "loading" screen until timeout and "internal error".

  1. For uninstallation, it could be documented 8.1 FIRST drop kolab and roundcube databases

mysql --password=your_mysql_root_passwd
mysql> show databases;




5 rows in set (0.00 sec)

mysql> drop database kolab;
mysql> drop database roundcube;
Query OK, 34 rows affected (0.22 sec)

mysql> show databases;




3 rows in set (0.00 sec)

mysql> quit

8.2 to avoid the following next installation dialog
It seems 389 Directory Server has an existing instance configured. This setup
script does not intend to destroy or overwrite your data. Please make sure
/etc/dirsrv/ and /var/lib/dirsrv/ are clean so that this setup does not have to

8.3 One should run the command to clean ldap: -i slapd-$HOSTNAME -a

8.4 to clean mailboxes
kolab list-mailboxes
kolab delete-mailbox "user/"

8.5 THEN remove packages
apt-get -d --purge --auto-remove remove kolab apache2 apache2-bin apache2-data apache2-utils

Well, I still do not have a solution for problem 7. Do you have suggestions?

Andre Felipe Machado


Ticket Type

Event Timeline

andremachado renamed this task from Winterfell Installation bug report on Debian Jessie to Kolab Winterfell Installation bug report on Debian Jessie.Aug 8 2016, 4:37 PM

Please note, from:

Kolab Winterfell eats babies, for breakfast.

We expect consumers of Winterfell to be experienced contributors, or #YOLO believers.

In other words: Winterfell is your development snapshot, intended for upstream developers of Kolab.

And where Development happens, things are by definition not stable. Also, since Debian tends to have rather old packages of many essential components which at times need to be provided in semi-recent versions by ourselves to bring a release onto Debian, the vast majority of development does not happen on Debian, but on the primary platforms CentOS 7/RHEL 7. I believe some people also run openSUSE, which is moving at a similar speed.

So if this is your first time trying out Kolab, your life would be a lot easier if you took an actual release, ideally on a primary platform.

That said, Debian contributors are always extremely welcome.

As for general help questions, is your best choice.

The development phase is when the costs to find bugs and improve documentation are lower than at production phase.
We posted the installation report to help kolabsystems to improve its documentation.

Our team manage hundreds of servers for groupware service and Debian is a breeze for sysadmins at its Stable release over other distros. (Debian Testing and Unstable ,ubuntu are suitable for home users). As our main concerns are security, rock solid stability, manageability and package availability over "flashy features", we use Debian Stable for our servers because we manage them ourselves. As far as we could, used only official Debian repositories, and sometimes Backports repo, to receive timely security patches from Debian Security Team. As a last resort occasionaly we backported one or another package from Testing repository ourserlves.

Yes, Kolab is next to impossible to install without reading docs and tutorials over internet, and we listed the relevant ones below to help other users.

We already installed over CentOS 7 and may post its own installation bug report for its own bunch of problems and documentation improvements.

As you read, the listed problems are documentation or likely "easy" to solve at development phase, but problem 7 is still without a work around or solution.
By your text is likely to be some roundcube library or php library needed or not installed because of unlisted dependencies on kolab package.
We observed similar problem at CentOS 7 installation, because of yum design flaw. It proceeded installation WITHOUT downloading ALL needed packages.
Apt does not start installation without downloading ALL dependencies before, at download phase.

As Stable Debian 8.x Jessie is using php 5.6.24 and official CentOs 7 seems to use 5.4.16, an unlisted dependency at kolab package is likely the cause.
What are the steps to find it?

Andre Felipe *** install kolab;zoom=1 *** **** ******** **** ******* ***** *** * ** ****** **** ** **

I tried installing Kolab 16 (from OBS as of today) on Jessie.
From all the above issues I confirm issues 2.1, 5 and 6.

I found one new issue on setup-kolab:

Kolab Service password [1ZNp7PK8xTPMeLB]: 
Confirm Kolab Service password: 
ERROR: /var/log/clamav/freshclam.log is locked by another process
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
Failed to restart amavisd.service: Unit amavisd.service failed to load: No such file or directory.
Synchronizing state for postfix.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d postfix defaults
Executing /usr/sbin/update-rc.d postfix enable
Failed to execute operation: No such file or directory
vanmeeuwen lowered the priority of this task from 60 to Normal.Mar 28 2019, 8:12 AM