Summary: | net/openldap24-server: User Schema load failed for attribute "pwdMaxRecordedFailure". Error code 17: attribute type undefined | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | O. Hartmann <ohartmann> |
Component: | Individual Port(s) | Assignee: | Xin LI <delphij> |
Status: | Closed Unable to Reproduce | ||
Severity: | Affects Many People | CC: | w.schwarzenfeld |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(delphij) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
O. Hartmann
2015-12-02 09:12:21 UTC
(In reply to ohartman from comment #0) I think it's probably more efficient to contact upstream (OpenLDAP.org) for help. In the meantime, have you enabled PPOLICY when building the server? You seem to be using ppolicy properties. I solved the problem by copying and modifying the port's ppolicy.ldif file according to the old one. Yes, I have checked PPOLICY to be build! The problem is: without the ppolicy schema loaded correctly, my whole DIT gets inaccessible, so I'm unable to "ldapmodify" the OLC-based configuration. Since I use PPOLICY on all OpenLDAP installations and most of them got updated the very same time, I'm courious about what is different to the system in question - but a review of the LDIF files didn't reveal much to me. I stays obscure. Dec 5 16:27:36 <0.6> thor kernel: pid 7553 (slapd), uid 389: exited on signal 6 I receive massively SIGNAL 6 corruptions a a non-working LDAP environment! This happens on systems used with port net/nss-pam-ldapd-sasl-0.8.14_3. Is this still relevant, or could it closed. |