Re: BDB 4.2.50 [finally] available

[Matthew Schumacher <matt.s@aptalaska.net>]

Mine doesn't work with db-4.2:

I get though the first 3 tests without issues then:

>>>>> Starting test004-modify ...
running defines.sh
running defines.sh . bdb
Cleaning up in ./test-db...
Running slapadd to build slapd database...
Starting slapd on TCP/IP port 9009...
Testing slapd modify operations...
Waiting 5 seconds for slapd to start...
Testing modify, add, and delete...
ldapmodify failed (80)!
>>>>> ./scripts/test004-modify failed (exit 80)

My master.log reports:

<= index_entry_add( 20, "cn=Gern Jensen,ou=Information Technology 
Division,ou=People,o=University of Michigan,c=US" ) success
bdb(o=University of Michigan,c=US): lock_downgrade: Lock is no longer valid
bdb(o=University of Michigan,c=US): lock_downgrade: Lock is no longer valid
bdb(o=University of Michigan,c=US): lock_downgrade: Lock is no longer valid
bdb(o=University of Michigan,c=US): lock_downgrade: Lock is no longer valid
bdb(o=University of Michigan,c=US): PANIC: Invalid argument
bdb_add: txn_commit failed : DB_RUNRECOVERY: Fatal error, run database 
recovery (-30978)
send_ldap_result: conn=1 op=5 p=3
send_ldap_result: err=80 matched="" text="txn_commit failed"
send_ldap_response: msgid=6 tag=105 err=80
ber_flush: 31 bytes to sd 11
connection_get(11)
connection_get(11): got connid=1
connection_read(11): checking for input on id=1
ber_get_next
ber_get_next: tag 0x30 len 5 contents:
ber_get_next
ber_get_next on fd 11 failed errno=0 (Success)
connection_read(11): input error=-2 id=1, closing.
connection_closing: readying conn=1 sd=11 for close
connection_close: deferring conn=1 sd=11
do_unbind
conn=1 op=6 UNBIND
connection_resched: attempting closing conn=1 sd=11
connection_close: deferring conn=1 sd=11
daemon: shutdown requested and initiated.
connection_close: deferring conn=1 sd=11
slapd shutdown: waiting for 1 threads to terminate
bdb(o=University of Michigan,c=US): PANIC: fatal region error detected; 
run recovery
conn=1 op=5 RESULT tag=105 err=80 text=txn_commit failed
slapd: entry.c:347: entry_free: Assertion `e->e_private == ((void *)0)' 
failed.

Can you modify records in your database?

schu

Quanah Gibson-Mount wrote:
> --On Tuesday, November 25, 2003 3:58 PM -0600 Lars Peterson 
> <lars@itech-mke.com> wrote:
>
> > After hacking configure, you were able to successfully build and install
> > 2.1.23? Are the existing 4.1.x bdb files compatible, or would this
> > upgrade require a slapcat/slapadd?
>
>
> I just got it built. :)  Here is what I find so far:
>
> You cannot use an existing DB-4.1 database.
> You cannot use slapcat to export an existing DB-4.1 database.
>
> So to upgrade:
>
> 1) slapcat DB with your 4.1 build.
>
> 2) Install 4.2 build (bdb & openldap)
>
> 3) slapadd your DB
>
> --Quanah
>
> --
> Quanah Gibson-Mount
> Principal Software Developer
> ITSS/TSS/Computing Systems
> ITSS/TSS/Infrastructure Operations
> Stanford University
> GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html