Bug 109995 – openldap-2.2.28 + db-4.2.52_p2 fails with "illegal flag specified to txn_begin"

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Julien Allanos (RETIRED) 2005-10-21 01:01:04 UTC]

When accessing the ldap server, I get "invalid credentials" and the following
error in the logs:

bdb(dc=c,dc=b,dc=a): illegal flag specified to txn_begin
bdb_txn_get: BerkeleyDB 4.2.52 library needs TXN patch!
conn=0 op=0 RESULT tag=97 err=49 text=
conn=0 fd=10 closed

emerge info:

Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.1
3-ck8 i686)
=================================================================
System uname: 2.6.13-ck8 i686 AMD Athlon(tm) XP 1600+
Gentoo Base System version 1.6.13
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
dev-lang/python:     2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/
/usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O2 -pipe -fomit-frame-pointer"
DISTDIR="/var/portage/distfiles"
FEATURES="autoconfig collision-protect distcc distlocks fixpackages sandbox
sfperms strict userpriv usersandbox"
GENTOO_MIRRORS="ftp://ftp.proxad.net/mirrors/ftp.gentoo.org
http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
LC_ALL="fr_FR.utf8"
LINGUAS="en fr"
MAKEOPTS="-j2"
PKGDIR="/var/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/var/portage/tree"
PORTDIR_OVERLAY="/var/portage/overlay/dju"
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowext X Xaw3d alsa apache2 apm arts audiofile avi
bash-completion berkdb bitmap-fonts bzip2 cairo calendar crypt ctype cups curl
curlwrappers dbx divx4linux emboss encode exif expat fam ffmpeg firefox flac
foomaticdb ftp gd gdbm gif glitz gnome gpm gstreamer gtk gtk2 hal iconv
imagemagick imap imlib innodb ipv6 java javascript jikes jpeg jpeg2k junit kde
ldap libg++ libwww lm_sensors logitech-mouse lzw-tiff mad maildir mailwrapper
matroska mikmod mime mmx mmxext mng motif mozdevelop moznomail mozsvg mp3 mpeg
mysql ncurses nls nptl nptlonly nsplugin ogg oggvorbis opengl oss pam pcre
pdflib perl php png posix python qt quicktime readline real rtc samba sasl sdl
session shared simplexml sndfile soap sockets spell sqlite sse ssl svga symlink
tcpd tetex theora tidy tiff truetype truetype-fonts type1-fonts unicode
userlocales vhosts vidix visualization vorbis win32codecs xine xml2 xmlrpc xpm
xprint xsl xv xvid zlib linguas_en linguas_fr userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LDFLAGS

[Comment 1 Benjamin Smee (strerror) (RETIRED) 2005-11-17 09:35:15 UTC]

I tried applying the additional two patches from the openldap site with no luck.
On a hunch I then blew away ALL my old data and restarted openldap and it works
fine. A few checks have shown that other people have had similar problems and
the fix seems to be to allow openldap to rebuild the DB from scratch. 
I'd suggest this bug could be closed as the problem, I think, is due to
corrupted existing data.

[Comment 2 Robin Johnson 2005-11-17 10:03:13 UTC]

Ok, thanks.
Closing.

[Comment 3 Julien Allanos (RETIRED) 2005-11-17 12:29:27 UTC]

I already tried to save my data as LDIF, delete /var/lib/openldap-data, 
restart slapd and import back my data, without any success: I still got the 
same error message... so what should I do now?