[389-users] high-rate queries

[Gerrard Geldenhuis]

Hi Karoly,
When you run the 389-console and double click on the Directory Server component of you installation you will have the ability to change the loglevel. Select the configuration tab and then select access log. That will show you were the access log is stored. You can also select error log and select the log levels that you want to see monitored. You can select multiple levels at once.

Additional I would recommend enabling the Audit Log before you change any of the above as that will tell you how to make the changes using LDIF files and thus not needing the GUI.

Hope that helps.

Regards

From: 389-users-bounces at lists.fedoraproject.org [mailto:389-users-bounces at lists.fedoraproject.org] On Behalf Of Karoly Czovek
Sent: 28 March 2011 11:35
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] high-rate queries

Ok. Migrating from openldap with 4 slave replicas to 389DS,
so i am new in the world of 389DS but my boss is forcing it cos have nice UI ;)

Where i can check for verbose error logs or increase log level?


On Mar 28, 2011, at 12:26 PM, Gerrard Geldenhuis wrote:


Hi Karoly,
You give very little information to go by... it might help to provide log files error and maybe access. Try different loglevels for the error log and explain in a bit more detail what is going wrong with your installation.

Regards

From: 389-users-bounces at lists.fedoraproject.org<mailto:389-users-bounces at lists.fedoraproject.org> [mailto:389-users-bounces at lists.fedoraproject.org] On Behalf Of Karoly Czovek
Sent: 28 March 2011 10:45
To: 389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>
Subject: [389-users] high-rate queries

Hi All,


Is there any reason, workaround for the 389DS about high-rate queries?
Acting as LDAP server for one exim and 5 postfix servers, and for 6 courier-imap servers, libnss-pam

After a time, my clients cannot connect to the 389DS, ldap queries coming back with temporary lookup faulure.
The 389DS has 2 cores with 2GB of ram, related settigns are the following:


# Open file descriptors
*        -        nofile        28192

# sysctl parameters
net.ipv4.tcp_keepalive_time = 120
net.ipv4.tcp_keepalive_intvl = 5
net.ipv4.tcp_keepalive_probes = 2


After I restarting the service, everything is going fine for a while.
OS: Centos 5.5


Any recommendations?


--
Karoly CZOVEK
Global Systems Administrator
MoveOne IT Department

Eastern Europe - Balkans - CIS&  Central Asia - Middle East&  Africa -
Asia Pacific
phone: +36 1 266 0181 - ext.6710
mobile: +36 70 708 9953
skype: mo_karoly.czovek
email: karoly.czovek at moveoneinc.com<mailto:karoly.czovek at moveoneinc.com>
web: http://www.moveoneinc.com<http://www.moveoneinc.com/>




________________________________________________________________________
In order to protect our email recipients, Betfair Group use SkyScan from
MessageLabs to scan all Incoming and Outgoing mail for viruses.

________________________________________________________________________
--
389 users mailing list
389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
Karoly CZOVEK
Global Systems Administrator
MoveOne IT Department

Eastern Europe - Balkans - CIS&  Central Asia - Middle East&  Africa -
Asia Pacific
phone: +36 1 266 0181 - ext.6710
mobile: +36 70 708 9953
skype: mo_karoly.czovek
email: karoly.czovek at moveoneinc.com<mailto:karoly.czovek at moveoneinc.com>
web: http://www.moveoneinc.com<http://www.moveoneinc.com/>




________________________________________________________________________
In order to protect our email recipients, Betfair Group use SkyScan from 
MessageLabs to scan all Incoming and Outgoing mail for viruses.

________________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20110328/33e97901/attachment.html>