[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: pwdfailuretime with multi-sync

To: Chris Leung <chris@q-station.net>, openldap-technical@openldap.org
Subject: Re: pwdfailuretime with multi-sync
From: Quanah Gibson-Mount <quanah@symas.com>
Date: Wed, 30 Aug 2017 08:21:32 -0700
Content-disposition: inline
In-reply-to: <WM!67da46dcf64de75ae4fd155293eae18764bed4bba7918816a53129a4458cf0d19fb3ea6e7edcd83008097d8fb69740c1!@mailstronghold-1.zmailcloud.com>
References: <alpine.DEB.2.20.1708301340180.20362@dawn> <WM!67da46dcf64de75ae4fd155293eae18764bed4bba7918816a53129a4458cf0d19fb3ea6e7edcd83008097d8fb69740c1!@mailstronghold-1.zmailcloud.com>

--On Wednesday, August 30, 2017 2:49 PM +0800 Chris Leung<chris@q-station.net> wrote:

Sometime, the user password is replicated without problem after switched
to REFRESH, however, sometime password can't be sync.

Error 16 means "no such attribute exists". My guess would be you have ACLsthat block your replica from replicating userPassword. I'd also guess thatyou originally loaded the replica via a slapcat of the other master, sosome accounts have passwords, and others don't. This is all guesswork ofcourse, but it would match the behavior you're seeing.


--Quanah

--

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

References:
- pwdfailuretime with multi-sync
  - From: Chris Leung <chris@q-station.net>

Prev by Date: Re: Removing Berkeley DB Log Files
Next by Date: Re: pwdfailuretime with multi-sync
Index(es):
- Chronological
- Thread