Re: Second instance of slapd segfaults (ITS#2694)

[richardh@examen.com]

On Sat, 2003-09-13 at 21:47, Howard Chu wrote:
> I cannot reproduce this problem on my Linux test systems. Please run with "-d 7"
> and send us the debug output from the crash. Also, please run under the debugger
> and send us the stack backtrace from the crash:
>         gdb slapd
>         run -d7 -g ldap -u ldap -h "ldap://0.0.0.0:3000";
> 

GDB output of slapd when default instance already running with segfault:
***********************

# gdb /opt/openldap/libexec/slapd 
GNU gdb 2002-04-01-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-linux"...(no debugging symbols
found)...
(gdb) run -d7 -u ldap -g ldap -h ldap://0.0.0.0:3000 -f
/opt/openldap/etc/openldap/slapd_backup.conf
Starting program: /opt/openldap_2.1.22/libexec/slapd -d7 -u ldap -g ldap
-h ldap://0.0.0.0:3000 -f /opt/openldap/etc/openldap/slapd_backup.conf
[New Thread 1024 (LWP 22120)]
@(#) $OpenLDAP: slapd 2.1.22 (Aug 26 2003 16:11:54) $
        root@:/tmp/openldap-2.1.22/servers/slapd
daemon_init: ldap://0.0.0.0:3000
daemon_init: listen on ldap://0.0.0.0:3000
daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldap://0.0.0.0:3000)
daemon: initialized ldap://0.0.0.0:3000
daemon_init: 1 listeners opened

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 22120)]
client_dispose (pconn=0xc) at client.c:255
255     client.c: No such file or directory.
        in client.c


***************************


GDB output of same program without default instance already running:
***************************
gdb /opt/openldap/libexec/slapd 
GNU gdb 2002-04-01-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-linux"...(no debugging symbols
found)...
(gdb) run -d7 -u ldap -g ldap -h ldap://0.0.0.0:3000 -f
/opt/openldap/etc/openldap/slapd_backup.conf
Starting program: /opt/openldap_2.1.22/libexec/slapd -d7 -u ldap -g ldap
-h ldap://0.0.0.0:3000 -f /opt/openldap/etc/openldap/slapd_backup.conf
[New Thread 1024 (LWP 22124)]

@(#) $OpenLDAP: slapd 2.1.22 (Aug 26 2003 16:11:54) $
        root@sphinx2:/tmp/openldap-2.1.22/servers/slapd
daemon_init: ldap://0.0.0.0:3000
daemon_init: listen on ldap://0.0.0.0:3000
daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldap://0.0.0.0:3000)
daemon: initialized ldap://0.0.0.0:3000
daemon_init: 1 listeners opened
slapd init: initiated server.
slap_sasl_init: initialized!
bdb_initialize: initialize BDB backend
bdb_initialize: Sleepycat Software: Berkeley DB 4.1.25: (December 19,
2002)
>>> dnNormalize: <cn=Subschema>

***SNIP**** -Continues to load from here. 


****************************

Perhaps the issue is in the slapd_sasl_init? Again if the listener on
port 3000 is started first, then the one on the default port has no
issues.

Thanks,

-Richard