openldap-technical September 2017

openldap-technical@openldap.org

54 participants
164 discussions

Re: Antw: Re: Removing Berkeley DB Log Files
by Douglas Duckworth 01 Sep '17

01 Sep '17

Vinyl records are back in style. So it seems slapd.conf and bdb. Thanks, Douglas Duckworth, MSc, LFCS HPC System Administrator Scientific Computing Unit Physiology and Biophysics Weill Cornell Medicine E: doug(a)med.cornell.edu O: 212-746-6305 F: 212-746-8690 On Fri, Sep 1, 2017 at 10:46 AM, Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Thursday, August 31, 2017 9:51 AM +0200 Ulrich Windl > <Ulrich.Windl(a)rz.uni-regensburg.de> wrote: > > > Also note "olcDbConfig: <DB_CONFIG setting>" is probably the modern way > > to do it. > > The "modern" way of doing things is to not use back-{bdb|hdb} at all. > > --Quanah > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <https://urldefense.proofpoint.com/v2/url?u=http- > 3A__www.symas.com&d=DwICAg&c=lb62iw4YL4RFalcE2hQUQealT9- > RXrryqt9KZX2qu2s&r=2Fzhh_78OGspKQpl_e-CbhH6xUjnRkaqPFUS2wTJ2cw&m= > iUdH-3oK-ghXbFvuOvVSpxIO_O7WDzVdOnpAuUxHEew&s=rb0zQFdfUxkSKj1ZW5SZegqif0- > UP53lXt084_p_UOE&e=> > >

1 0

Re: Antw: Re: Removing Berkeley DB Log Files
by Quanah Gibson-Mount 01 Sep '17

01 Sep '17

--On Thursday, August 31, 2017 9:51 AM +0200 Ulrich Windl <Ulrich.Windl(a)rz.uni-regensburg.de> wrote: > Also note "olcDbConfig: <DB_CONFIG setting>" is probably the modern way > to do it. The "modern" way of doing things is to not use back-{bdb|hdb} at all. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: pwdfailuretime with multi-sync
by Quanah Gibson-Mount 31 Aug '17

31 Aug '17

--On Wednesday, August 30, 2017 9:21 AM -0700 Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Wednesday, August 30, 2017 2:49 PM +0800 Chris Leung > <chris(a)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 > ACLs that block your replica from replicating userPassword. I'd also > guess that you originally loaded the replica via a slapcat of the other > master, so some accounts have passwords, and others don't. This is all > guesswork of course, but it would match the behavior you're seeing. Also, I would confirm that you have identical overlay configurations between the two masters. It sounds like on has ppolicy and perhaps the other one doesn't? Also be sure and read the ppolicy manpage closely on replication behavior. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

2 1

N-Way replication configuration
by rammohan ganapavarapu 31 Aug '17

31 Aug '17

Hi, I have a basic question in N-Way Multi master replication configuration, For example i have 3 servers and i wanted to setup N-Way replication across those servers, in the "olcSyncRepl" configuration do i have to include the Nth server it self? On each server: olcSyncRepl: rid=001 provider=$URI1 olcSyncRepl: rid=002 provider=$URI2 olcSyncRepl: rid=003 provider=$URI3 VS Server1: olcSyncRepl: rid=002 provider=$URI2 olcSyncRepl: rid=003 provider=$URI3 Server2: olcSyncRepl: rid=001 provider=$URI1 olcSyncRepl: rid=003 provider=$URI3 Server3: olcSyncRepl: rid=001 provider=$URI1 olcSyncRepl: rid=002 provider=$URI2 Which one is the right way to do? Also what is the significance of "olcServerID" do we have keep every server "olcServerID" in each server? Thanks, Ram

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical September 2017