[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: openldap does not want to write log files?
- To: openldap-technical <openldap-technical@openldap.org>
- Subject: Re: openldap does not want to write log files?
- From: Mauricio Tavares <raubvogel@gmail.com>
- Date: Tue, 1 Mar 2011 10:24:48 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=xCwg4qKHGntuD5+K6kw9Shl6i9i16/zKnBlO3QSseQI=; b=o9WMTPDtqzh0fxgOw77YM0a/7Zi8eQwK/chuHm1rL3gza+y4cDPZ9tCVWtrY1R5dZ4 hGfbqkgW+qvZeHP/lpJ5szZE6aI0fV+pvGFmUdzp14QwsNll58m4jX+aoK8uORIhBOAF LT7lXFQY7LpDrLtvppsNrkOxQeF6mFaDdxTjU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=LhLaWnJdZTPnJCLYFzEJmTtJHleOc4NRxc25Pl9/DyxIZ6qcaEjsobcpLOwIgz3nAl kreFLvnxSYi+UV3RvVt2N97xxy5tkg+DC5+clnTUApktxSptjlJAunqVRXcT/jyF3be4 XUXlw/X1CbzT8znsTxDA+fh0XBQnjy0vkqqcU=
- In-reply-to: <AANLkTin5szgr56zaXWjFaE1f_eXV+PXpZDtX6MT4X5zb@mail.gmail.com>
- References: <AANLkTikOMCRjg_FLupS5tT5E0diBLhDBgsnvKDu9kRNN@mail.gmail.com> <AANLkTin5szgr56zaXWjFaE1f_eXV+PXpZDtX6MT4X5zb@mail.gmail.com>
On Tue, Mar 1, 2011 at 9:55 AM, Brett @Google <brett.maxfield@gmail.com> wrote:
> you are missing local4.debug in your syslog.conf, syslog messages are
> logged at DEBUG level by default, unless you say otherwise.
>
> " -s syslog-level
> This option tells slapd at what level debugging statements
> should be logged to the syslog(8) facility. The value "sys-
> log-level" can be set to any value or combination allowed by the
> "-d" switch. Slapd logs all messages selected by "syslog-level"
> at the syslog(3) severity level "DEBUG", on the unit specified
> with "-l".
> "
>
Thanks! Now I am getting the same output as I would get if I ran
slapd in debug mode (will fine tune later now I know what I am looking
for). I honestly did not expect it, but hey I am learning something
new! =)
> dont know why the other log is not working, perhaps check you are not
> writing logs as the ldap user or you need to --enable-debug during
> configure ?.
>
Good question, specially since now /var/log/ldap is being
written. At the same time, it barking that I did not setup monitoring
(probably need to --enable-debug and recompile):
Mar 1 09:45:09 auth slapd[12169]: [ID 468869 local4.debug]
bdb_monitor_db_open: monitoring disabled; configure monitor database
to enable
Do I need that to write to a log file defined in slapd.conf?
> Cheers
> Brett
>
> On Wed, Mar 2, 2011 at 12:17 AM, Mauricio Tavares <raubvogel@gmail.com> wrote:
>> I am feeling rather confused here. I installed openldap in a
>> solaris10/sparc box but I do not seem to persuade it to write to a log
>> file. FYI, right now I am running slapd as root so permissions AFAIk
>> should not be the issue. FYI, syslog here is the old,
>> non-rsyslog/syslog-ng variety.
>>
>> So, in the /etc/syslog.conf file I have:
>>
>> local4.info /var/log/ldap.log
>> local4.err /var/log/ldap.log
>> local4.notice /var/log/ldap.log
>>
>> which makes me think I should be covering every possible message sent
>> by slapd. Now /var/log/ldap.log is created as
>>
>> -rw------- 1 root sys 0 Feb 28 16:21 ldap.log
>>
>> and in the slapd.conf file I have
>>
>> loglevel 11560
>> logfile /var/log/slapd.log
>>
>> which not only should mean slapd is blabbing a lot to the log file.
>> Also note I am telling it to write to /var/log/slapd.log,
>>
>> -rw------- 1 root sys 0 Mar 1 07:39 slapd.log
>>
>> When I start slapd (after restarting syslog just in case), nothing is
>> written to those two log files. In fact, the only clue that something
>> happened is the data in slapd.log changed:
>>
>> -rw------- 1 root sys 0 Feb 28 16:21 ldap.log
>> -rw------- 1 root sys 0 Mar 1 07:40 slapd.log
>>
>> Anything I am missing here?
>>
>