Error apperas when number of users is higher than 21800 (total users 21900)
and difference between successful query and bad one is:
Good
517a35fd = access_allowed: search access to
uid=1000,ds=USERS,o=STANDARD,dc=SPR entry requested
517a35fd = root access granted
517a35fd = access_allowed:
Hi all
I'm a beginner of openldap.
When I can't use a ldap server because of hardware or network trouble, I
want to reduce the influence of ldap client.
I changed the following configration of ldap.conf.
bind_policy soft
bind_timelimit 10
nss_initgroups_ignoreusers [local users...]
Are there
I just recently migrated to a new OpenLDAP environment, and am
experiencing an occasional issue. I am using 2.4.35 and Redhat 6 -
x64 with OpenLDAP compiled and packaged locally. I have setup
multimaster using delta-sync with MDB being utilized for both the user
data as well as the access
On 26/4/2013 12:50 μμ, Yuki Takase wrote:
When I can't use a ldap server because of hardware or network trouble,
I want to reduce the influence of ldap client.
I changed the following configration of ldap.conf.
You can setup your software to try a number of ldap servers in turn (I
guess it
syncrepl really isn't intended for initial full loads, although it will
work eventually (as you've seen). The preferred method for standing up an
offline server is slapadd -q. syncrepl can then handle deltas since the LDIF
was generated; this should complete fairly rapidly.
Ok, sound
Meike Stone schrieb (26.04.2013 14:34 Uhr):
Is it possible to simulate the present phase with ldapsearch, to look
if the provider needs so long and if, what part (entries updated or
unchanged entry ) needs so long?
look at
# man ldapsearch
for -E and sync=rp[/cookie][/slimit]
2013/4/26 Marc Patermann hans.mo...@ofd-z.niedersachsen.de:
Meike Stone schrieb (26.04.2013 14:34 Uhr):
Is it possible to simulate the present phase with ldapsearch, to look
if the provider needs so long and if, what part (entries updated or
unchanged entry ) needs so long?
look at
# man
--On Friday, April 26, 2013 8:01 AM -0400 Al afrunn...@gmail.com wrote:
I figured out how to replicate this. When a user messes up their
password, they get a pwdFailureTime attribute set. When the password
is reset by an administrator (userPassword is modified), this error
occurs. Is this a
