sasldb + saslpasswd2 problem

[Cork Crawbaugh]

I've built and installed cyrus sasl 2.1.22. I am using BerkeleyDB version 
4.5. I've tested this installation using a simple script provided in the 
BerkeleyDB documentation - it creates a database from the /etc/passwd file. 
I believe the database code is working.

When I run saslpasswd2 it queries for a password verifies it and then 
exits. There is no apparent error.

Nothing gets written to '/etc/sasldb2'. If I manually create the file it 
remains empty. If I don't create it it's not created by the db routines.

In the 'auth.log' I consistently see the following for each invocation of 
'saslpasswd2':

Jan  8 23:29:59 abcdef saslpasswd2: error closing sasldb: Invalid argument
Jan  8 23:29:59 abcdef saslpasswd2: error closing sasldb: Invalid argument
Jan  8 23:29:59 abcdef saslpasswd2: Setpass for OTP successful
Jan  8 23:29:59 abcdef saslpasswd2: error deleting entry from sasldb: 
Invalid argument
Jan  8 23:29:59 abcdef saslpasswd2: error closing sasldb: Invalid argument

 From this there appears to be no problem opening the database just 
writing/flushing/closing the database file.

I am running all tests as 'root'.

I believe the SASL code is using the correct installed version of 
BerkeleyDB. I see the following:

ldd libsasldb.so
         linux-gate.so.1 =>  (0xffffe000)
         libresolv.so.2 => /lib/libresolv.so.2 (0x40018000)
         libdb-4.5.so => /usr/lib/libdb-4.5.so (0x4002c000)    <===  this 
is what I would expect
         libc.so.6 => /lib/tls/libc.so.6 (0x40132000)
         libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40248000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

I have plugins installed, as expected, in /usr/local/lib/sasl2. There is a 
link with /usr/lib/sasl2. If I run the cyrus imap server and connect with 
'imtest' I see the 'mechs' listed that I would expect.

I've added some additional debug statements to db_berkeley.c, especially in 
the open routine, i.e. DB->set_errfile( ..). I've had no luck getting 
additional error info from the app.

I'm running this on VIA chipset, x86 low-power box. I'm running SuSE linux, 
version 9.2. ( I can provide more details if need be. )

At this point any help would be most appreciated.

( I did have all of this working on a different box about 3 years ago, very 
different versions of all  these pieces, so not a complete newbie.)

Thanks,
Cork