Strange problems bootstrapping 2.0.3

Hi,

I just recently downloaded kolab 2.0.3 (sources), compiled
and installed them 
on a Debian 3.1 stable system inside a virtual machine. Now
I'm having with 
some services after bootstrapping and can't figure out why.

So far I have the following issues:
1. /kolab/etc/apache/apache.local is not created. This makes
apache fail to 
start. Creating an empty file fixes this, but nevertheless
it seems strange. 
The template (httpd.local.template) is there. Maybe this is
an issue with 
mtimes? How does kolabconf figure out which config files to
rewrite?

2. My /kolab/etc/imapd/imapd.conf contains the following:
admins:		kolab-r
defaultacl:	kolab-r lrswipcda
while kolab.globals tells me:
cyrus-admins : manager
I can't figure out why it reads kolab-r. I don't think the
imap admin's 
account name has been changed. Accordingly, with this setup,
creating user 
accounts just creates the account in ldap, no INBOX is
created for the users 
(Permission denied). This - as well - isn't fixed by
kolabconf.

Things (maybe) out of the ordinary:
- I built imapd with an extra-switch: --with=murder
- I rebooted in between obmtool kolab and kolab_bootstrap
(which I didn't on 
previous installs I did).

I'd be really happy if someone could give me a hint as to
where to look for 
the conditions causing these errors. I was able to reproduce
the errors by 
cloning the respective virtual machines prior to
kolab_bootstrap-ping.
I can't imagine anyone else is getting this error (else the
issue tracker 
would mention it), but I don't get what's wrong with my
system.

Thanks and kind regards,
Michael

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Hi,

Am Samstag, 29. April 2006 18:07 schrieb Michael Leupold:
> 2. My /kolab/etc/imapd/imapd.conf contains the
following:
> admins:		kolab-r
> defaultacl:	kolab-r lrswipcda
> while kolab.globals tells me:
> cyrus-admins : manager

I happened to find out what caused this. Some
file-permissions were wrong 
(that's what kolabcheckperm said). It seems kolabconf
hasn't been running 
successfully at all. After changing permissions manually,
everything seems to 
work just fine. Unfortunately I didn't write down what
kolabcheckperm gave me 
on its first run, but the most important part for me might
have been:
File /kolab/etc/imapd/imapd.conf has the wrong
persmissions/owner. Found 644 
kolab:kolab, expected 640 kolab:kolab-r
Please note that this is verbatim and the typo wasn't mine


The version I'm using now is 2.1-beta1 which still showed
the above behaviour. 
Still no apache.local...

Regards,
Michael

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Op zaterdag 29 april 2006 23:12, schreef Michael Leupold:
> I happened to find out what caused this. Some
file-permissions were wrong
> (that's what kolabcheckperm said). It seems kolabconf
hasn't been running
> successfully at all. After changing permissions
manually, everything seems
> to work just fine. Unfortunately I didn't write down
what kolabcheckperm
> gave me on its first run, but the most important part
for me might have
> been: File /kolab/etc/imapd/imapd.conf has the wrong
persmissions/owner.
> Found 644 kolab:kolab, expected 640 kolab:kolab-r
> Please note that this is verbatim and the typo wasn't
mine 
>
> The version I'm using now is 2.1-beta1 which still
showed the above
> behaviour. Still no apache.local...

Change log level in /kolab/etc/kolab/kolab.globals.  Make it
e.g. 4
tail //var/log/messages, after that run 'kolabconf -n'

-- 
Richard Bos
Without a home the journey is endless

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Am Sonntag, 30. April 2006 09:37 schrieb Richard Bos:
> > The version I'm using now is 2.1-beta1 which
still showed the above
> > behaviour. Still no apache.local...
> Change log level in /kolab/etc/kolab/kolab.globals. 
Make it e.g. 4
> tail //var/log/messages, after that run 'kolabconf
-n'

Find attached the log output of kolabconf with loglevel 4.
The version running 
is 2.1-beta1.

Regards,
Michael
_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Op zondag 30 april 2006 10:38, schreef Michael Leupold:
> Am Sonntag, 30. April 2006 09:37 schrieb Richard Bos:
> > > The version I'm using now is 2.1-beta1 which
still showed the above
> > > behaviour. Still no apache.local...
> >
> > Change log level in
/kolab/etc/kolab/kolab.globals.  Make it e.g. 4
> > tail //var/log/messages, after that run
'kolabconf -n'
>
> Find attached the log output of kolabconf with loglevel
4. The version
> running is 2.1-beta1.

Look at the last lines, it contains:
T Error: Error moving configfile to
/kolab/etc/clamav/clamd.conf, error: No 
such file or directory 

Do you have clamav (rpm) installed?

-- 
Richard Bos
Without a home the journey is endless

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Am Sonntag, 30. April 2006 11:03 schrieb Richard Bos:
> > Find attached the log output of kolabconf with
loglevel 4. The version
> > running is 2.1-beta1.
> Look at the last lines, it contains:
> T Error: Error moving configfile to
/kolab/etc/clamav/clamd.conf, error: No
> such file or directory
> Do you have clamav (rpm) installed?

Yes, it seems I do. obmtool.conf contains:
install $clamav-0.88-20060110

But that's nothing I changed. The only change I made to
obmtool.conf was 
adding --with=murder to imapd. However, I also found 
a /kolab/etc/kolab/templates/clamd.conf.template. It
doesn't seem to be used 
though (maybe this is already fixed in latest cvs?).

Regards,
Michael

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users