[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Error while updating olcDbConfig
- To: Howard Chu <hyc@symas.com>, openldap-technical@openldap.org
- Subject: Re: Error while updating olcDbConfig
- From: Daniel Jung <mimianddaniel@gmail.com>
- Date: Mon, 18 Nov 2013 21:40:17 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=jc4VVGNuBxlWK+2ufvWvYLRFYW9CNfFrlBpU/dltrVA=; b=SK4a1hfFQamnB9kKZoua3Ol8lyD27OHmOoAUHPorKuHRc3TvqLXqyE3UkAa8EtVUlG 4i8j38enJ/0NqB2zkRfwjY1+YDRFsHpiw1JXa7dCcTKt/i4cAq6pE9L2GLZi05q1QiAK 455w4kHr9rCJwnmIDRmnDcbUrySU5NRtxclw8fahTcvi43pTGLiVXjoI6jUNSty7uiIi bBB6+cIgqQNYG3hz4zkvj5R71XLgShtM9GZjeWmb3Kq/jzduYy7LgEsk4lvqn+9K3xED Fq7yzhZS+xNODn+NeFgj3vjpjQrU9xc3lgWRepdGRsVWkWwPZIG7gASD+MZrebi2kfTe IHgQ==
- In-reply-to: <528AEACB.7030206@symas.com>
- References: <CAN+6oicChf0WsXRSHGpq9cMSU1WkEFQQ-EPPBP=+X9bR4hKhPA@mail.gmail.com> <528AEACB.7030206@symas.com>
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
following seems to indicate that it isn't a permission issue. I am
running old version DB, 4.7 from our favourite distro repo :(
Seems like there is transaction that is not being closed properly??
528af863 connection_get(16)
=> ldap_bv2dn(cn=Manager,cn=config,0)
<= ldap_bv2dn(cn=Manager,cn=config)=0
=> ldap_dn2bv(272)
<= ldap_dn2bv(cn=Manager,cn=config)=0
=> ldap_dn2bv(272)
<= ldap_dn2bv(cn=manager,cn=config)=0
528af863 send_ldap_result: err=0 matched="" text=""
528af863 connection_get(16)
528af863 conn=1003 op=1 do_modify: dn (olcDatabase={2}hdb,cn=config)
=> ldap_bv2dn(olcDatabase={2}hdb,cn=config,0)
<= ldap_bv2dn(olcDatabase={2}hdb,cn=config)=0
=> ldap_dn2bv(272)
<= ldap_dn2bv(olcDatabase={2}hdb,cn=config)=0
=> ldap_dn2bv(272)
<= ldap_dn2bv(olcDatabase={2}hdb,cn=config)=0
528af863 conn=1003 op=1 modifications:
528af863 replace: olcDbConfig
528af863 multiple values
528af863 bdb(dc=example,dc=com): Error: closing the transaction region
with active transactions
528af863 bdb_db_close: database "dc=example,dc=com": close failed:
Invalid argument (22)
528af863 hdb_cf_cleanup: failed to reopen database, rc=22
528af863 send_ldap_result: err=80 matched="" text="failed to reopen
database, rc=22"
528af863 daemon: abnormal condition, shutdown initiated.
On 2013-11-18 8:36 PM, Howard Chu wrote:
Daniel Jung wrote:
Hi wonderful ppl at openldap-
Running 2.4.37 - on centos 6.4
using following ldif to update olcDbConfig
dn: olcDatabase={2}hdb,cn=config
changetype: modify
replace: olcDbConfig
olcDbConfig: set_lg_max 10485760
olcDbConfig: set_lg_regionmax 262144
olcDbConfig: set_lg_bsize 2097152
olcDbConfig: set_lg_dir /var/lib/ldap/
olcDbConfig: set_lk_max_locks 8192
olcDbConfig: set_lk_max_objects 8192
olcDbConfig: set_flags DB_LOG_AUTOREMOVE
olcDbConfig: set_tas_spins 1
-
ldapmodifyx -d 1 -h localhost -D 'cn=Manager,cn=config' -W -f
/var/tmp/ldif
Getting the following error
res_errno: 80, res_error: <failed to reopen database, rc=22>,
res_matched: <>
ldap_free_request (origid 2, msgid 2)
ldap_parse_result
ber_scanf fmt ({iAA) ber:
ber_scanf fmt (}) ber:
ldap_msgfree
ldap_err2string
ldap_modify: Other (e.g., implementation specific) error (80)
additional info: failed to reopen database, rc=22
Going through the list lead me to believe that changes will be
applied after
the restart? but didnt say it causes an error. Also does olcDbNoSync
play a
role here ?
The change is applied immediately, there should not be any restart
required. Unfortunately, it seems like the changes you applied were
invalid for the version of BerkeleyDB you're using. Your LDIF worked
perfectly fine for me, using BDB 5.3.21.
Another possibility is that the directory you specified for set_lg_dir
was invalid, didn't exist, or you didn't have permissions to write it.
One further possibility is that you were changing this value - in that
case, you need to make sure to manually move all of the BDB logfiles
from the old location to the new location first, otherwise BDB won't
be able to find them and it will think the BDB environment is corrupted.
Using the -d debug flag on the client doesn't tell you anything useful
though, you need to use -d on slapd to see what the actual error was.