<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi Timotheus, thanks for caring :-)</p>
<p>It turns out that resetting the 389 Directory server was quite easy, simply using the bundled remove-ds tool, like this:</p>
<p> remove-ds -i slapd-$HOSTNAME -a</p>
<p>I will consider submitting it as a suggestion to setup-kolab, if I am able to confirm a successful setup. I was then able to get through the setup, but with some error messages related to Postfix. When Postfix was installed from packages, I was prompted, and opted, for "No configuration". Do you know if I should go for the default "Internet Site" option instead?</p>
<p>Then I discovered this one, with web-server not starting:</p>
<p><a href="https://lists.kolabsys.com/pipermail/bugzilla/2015-February/022601.html">https://lists.kolabsys.com/pipermail/bugzilla/2015-February/022601.html</a></p>
<p>but a reboot of the server seems to get them started. I was able to access the webadmin panel setting up my user. However, I cannot login on roundcube due to guam not running:</p>
<p># systemctl status guam <br />● guam.service - Intelligent IMAP Reverse Proxy <br /> Loaded: loaded (/lib/systemd/system/guam.service; enabled) <br /> Active: failed (Result: start-limit) since ti. 2016-05-24 16:08:28 CEST; 8min ago <br /> Main PID: 1031 (code=exited, status=1/FAILURE) <br /> <br />mai 24 16:08:28 cloud systemd[1]: guam.service: main process exited, code=exited, status=1/FAILURE <br />mai 24 16:08:28 cloud systemd[1]: Unit guam.service entered failed state. <br />mai 24 16:08:28 cloud systemd[1]: guam.service start request repeated too quickly, refusing to start. <br />mai 24 16:08:28 cloud systemd[1]: Failed to start Intelligent IMAP Reverse Proxy. <br />mai 24 16:08:28 cloud systemd[1]: Unit guam.service entered failed state.</p>
<p>At this point I have to admit that I am tempted to throw in the towel and go for Kolab 16 on CentOS 7. However, it would really be cool to get it up and running, so I will burn some more hours on it :-) Giving it a new go with a fresh install as we speak.</p>
<p>Cheers,</p>
<p>Alf</p>
<p> </p>
<p>On 2016-05-23 07:41, Timotheus Pokorra wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Hello Alf,<br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">It seems 389 Directory Server has an existing instance configured. This<br /> setup<br /> script does not intend to destroy or overwrite your data. Please make sure<br /> /etc/dirsrv/ and /var/lib/dirsrv/ are clean so that this setup does not have<br /> to<br /> worry.<br /><br /> Following the advice, I removed the content of those two folders to be able<br /> to run the setup-kolab script again, but then I got this error message:<br /><br /> Could not copy file '/etc/dirsrv/config/certmap.conf' to<br /> '/etc/dirsrv/slapd-cloud/certmap.conf'. Error: No such file or directory<br /><br /> so it seems the first message is misleading, encouraging users to remove a<br /> file that is a needed part of the 389-ds-base installation. I suggest<br /> rephrasing the message, even a very generic message is better, e.g.,</blockquote>
<br /> Clean probably does not mean "deleted", but in the state how it was<br /> before you configured the Kolab instance for the directory server.<br /><br /> This error message comes from the 389 Directory Server, as far as I can see.<br /> I cannot find the error message in<br /><a href="https://git.kolab.org/diffusion/P/browse/master/pykolab/setup/setup_ldap.py">https://git.kolab.org/diffusion/P/browse/master/pykolab/setup/setup_ldap.py</a><br /><br /> I think I remember I was told that you cannot re-run setup-kolab for<br /> the directory server.<br /> I usually do a full reinstall with this script:<br /><a href="https://github.com/TBits/KolabScripts/blob/master/kolab/reinstallCentOS.sh">https://github.com/TBits/KolabScripts/blob/master/kolab/reinstallCentOS.sh</a><br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Even better would be to include an option to clear the directory server when<br /> running setup-kolab.</blockquote>
Please file a feature request at<br /><a href="https://git.kolab.org/maniphest/task/edit/form/12/">https://git.kolab.org/maniphest/task/edit/form/12/</a><br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Almost forgot, thanks for an awesome software suite!</blockquote>
I am glad you are enjoying Kolab and you are experimenting with Winterfell!<br /><br /> Please note that Winterfell is the latest but not the greatest :) It<br /> exists for testing purposes and development purposes, and is usually<br /> not used in production.<br /> But it is good that many in the community will try to break it because<br /> the stable versions are derived from it!<br /><br /> All the best,<br /> Timotheus<br /> _______________________________________________<br /> users mailing list<br /><a href="mailto:users@lists.kolab.org">users@lists.kolab.org</a><br /><a href="https://lists.kolab.org/mailman/listinfo/users">https://lists.kolab.org/mailman/listinfo/users</a></div>
</blockquote>
<p> </p>
<div> </div>
</body></html>