Re: Upgrade from 2.4.40 to 2.4.44

To: Quanah Gibson-Mount <quanah@symas.com>

Subject: Re: Upgrade from 2.4.40 to 2.4.44

From: rammohan ganapavarapu <rammohanganap@gmail.com>

Date: Thu, 14 Sep 2017 20:30:49 -0700

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=R6H0/0yHeGF5/AhHsJX6KsPvma2T8HHOjYsAbu+U8zk=; b=jOdEjlIaqJmy6esCf+hJ+bYILoPVz65RCe3QmtqjgevpUlhHRJ2u+hzYrQon6D8LtG ZdvN8T9onnOBQjg+otaECBNFbxgxwii0kwK342WdPvjNHRa5sKTTkS5ha5gB5At2fRZw zXCo9Pkv0Rah3o7iFaUvM4sd8YqXwYmywxPYUsjBdq+S1w7pTiAoWkgVGucom5GKu/WT rs0wcqesos7XmOT7sCDHp8bOq0uxl2gLk2d9KpFnBHMp3uOZY8fGS9NWwOtxrrStsarj Vlfloj3/J4EDdhL359Xpe6HXF7ydHqCDzpHvj/UbZnQ8PPl+4p0jrbIIXeRxKb3Nv/3G BCpQ==

In-reply-to: <CALm_VjhPWWj8VvAEf1RVW9vt0mMKTZgFZrYOWHY4BU648eYyWA@mail.gmail.com>

References: <CALm_Vjg1UdjtBmEDKWxy-ih46wTRx+OvDcu=kjH-Wq__d0twGA@mail.gmail.com> <CALm_VjiZDRV0rZ8CGer6GzownQG=7mD07x93juocGSRpc6U+WQ@mail.gmail.com> <CALm_Vjh5YUwhBUQSft_FyRb00WQFiDC-LJPYjcOLKf00hmNY8A@mail.gmail.com> <CALm_VjhbmFFmP4qAsT8_yoPvsnWveAPT6O_2j1aibx6zumN+Ag@mail.gmail.com> <WM!2b27804d1962c89ca60ba6b779a9a7b5e4e4ec48313350811fd70226bb045af70095c25acfcf2c6f7407bb706df0f16c!@mailstronghold-3.zmailcloud.com> <4AA27E7AC368477495247EAC@192.168.1.30> <CALm_VjhPWWj8VvAEf1RVW9vt0mMKTZgFZrYOWHY4BU648eYyWA@mail.gmail.com>

If i accident allt upgrade rpm to 2.4.44 is there any way to fix this issue?

On Sep 14, 2017 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>

References:

Upgrade from 2.4.40 to 2.4.44
- From: rammohan ganapavarapu <rammohanganap@gmail.com>