We also first started testing with pipes to send logs to our logserver.
Then we switched to rsyslog to trasport the logs.
Add the following line near the top of rsyslog.conf:
$ModLoad imfile
Append to the end of rsyslog.conf or into a new file in /etc/rsyslog.d:
$InputFileName /var/log/dirsrv/slapd-users/access
$InputFileTag 389ds-access
$InputFileStateFile state-389ds-access
$InputFileSeverity info
$InputFileFacility local4
$InputRunFileMonitor
$InputFileName /var/log/dirsrv/slapd-users/errors
$InputFileTag 389ds-errors
$InputFileStateFile state-389ds-errors
$InputFileSeverity info
$InputFileFacility local4
$InputRunFileMonitor
We use the local4 facility as it was the default when we were using
OpenLDAP.
And take into account that all messages will have the same severity, in
this case info.
Regards,
Mitja
--
Mitja Mihelič
ARNES, Tehnološki park 18, p.p. 7, SI-1001 Ljubljana, Slovenia
tel: +386 1 479 8877, fax: +386 1 479 88 78
On 08/17/2013 01:46 AM, Jeffrey Dunham wrote:
We've been playing around with the named pipe log script. You could
use something like that to pass the logs to a syslog server.
http://directory.fedoraproject.org/wiki/Named_Pipe_Log_Script
-Jeff
On Fri, Aug 16, 2013 at 4:07 PM, Tom Tucker <tktuc...@gmail.com
<mailto:tktuc...@gmail.com>> wrote:
Is it possible to write 389 DS access, error and audit logs to a
downstream syslog server ($syslog_server:514) ? I did some poking
around in the UI and I can't seem to find anything like this.
Thanks in advance,
Tom
--
389 users mailing list
389-users@lists.fedoraproject.org
<mailto:389-users@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
