Hi, I was wondering if you founded a solution to your issue, since I'm having the same...
Posts made by baruch
RE: ptloader problem finding the domain in "Hosted Kolab Groupware" Multidomain setup (Kolab16 on CenOS 7.3)
RE: Kolab 16 on Centos 7 - installation issue
Hi, thanks tku, your explanations really helped me a lot!!
I can confirm that issue and the solution provided. With a slight difference for the line to change in config.inc.php because:
- the database created by kolab is roundcube and not roundcubemail
- There is no way that I'm going to create a roundcube user and give him full right on all database. And no way that I'm letting a root user without password. So my approach is to create a roundcube user with a password
- I'll make sure to have a password on the mysql root user (for instance by running the script mysql_secure_installation:
- I create the roundcube user and database (thess commands will ask for the root password set above)
# mysql -u root -p -e "CREATE DATABASE roundcube;" # mysql -u root -p -e "GRANT ALL PRIVILEGES ON roundcube.* TO roundcube@localhost IDENTIFIED BY 'CHOOSE_A_ROUNDCUBE_PASS_HERE'";
- populate the roundcube database (again this will ask for the root password)
mysql -u root -p roundcube < /root/mysql.initial.sql
I replace the line in config.inc.php:
# sed -i "s#\$config\['db_dsnw'\] = 'mysql\://roundcube\:pass\@localhost/roundcubemail'\;#\$config['db_dsnw'] = 'mysql://roundcube:PUT_THE_SAME_ROUNDCUBE_PASS_HERE@localhost/roundcube';#g" /etc/roundcubemail/config.inc.php
- when running setup-kolab, select the option for an existing database and enter the root and roundcube password according to the ones you picked earlier
Error while installing on centos7
I'm installing kolab on a centos7 system. Everything seems to go ok except for the mysql part:
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: 2 Please supply a root password for MySQL. This password will be the administrative user for this MySQL server, and it should be kept a secret. After this setup process has completed, Kolab is going to discard and forget about this password, but you will need it for administrative tasks in MySQL. MySQL root password [XXXXXXXXXXXXXXXx]: Confirm MySQL root password: Please supply the timezone PHP should be using. You have to use a Continent or Country / City locality name like 'Europe/Berlin', but not just 'CEST'. Timezone ID [UTC]: Europe/Bucharest Please supply a password for the MySQL user 'roundcube'. This password will be used by the Roundcube webmail interface. MySQL roundcube password [XXXXXXXXXXXXXXXXXX]: Confirm MySQL roundcube password: ERROR 1005 (HY000) at line 9: Can't create table 'roundcube.kolab_alarms' (errno: 150) ERROR 1146 (42S02) at line 191: Table 'roundcube.system' doesn't exist Created symlink from /etc/systemd/system/multi-user.target.wants/httpd.service to /usr/lib/systemd/system/httpd.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.service 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.
Also obviously some part of the database seems to be missing. I don't have a kolab database, is it normal? The roundcube database seems pretty empty too:
MariaDB [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | | roundcube | +--------------------+ 4 rows in set (0.00 sec) MariaDB [(none)]> use roundcube; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed MariaDB [roundcube]> show tables; +---------------------------+ | Tables_in_roundcube | +---------------------------+ | kolab_cache_configuration | | kolab_cache_contact | | kolab_cache_event | | kolab_cache_file | | kolab_cache_freebusy | | kolab_cache_journal | | kolab_cache_note | | kolab_cache_task | | kolab_folders | +---------------------------+ 9 rows in set (0.00 sec)
The only thing is that I'm installing in a systemd-nspawn container build from a minimal install. So there might be some dependencies missing, but there are some db and tables created so the problem should be in the script itself...
For the install I stuck with https://docs.kolab.org/installation-guide/centos-7.html
RE: Error while installing in Debian 8
Hi guys thanks for your answer. So that specific problem was related to 389 not working with different user for different config. I solved it by deleting all folders related to it, even log.
That being said. Yes the install is unusable on debian.
I moved from chroot to systemd-nspawnd container and installed a centos system on it.
Error while installing in Debian 8
I'm trying to install Kolab on a Debian 8 chrooted system.
I've been following the following guide:
Then when I try to launch setup-kolab:
(kolab)root@pc-front:~# setup-kolab --fqdn=kolab.mydomain.com --mysqlserver=127.0.0.1:3306 WARNING: The Fully Qualified Domain Name or FQDN for this system is incorrect. Falling back to 'localdomain'. Running in chroot, ignoring request. Please supply a password for the LDAP administrator user 'admin', used to login to the graphical console of 389 Directory server. Administrator password [XXXXXXXXXXXX]: 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 [XXXXXXXXXXXX]: Confirm Directory Manager password: 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 [dirsrv]: kolab-server Group [dirsrv]: kolab-server 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. mydomain.com [Y/n]: Y The standard root dn we composed for you follows. Please confirm this is the root dn you wish to use. dc=mydomain,dc=com [Y/n]: Y Setup is now going to set up the 389 Directory Server. This may take a little while (during which period there is no output and no progress indication). An error was detected in the setup procedure for 389 Directory Server. This setup will write out stderr and stdout to /var/log/kolab/setup.error.log and /var/log/kolab/setup.out.log respectively, before it exits. (kolab)root@pc-front:~# cat /var/log/kolab/setup.out.log Could not import LDIF file '/tmp/ldifQ21CEQ.ldif'. Error: 256. Output: importing data ... Error - Problem accessing the lockfile /var/lock/dirsrv/slapd-kolab/lock [10/May/2017:11:43:54 +0000] - Shutting down due to possible conflicts with other slapd processes Error: Could not create directory server instance 'kolab'. Exiting . . . Log file is '/tmp/setupG78y0A.log'
Looking up on the Internet I already checked:
- No other slapd instance (either on chroot environment of host)
- Playing with /var/lock/dirsrv/slapd-kolab/ permission doesn't help
- Using default dirsrv user and group doesn't help either...
So I'm kind of stuck now. Would you have any suggestion?