[Kolab-devel] kolabquotawarn complains about missing settings in kolab.conf
Steffen Hansen
steffen at klaralvdalens-datakonsult.se
Wed Dec 22 11:51:58 CET 2004
On Tuesday 21 December 2004 20:48, Bernhard Herzog wrote:
> Hi,
>
> on our server, kolabquotawarn (most likely, could be something else)
> produces the following messages in /var/log/syslog:
>
> Dec 21 20:20:01 neso /USR/SBIN/CRON[3946]: (kolab) CMD
> (/kolab/etc/kolab/kolabquotawarn) Dec 21 20:20:03 neso C Error: One
> or more required configuration variables (`bind_dn', `bind_pw',
> `ldap_uri' and/or `base_dn') are missing in `kolab.conf' Dec 21
> 20:20:03 neso C Error: One or more required configuration variables
> (`bind_dn', `bind_pw', `ldap_uri' and/or `base_dn') are missing in
> `kolab.conf' Dec 21 20:20:03 neso C Error: Unable to bind to DN `'
> Dec 21 20:20:03 neso C Error: Unable to find kolab object `k=kolab,'
> Dec 21 20:20:03 neso C Error: Unable to bind to DN `'
> Dec 21 20:20:03 neso C Error: Unable to find kolab object `k=kolab,'
> Dec 21 20:20:07 neso /kolab/etc/kolab/kolabquotawarn[3946]:
> kolabquotawarn: fatal: Unable to authenticate with Cyrus admin
> interface, Error = `'
>
>
> The settings that kolabquotawarn claims to be missing are present in
> /kolab/etc/kolab/kolab.conf. The ldap contents look fine, too. What
> could be the problem?
You might have found a bug that must have been introduced recently when
some permissions on the conf-files were tweaked. kolabquotawarn is run
as user kolab, but kolab.conf is only readable by root.
I'll make the conf-file owned by kolab instead.
regards
--
Steffen Hansen | Klarälvdalens Datakonsult AB
Senior Software Engineer| http://www.klaralvdalens-datakonsult.se
|
| Platform-independent
| software solutions
More information about the devel
mailing list