Submission from: (NULL) (22.214.171.124)
When slapd configured with database ldap only, an error occurs,
#0 0x00007ffff7bb8038 in get_token (sp=sp@entry=0x7fffffff9590,
#1 0x00007ffff7bbc6f2 in ldap_str2objectclass (s=s@entry=0x7 <Address 0x7 out
flags=flags@entry=63) at schema.c:2461
#2 0x00005555555e7c1c in register_oc (def=0x7 <Address 0x7 out of bounds>,
dupok=dupok@entry=1) at oc.c:917
#3 0x00005555555935ee in init_config_ocs (ocs=ocs@entry=0x7ffff30a5960 <pcocs>)
#4 0x000055555558bf18 in config_register_schema (ct=0x7ffff30a54c0 <pccfg>,
Full_Name: Howard Chu
Submission from: (NULL) (126.96.36.199)
Submitted by: hyc
mdb_dbi_open may use "dummy" after it has gone out of scope, when creating a new
named subDB. This never caused any problem under gcc, but breaks using the Sun C
compiler when debugging is enabled and optimization is disabled. A fix is coming
--On Wednesday, August 06, 2014 11:26 AM +0000 anshman.osc(a)gmail.com wrote:
> Full_Name: Anshuman
> Version: 2.4.23
2.4.23 is 4+ years old. In addition, the ITS system is for filing bugs,
not for asking usage questions. You need to (a) upgrade to a current
release or (b) contact the vendor of your massively out of date packages.
For (a), I suggest packages from either Symas or the LTB project if you are
not able to build OpenLDAP yourself.
This ITS will be closed.
Zimbra :: the leader in open source messaging and collaboration
OS: RHEL 6.4
Submission from: (NULL) (188.8.131.52)
I am trying to get the ppolicy to lock account after N unsuccessful attempts. To
accomplish this, I defined the overlay policy in slapd.conf, and also attached
the pwdPolicySubentry to the user object.
It is able to detect the password policy, because the number of times
"pwdFailureTime" appears is always 1 less than the value I set for
"pwdMaxFailure" in the password policy.
So, if I set pwdMaxFailure=4, the count pwdFailureTime stops growing after 3.
However, the pwdAccountLockedTime is never set.
Up until release 2.3.x adding a rootdn entry to the slapd.conf solved this
issue. But today we are trying to upgrade to 2.4.23, and this "fix" no longer
Could someone please let me know what needs to be done to make this work?
# Load dynamic backend modules:
> While testing out the new mdb_copy compaction, I tried switching a live instance
> to use a different db path via MOD to change olcDbDirectory.
> This results in repeatable segv in ppolicy.c:ppolicy_connection_destroy, where
> conn refers to the correction making the change that is likely in the process of
> disconnecting, and pwcons is NULL.
There are more pwcons hits than just ppolicy_connection_destroy,
looking for the others but at a minimum ppolicy_restrict.