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

Re: olcDbConfig: value #14 provided more than once



this often happens when slapd.conf is converted to slapd.d/.
the easiest way to prevent this is to remove all comments
from the DB_CONFIG file in your db-directory.

oliver

Quanah Gibson-Mount schrieb:


--On August 3, 2009 4:34:54 PM -0400 Matthew Edlefsen <matt.edlefsen@gmail.com> wrote:

Hello, I'm trying to do multi-master replication and after following
the directions in the User Guide I came across the error:

Aug  3 20:21:38 gabbro slapd[81578]: syncrepl_message_to_entry:
rid=001 mods check (olcDbConfig: value #14 provided more than once)
olcDbConfig: {0}# $OpenLDAP: pkg/ldap/servers/slapd/DB_CONFIG,v
1.3.2.4 2007/12/18 11:53:27 ghenry Exp $
olcDbConfig: {1}# Example DB_CONFIG file for use with slapd(8) BDB/HDB
databases.
olcDbConfig: {2}#
olcDbConfig: {3}# See the Oracle Berkeley DB documentation
olcDbConfig: {4}#
<http://www.oracle.com/technology/documentation/berkeley-db/db/ref/env/db
_config.html> olcDbConfig: {5}# for detail description of DB_CONFIG
syntax and semantics. olcDbConfig: {6}#
olcDbConfig: {7}# Hints can also be found in the OpenLDAP Software FAQ
olcDbConfig: {8}#       <http://www.openldap.org/faq/index.cgi?file=2>
olcDbConfig: {9}# in particular:
olcDbConfig: {10}#   <http://www.openldap.org/faq/index.cgi?file=1075>
olcDbConfig: {11}
olcDbConfig: {12}# Note: most DB_CONFIG settings will take effect only
upon rebuilding
olcDbConfig: {13}# the DB environment.
olcDbConfig: {14}
olcDbConfig: {15}# one 1 GB cache
olcDbConfig: {16}set_cachesize 0 1073741824 1
olcDbConfig: {17}
olcDbConfig: {18}# Data Directory
olcDbConfig: {19}#set_data_dir db
olcDbConfig: {20}
olcDbConfig: {21}# Transaction Log settings
olcDbConfig: {22}set_lg_regionmax 262144
olcDbConfig: {23}set_lg_bsize 104857600
olcDbConfig: {24}set_lk_max_locks 100000
olcDbConfig: {25}#set_lg_dir logs
olcDbConfig: {26}
olcDbConfig: {27}# Note: special DB_CONFIG flags are no longer needed
for "quick"
olcDbConfig: {28}# slapadd(8) or slapindex(8) access (see their -q
option).

At a complete guess, this would be because lines 11, 14, 17, 20, and 26 are all identical empty values. Try making them comments ("#") instead.

--Quanah

--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration