On Fri, 25 Jul 2003, Nikola Milutinovic wrote:
> > the binaries shows the same output as above. When I start the Cyrus
> > server up, I get the same errors!!! I thought I disabled BerkeleyDB by
> > specifying skiplist for everything? So, why am I still getting the
> > "db4: unable to join the en
>By the way, I through ladebug at the ctl_cyrudb program. The stack trace
>looks like the following:
>
>>0 0x304f624 in __db_errcall(0x3ffc008a2b0, 0x0, 0x57, 0x0, 0x0, 0x0)
>in /usr/local/BerkeleyDB.4.1/lib/libdb-4.1.so
>#1 0x304f4b0 in __db_err(0x3ffc008a2b0, 0x0, 0x57, 0x0, 0x
By the way, I through ladebug at the ctl_cyrudb program. The stack trace
looks like the following:
0 0x304f624 in __db_errcall(0x3ffc008a2b0, 0x0, 0x57, 0x0, 0x0, 0x0)
in /usr/local/BerkeleyDB.4.1/lib/libdb-4.1.so
#1 0x304f4b0 in __db_err(0x3ffc008a2b0, 0x0, 0x57, 0x0, 0x0, 0x0)
I have tried everything to get DB stuff working... I just don't know what
is going on. Once again, I am on a Tru64 5.1a cluster, was using BerkDB
4.0.14, then switched to 4.1.25. This is with Cyrus IMAP 2.2.1-beta.
Basically, I get the following errors (just the ctl_cyrusdb lines):
DBERROR db4: