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

Re: (ITS#4961) If database suffix is ""



Unfortunately the problem has not been completely fixed in the HEAD.
With the fix in the head the error message disappears but the contextCSN ins NOT
ACTUALLY written to the disk. So at the next slapd startup the ContextCSN is
missing. An the servers hav to resynchronize.

Below you find the log extract.

Thanks
Best regards
Ali

============================


Log extract :
daemon: shutdown requested and initiated.
daemon: closing 7
connection_closing: readying conn=0 sd=11 for close
connection_close: conn=0 sd=11
daemon: removing 11
conn=0 fd=11 closed (slapd shutdown)
=>do_syncrepl rid=123
connection_get(12)
connection_get(12): got connid=0
daemon: removing 12r
slapd shutdown: waiting for 1 threads to terminate
ldap_free_request (origid 2, msgid 2)
ldap_free_connection 1 1
ldap_send_unbind
ber_flush2: 7 bytes to sd 12
  0000:  30 05 02 01 03 42 00                               0....B.
ldap_write: want=7, written=7
  0000:  30 05 02 01 03 42 00                               0....B.
ldap_free_connection: actually freed
slapd shutdown: initiated
bdb_modify:
bdb_dn2entry("")
bdb_modify_internal: 0x00000000:
<= acl_access_allowed: granted to database root
bdb_modify_internal: replace contextCSN
is_entry_objectclass("", "2.5.17.0") no objectClass attribute
=> entry_encode(0x00000000):
bdb_modify: updated id=00000000 dn=""
send_ldap_result: conn=-1 op=0 p=0
send_ldap_result: err=0 matched="" text=""
====> bdb_cache_release_all
slapd destroy: freeing system resources.
slapd stopped.