One more question, is 2.4.44 schema and cn=config backward compatible to older version, meaning can i use 2.4.44 schema and cn=config to start 2.4.40 or prior versions?

Thanks, Ram

On Thu, Sep 14, 2017 at 9:49 PM, rammohan ganapavarapu < rammohanganap@gmail.com> wrote:

Quanah,

Thank you ,is there any thing else do i have to take care to upgrade from <=2.4.40 to 2.4.44? is there any upgrade doc that i can use?

Ram

On Thu, Sep 14, 2017 at 6:50 PM, Quanah Gibson-Mount quanah@symas.com wrote:

...

--On Thursday, September 14, 2017 7:24 PM -0700 rammohan ganapavarapu < rammohanganap@gmail.com> wrote:

I have ldap server with 2.4.40 and I have upgraded to 2.4.44 as part of

...

yum upgrade, now I am not able to bring up ldap server , i am getting some ppolicy maxrecord failure attribute error, we are using ppolicy overlay, any advice how to fix this issue?

The schema for ppolicy was changed in 2.4.43. You have to add the the following attribute to ppolicy.ldif:

olcAttributeTypes: {16}( 1.3.6.1.4.1.42.2.27.8.1.30 NAME 'pwdMaxRecordedFailure' EQUALITY integerMatch ORDERING integerOrderingMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE )

This should be done *prior* to upgrading. Unfortunately, it appears this requirement was not well communicated.

--Quanah

--

Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com