On 03/28/2011 08:29 AM, Karoly Czovek wrote:
the server is 32bit, the exact client error message is cannot
connect to the server.
But what is the error code? 80? 81? 91? If you can reproduce
with ldapsearch, in the shell, $? should hold the error code
(even ldapsearch cant). let me check the logs once appearing
the errors again,
now disabled the restart cronjob.
On Mar 28, 2011, at 4:16 PM, Rich Megginson wrote:
On 03/28/2011 03:45 AM,
Karoly Czovek wrote:
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
What version of 389-ds-base? 32-bit or 64-bit?
After a time, my clients cannot connect to the 389DS,
ldap queries coming back with temporary lookup faulure.
What are the exact client error codes/messages? Any errors
in the dirsrv errors log? Can you post excerpts of the
dirsrv access log from around the time of the client errors?
The 389DS has 2 cores with 2GB of ram, related
settigns are the following:
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@xxxxxxxxxxxxxx
web: http://www.moveoneinc.com
--
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@xxxxxxxxxxxxxx
web: http://www.moveoneinc.com
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
|
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
