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)
This is from the logs when it is syncing the cn=config tree. The especially odd thing about this error is that olcDbConfig is one of the numbered entries (the ones with {#} prepending each value), not to mention that the line is question is blank. This isn't the first time I've encountered this error when trying to do this type of thing (alas, I never got around to trying to fix it before :) ), so I'm hoping that means either I'm doing something obviously wrong or somebody has seen this before.
Both servers are freebsd jails running FreeBSD 7.2 Stable.
Here are some of the relevant configs. These are not the full entries, just the important bits. They are identical on both servers and they do sync parts of the config (everything up to the value that fails).
dn: cn=config olcServerID: 1 ldap://rock.earlham.edu/ olcServerID: 2 ldap://gabbro.earlham.edu/
dn: olcDatabase={0}config,cn=config olcSyncrepl: {0}rid=001 provider=dap://rock.earlham.edu/ binddn="<snip>" bindmethod=simple credentials=<snip> searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5" timeout=1 olcSyncrepl: {1}rid=002 provider=ldap://gabbro.earlham.edu/ binddn="<snip>" bindmethod=simple credentials=<snip> searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5" timeout=1 olcMirrorMode: TRUE
olcOverlay={0}syncprov,olcDatabase={0}config,cn=config objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov
olcDatabase={1}bdb,cn=config 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).
Thanks!
Matt Edlefsen Earlham College
--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
--On August 3, 2009 1:44:24 PM -0700 Quanah Gibson-Mount quanah@zimbra.com wrote:
--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:
Also, please always include the OpenLDAP and BDB releases you are using.
Thanks, Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
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
Thatks all, that worked. I'm surprised though, as I thought that one of the points of the {#} scheme was to make all the values unique (by assigning a unique number).
I guess it was something obvious :)
Matt Edlefsen Earlham College
On Mon, Aug 3, 2009 at 5:25 PM, Oliver Liebeloliver@itc.li wrote:
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
--On August 3, 2009 7:59:23 PM -0400 Matthew Edlefsen matt.edlefsen@gmail.com wrote:
Thatks all, that worked. I'm surprised though, as I thought that one of the points of the {#} scheme was to make all the values unique (by assigning a unique number).
It should work. Which is why I asked for you to provide the release number, so we can verify if it is still a problem, or something that has already been fixed. So, again, please always provide what OpenLDAP release you are using.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
oops, sorry: slapd 2.4.16
I built it from the freebsd ports tree ( net/openldap24-server )
Here is my make showconfig if you're interested: ===> The following configuration options are available for openldap-server-2.4.16_1: SASL=off "With (Cyrus) SASL2 support" DYNACL=on "Run-time loadable ACL (experimental)" ACI=on "Per-object ACI (experimental)" DNSSRV=off "With Dnssrv backend" PASSWD=off "With Passwd backend" PERL=off "With Perl backend" RELAY=on "With Relay backend" SHELL=off "With Shell backend (disables threading)" SOCK=off "With Sock backend" ODBC=on "With SQL backend" RLOOKUPS=off "With reverse lookups of client hostnames" SLP=on "With SLPv2 (RFC 2608) support" SLAPI=off "With Netscape SLAPI plugin API" TCP_WRAPPERS=on "With tcp wrapper support" BDB=on "With BerkeleyDB support" ACCESSLOG=on "With In-Directory Access Logging overlay" AUDITLOG=on "With Audit Logging overlay" COLLECT=off "With Collect overy Services overlay" CONSTRAINT=on "With Attribute Constraint overlay" DDS=on "With Dynamic Directory Services overlay" DEREF=on "With Dereference overlay" DYNGROUP=off "With Dynamic Group overlay" DYNLIST=on "With Dynamic List overlay" LASTMOD=off "With Last Modification overlay" MEMBEROF=on "With Reverse Group Membership overlay" PPOLICY=on "With Password Policy overlay" PROXYCACHE=on "With Proxy Cache overlay" REFINT=on "With Referential Integrity overlay" RETCODE=off "With Return Code testing overlay" RWM=on "With Rewrite/Remap overlay" SEQMOD=on "Sequential Modify overlay" SYNCPROV=on "With Syncrepl Provider overlay" TRANSLUCENT=on "With Translucent Proxy overlay" UNIQUE=on "With attribute Uniqueness overlay" VALSORT=on "With Value Sorting overlay" SMBPWD=on "With Samba Password hashes overlay" DYNAMIC_BACKENDS=on "Build dynamic backends" ===> Use 'make config' to modify these settings
I know some of those are experimental, so if you think one could be causing the problem I can rebuild with it off and try it out.
I don't know if openldap has this but if there is a way to print out what the configure arguments were I could get those too.
Matt Edlefsen Earlham College
On Mon, Aug 3, 2009 at 8:13 PM, Quanah Gibson-Mountquanah@zimbra.com wrote:
--On August 3, 2009 7:59:23 PM -0400 Matthew Edlefsen matt.edlefsen@gmail.com wrote:
Thatks all, that worked. I'm surprised though, as I thought that one of the points of the {#} scheme was to make all the values unique (by assigning a unique number).
It should work. Which is why I asked for you to provide the release number, so we can verify if it is still a problem, or something that has already been fixed. So, again, please always provide what OpenLDAP release you are using.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
Matthew Edlefsen wrote:
oops, sorry: slapd 2.4.16
I built it from the freebsd ports tree ( net/openldap24-server )
I know some of those are experimental, so if you think one could be causing the problem I can rebuild with it off and try it out.
No, not necessary. Please submit an ITS with your slapd version info.
I don't know if openldap has this but if there is a way to print out what the configure arguments were I could get those too.
Matt Edlefsen Earlham College
On Mon, Aug 3, 2009 at 8:13 PM, Quanah Gibson-Mountquanah@zimbra.com wrote:
--On August 3, 2009 7:59:23 PM -0400 Matthew Edlefsen matt.edlefsen@gmail.com wrote:
Thatks all, that worked. I'm surprised though, as I thought that one of the points of the {#} scheme was to make all the values unique (by assigning a unique number).
It should work. Which is why I asked for you to provide the release number, so we can verify if it is still a problem, or something that has already been fixed. So, again, please always provide what OpenLDAP release you are using.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
Hy Matthew,
I am not sure if this as anything to do with your problem, but there is a "l" missingin your olSyncrepl configuration :)
olcSyncrepl: {0}rid=001 provider=dap://rock.earlham.edu/ binddn="<snip>" bindmethod=simple credentials=<snip> searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5" timeout=1
should be
olcSyncrepl: {0}rid=001 provider=ldap://rock.earlham.edu/ binddn="<snip>" bindmethod=simple credentials=<snip> searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5" timeout=1
Cordialement,
Adrien Futschik
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)
This is from the logs when it is syncing the cn=config tree. The especially odd thing about this error is that olcDbConfig is one of the numbered entries (the ones with {#} prepending each value), not to mention that the line is question is blank. This isn't the first time I've encountered this error when trying to do this type of thing (alas, I never got around to trying to fix it before :) ), so I'm hoping that means either I'm doing something obviously wrong or somebody has seen this before.
Both servers are freebsd jails running FreeBSD 7.2 Stable.
Here are some of the relevant configs. These are not the full entries, just the important bits. They are identical on both servers and they do sync parts of the config (everything up to the value that fails).
dn: cn=config olcServerID: 1 ldap://rock.earlham.edu/ olcServerID: 2 ldap://gabbro.earlham.edu/
dn: olcDatabase={0}config,cn=config olcSyncrepl: {0}rid=001 provider=dap://rock.earlham.edu/ binddn="<snip>" bindmethod=simple credentials=<snip> searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5" timeout=1 olcSyncrepl: {1}rid=002 provider=ldap://gabbro.earlham.edu/ binddn="<snip>" bindmethod=simple credentials=<snip> searchbase="cn=config" type=refreshAndPersist retry="5 5 300 5" timeout=1 olcMirrorMode: TRUE
olcOverlay={0}syncprov,olcDatabase={0}config,cn=config objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov
olcDatabase={1}bdb,cn=config 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_c onfig.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).
Thanks!
Matt Edlefsen Earlham College
openldap-technical@openldap.org
-
Adrien Futschik -
Howard Chu -
Matthew Edlefsen -
Oliver Liebel -
Quanah Gibson-Mount