DB Errors

Patrick Nelson pnelson at neatech.com
Fri May 16 12:37:22 EDT 2003


On Fri, 2003-05-16 at 08:28, Patrick Nelson wrote:
> On Fri, 2003-05-16 at 05:24, Efler, Lukas wrote:
> > hi patrick
> > 
> > i assume you built cyrus-sasl and cyrus-imapd from source?
> > 
> > looks to me like you don't have db support... did you install the db4-devel rpm package before building cyrus-imapd?
> > did the configure script find a valid db support (ie. the various db*.h files)?
> > can you post the output of 'ldd /your/path/to/ctl_cyrusdb' ?
> > 
> > Lukas
> > 
> > > -----Original Message-----
> > > From: Patrick Nelson [mailto:pnelson at neatech.com]
> > > Sent: Donnerstag, 15. Mai 2003 18:56
> > > To: Cyrus List
> > > Subject: Re: DB Errors
> > > 
> > > 
> > > On Mon, 2003-05-12 at 23:00, Patrick Nelson wrote:
> > > > RH9 w/ cyrus-imap 2.1.13 and cyrus-sasl-2.1.13 using sasl 
> > > to connect to
> > > > a ldap server.
> > > > 
> > > > Have system installed but am seeing a error... Not sure what to do.
> > > > 
> > > > When I start cyrus-imap it appears that all is well, but I 
> > > get messages
> > > > in my /var/log/messages log that are like:
> > > > 
> > > > -------
> > > > May 12 22:22:48 co ctl_cyrusdb[17388]: DBERROR db4:
> > > > /var/lib/imap/db/__db.001: unable to initialize environment lock:
> > > > Function not implemented
> > > > May 12 22:22:48 co ctl_cyrusdb[17388]: DBERROR: dbenv->open
> > > > '/var/lib/imap/db' failed: Function not implemented
> > > > May 12 22:22:48 co ctl_cyrusdb[17388]: DBERROR: init 
> > > /var/lib/imap/db:
> > > > cyrusdb error
> > > > May 12 22:22:48 co ctl_cyrusdb[17388]: done checkpointing cyrus
> > > > databases
> > > > -------
> > > > 
> > > > Not sure if this is an error because the startup doesn't 
> > > say anything. 
> > > > Testing shows that things are working.
> > > 
> > > Hello... is there anybody out there?  Any ideas would be so cool...
> > > 
> > > 
> 
> Yes building from src
> Yes db4-devel-4.0.14-20 rpm is installed
> 
> ldd /usr/lib/cyrus-imapd/ctl_cyrusdb
> 	libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x40022000)
> 	libssl.so.2 => /lib/libssl.so.2 (0x40035000)
> 	libcrypto.so.2 => /lib/libcrypto.so.2 (0x40064000)
> 	libresolv.so.2 => /lib/libresolv.so.2 (0x40138000)
> 	libdb-3.2.so => /lib/libdb-3.2.so (0x40148000)
> 	libc.so.6 => /lib/libc.so.6 (0x401f0000)
> 	libdl.so.2 => /lib/libdl.so.2 (0x40316000)
> 	libcrypt.so.1 => /lib/libcrypt.so.1 (0x40319000)
> 	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> 
> Which is interesting that db4 isn't in there at all...  Although I'm not
> sure what that means.

Ooops I pulled the above ldd off a working system...

Here is the ldd of the offending system:

ldd /usr/lib/cyrus-imapd/ctl_cyrusdb
	libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x40022000)
	libssl.so.4 => /lib/libssl.so.4 (0x40035000)
	libcrypto.so.4 => /lib/libcrypto.so.4 (0x4006a000)
	libresolv.so.2 => /lib/libresolv.so.2 (0x40160000)
	libdb-4.0.so => /lib/libdb-4.0.so (0x40170000)
	libc.so.6 => /lib/libc.so.6 (0x40219000)
	libdl.so.2 => /lib/libdl.so.2 (0x4033f000)
	libcrypt.so.1 => /lib/libcrypt.so.1 (0x40342000)
	libgssapi_krb5.so.2 => /usr/kerberos/lib/libgssapi_krb5.so.2
(0x4036e000)
	libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x40381000)
	libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x403df000)
	libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x403f0000)
	libz.so.1 => /usr/lib/libz.so.1 (0x403f2000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x40400000)
	/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)







More information about the Info-cyrus mailing list