<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">OK, got it. The problem came with the
fact that apache user wasn't able to see the kolab conf file
(/etc/kolab/kolab.conf). In fact, the apache user was not part of
kolab group. <br>
<br>
Now, getting to the real thing: migrating kolab 2.3.1 users to 2.4
format...<br>
<br>
Christian Tardif<br>
<div class="moz-signature">
<style type="text/css" media="screen">
#container {
position: relative;
}
#top {
position: relative;
}
#logo {
position: relative;
float: left;
}
#infos {
position: relative;
float: left;
}
#bottom {
position: relative;
width: 100%;
clear: both</style>
<div id="bottom">
<p>SVP, pensez à l’environnement avant d’imprimer ce message.</p>
</div>
</div>
On 05/10/2012 15:27, Jeroen van Meeuwen wrote:<br>
</div>
<blockquote cite="mid:2469989.H2KWAVkNcl@albert.kolabsys.com"
type="cite">
<pre wrap="">On Friday, October 05, 2012 12:46:44 AM Christian Tardif wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm actually in the process of upgrading from 2.3.1 to 2.4 (and test the
script you provided).
But I have a problem I must fix before. The installation went well, but
after basic configuration, I can't login to /kolab-webadmin interface. I
keep getting an Internal system error. What did I missed? All the
services seem to start correctly, selinux is disabled, as the firewall is.
</pre>
</blockquote>
<pre wrap="">
There should be an errors file in /var/log/kolab-webadmin/ that could help
you, but to increase verbosity you may want to enable all calls to console()
throughout the webadmin;
# cd /usr/share/kolab-webadmin
# sed -r -i -e 's|^(\s*)//console|\1console|g' `find . -type f -name "*.php"`
This should give you very verbose output in /var/log/kolab-webadmin/console
The inverse (to silence the web admin again) is:
# sed -r -i -e 's|^(\s*)console|\1//console|g' `find . -type f -name "*.php"`
</pre>
<blockquote type="cite">
<pre wrap="">On 18/09/2012 05:16, Jeroen van Meeuwen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">You wouldn't be able to spawn a VM and see what, between ldapsearches
against your Kolab 2.3 server, and ldapadds against your Kolab 3.0
server, would need to happen to migrate your LDAP data, would you?
</pre>
</blockquote>
</blockquote>
<pre wrap="">
That said, I think any migration path is likely to be in the form of LDIF, not
via the web admin (unless for a limited number of users maybe?).
Kind regards,
Jeroen van Meeuwen
--
Systems Architect
Kolab Systems AG
Zürich, Switzerland
e: <a class="moz-txt-link-abbreviated" href="mailto:vanmeeuwen@kolabsys.com">vanmeeuwen@kolabsys.com</a>
t: +41 43 501 66 91
m: +44 74 2516 3817
w: <a class="moz-txt-link-freetext" href="http://kolabsys.com">http://kolabsys.com</a>
pgp: 0x9342BF08</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kolab-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kolab-users@kolab.org">Kolab-users@kolab.org</a>
<a class="moz-txt-link-freetext" href="https://www.intevation.de/mailman/listinfo/kolab-users">https://www.intevation.de/mailman/listinfo/kolab-users</a></pre>
</blockquote>
<br>
</body>
</html>