slapcat (openldap/slapd) seg fault on new rc1 kolab install under SuSE 9.3

[Jesse Mundis]

Greetings kolab users.  I've just built rc1 from sources for a fresh SuSE 9.3
system.  The build and install all seemed to work just fine.  But when I try to
bootstrap kolab, I get the following (note the Segmentation fault after the
checks for running servers):

----------------------------------------------------------------------
host:/ # cd - /kolab/rc1-sources
host:/kolab/rc1-sources # /kolab/etc/kolab/kolab_bootstrap -b

KOLAB BOOTSTRAP

Check for running webserver on port 80
Check for running webserver on port 443
Check for running imap server on port 143
Check for running imap server on port 220
Check for running imap server on port 585
Check for running imap server on port 993
Check for running pop3 server on port 109
Check for running pop3 server on port 110
Check for running pop3 server on port 473
Check for running pop3 server on port 995
Check for running smtp server on port 25
Check for running smtp server on port 465
Check for running ftp server on port 21
Check for running Amavis Virus Scanner Interface on port 10024
Check for running Kolab daemon on port 9999
Check for running OpenLDAP server on port 636
Check for running OpenLDAP server on port 389
Check for running Sieve server on port 2000
Excellent all required Ports are available!
sh: line 1: 14942 Segmentation fault      /kolab/sbin/slapcat >/dev/null 2>&1
LDAP repository is empty - assuming fresh install

[...choose defaults for mail domain, master server, and select password...]

prepare LDAP database...
temporarily starting slapd
Waiting for OpenLDAP to start

could not connect ldap server ldap://127.0.0.1:389/ at /kolab/etc/kolab/kolab_bootstrapline 415.
host:/kolab/rc1-sources #
----------------------------------------------------------------------

Obviously it can't connect because the server isn't running due to the segfault
listed above. 

Trying an strace of the slapd server itself seems to indicate a corrupted pointer 
reference.  The program starts up just fine, does a bunch of set up, then proceeds
to read in a bunch of files.  There are many successful sets of open / fstat64 /
mmap2 / read / close / munmap and then after one more it just blows up.  Note in
particular how the instruction pointer has gone off into lala-land on the segfault
line.  The last bit of the strace of slapd before the segfault looks like this:

[ffffe410] open("/etc/mtab", O_RDONLY)  = 6
[ffffe410] fstat64(6, {st_dev=makedev(3, 66), st_ino=107208, st_mode=S_IFREG|0644,
st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=197,
st_atime=2005/05/13-18:03:18, st_mtime=2005/05/13-11:51:13,
st_ctime=2005/05/13-11:51:13}) = 0
[ffffe410] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x40018000
[ffffe410] read(6, "/dev/hdb2 / reiserfs rw,acl,user"..., 4096) = 197
[ffffe410] close(6)                     = 0
[ffffe410] munmap(0x40018000, 4096)     = 0
[ffffe410] open("/proc/stat", O_RDONLY) = 6
[ffffe410] fstat64(6, {st_dev=makedev(0, 3), st_ino=4026531853,
st_mode=S_IFREG|0444, st_nlink=1, st_uid=0, st_gid=0, st_blksize=1024, st_blocks=0,
st_size=0, st_atime=2005/05/13-18:08:39, st_mtime=2005/05/13-18:08:39,
st_ctime=2005/05/13-18:08:39}) = 0
[ffffe410] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x40018000
[ffffe410] read(6, "cpu  365769 0 71164 8104199 2912"..., 1024) = 686
[ffffe410] read(6, "", 1024)            = 0
[ffffe410] close(6)                     = 0
[ffffe410] munmap(0x40018000, 4096)     = 0
[081dd426] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
upeek: ptrace(PTRACE_PEEKUSER,14669,48,0): No such process
[????????] +++ killed by SIGSEGV +++


Anyone have any ideas?  As a release candidate, I figured something like this would
have been spotted before now.  Searching the web and the other kolab groups, I've
found two other people with the same problem, but no solution.

Any and all ideas welcome.

Thanks,

Jesse