Re: 3.0 on Debian Wheezy: stuck
"Jeroen van Meeuwen (Kolab Systems)" <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab,gmane.comp.kde.kolab.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Johannes, On 2012-10-15 17:45, Johannes Graumann wrote: > When using the setup-kolab patches I recently checked into the git > repository, the configuration of a *.deb based installation runs > through to > its end. > I have not yet had a chance to review any of your patches, I do appreciate you working on them. > However, > 1) http://MYSERVER/kolab-admin shows the admin interface, I would have expected the webadmin be located at http://MYSERVER/kolab-webadmin/ - this is what is shipped in the default configuration as the rewritebase. > but I can't log in > using "cn=Directory Manager" - "internal System Error." Shows up in > the > browser. The dirsrv log shows what's attached below. I also think > cyrus > might not be configured/running. > The log snippet seems to be from setup-kolab's LDAP tree initialization as opposed to from your attempt to login to the Kolab Web Administration Panel (WAP). For better verbosity on what's going on in the WAP client and API side, set debug_mode = trace in [kolab_wap] in /etc/kolab/kolab.conf. You should then get log files in /var/log/kolab-webadmin/. There may already be a log file 'errors' in there. > 2) http://MYSERVER/roundcubemail does'nt exist at all - the apache > config of > this setup has me puzzled ... > > I'd highly appreciate any hints on how to verify the services > involved step > by step and also educated guesses what might be misconfigured. > I think the roundcubemail package is supposed to install an Apache configuration configuration file /etc/apache2/sites-enabled/roundcubemail - a subsequent step may therefore be to enable the site (a2ensite?). Kind regards, Jeroen van Meeuwen -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08