(ITS#5527) slapd segfaults when using dynlist

Bug #218734 reported by Pierre Paysant-Le Roux
6
Affects Status Importance Assigned to Milestone
openldap2.3 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Adding those tree lines to the default slapd.conf causes a segfault when starting slapd :

moduleload dynlist
overlay dynlist
dynlist-attrset groupOfNames labeledURI member

slapd 2.4.7-6ubuntu3 on Ubuntu hardy

Revision history for this message
Chuck Short (zulcss) wrote :

I was able to confirm this and have a patch to fix.

Thanks
chuck

Changed in openldap2.3:
status: New → Confirmed
Revision history for this message
Anderson (amg1127) wrote :

2.4.7-6ubuntu4.1 crashes with dynlists also...

Revision history for this message
Chuck Short (zulcss) wrote :

I have submitted a bug report upstream.

Thanks
chuck

Revision history for this message
Howard Chu (hyc) wrote :

I don't see a crash with stock 2.4.7 or 2.4.9. Please provide the actual slapd.conf used to reproduce this bug, and the stack trace for the crash.

Revision history for this message
Anderson (amg1127) wrote :

I think it's better to send my entire test base...

In order to reproduce the bug:

# Download my attachment and extract the BZIP archive on an existing folder '/home/amg1127'.
# "cd" to '/home/amg1127/ldap
# Create the database from the included LDIF by running './create-master-base.sh'
# Got a SIGSEGV
# Remove /home/amg1127/ldap folder and entire content within
# Extract the BZIP archive on that folder again
# Edit the file /home/amg1127/ldap/maindb-commonparams.conf and comment lines 44-45
# Create the database from the included LDIF by running './create-master-base.sh'
# Edit the file /home/amg1127/ldap/maindb-commonparams.conf and uncomment lines 44-45 (that is, undo the previous edition).
# Run the server: './run-master-slapd.sh'
# Got another SIGSEGV

Revision history for this message
Anderson (amg1127) wrote :

GDB backtrace and Valgrind logs, extracted using instructions from https://wiki.ubuntu.com/Backtrace and https://wiki.ubuntu.com/Valgrind .

Revision history for this message
Howard Chu (hyc) wrote :

Thanks for this. I see it crashing in 2.4.7 but not in 2.4.9.

Revision history for this message
Anderson (amg1127) wrote :

I just compiled openldap-2.4.9-1ubuntu1 and saw the bug fixed. It is now in production environment.

Are there plans to backport this package from Intrepid to Hardy?

Revision history for this message
Adam Sommer (asommer) wrote :

Justed tested openldap2.3 - 2.4.9-1ubuntu1~ppa1 from Chuck's PPA, and adding the dynlist configuration didn't cause slapd to segfault. Everything worked fine.

Revision history for this message
Chuck Short (zulcss) wrote :

This is in hardy-proposed now, please enable and test on a test machine since you are in a production environment already.

Thanks
chuck

Revision history for this message
Anderson (amg1127) wrote :

Sorry, I didn't saw your packages before, because of version numbering. I had installed packages from Chuck's PPA, with version 2.4.9-1ubuntu1~ppa1 and packages from hardy-proposed has version 2.4.9-0ubuntu0.8.04.

In order to allow automatic installation of hardy-proposed packages with a standard dist-upgrade, can version numbering be changed?

Revision history for this message
Anderson (amg1127) wrote :

I just installed them now... No crashes while starting services...

Revision history for this message
Anderson (amg1127) wrote :

I ran slapd with dynlist enabled since 20/06/2008 and stopped it yesterday (because of USN-625-1).

I think this bug can be closed now, but I didn't know if things were fixed in "pplr" setup...

Revision history for this message
Chuck Short (zulcss) wrote :

Closing thanks for the bug report.

Changed in openldap2.3:
status: Confirmed → Fix Released
status: Fix Released → In Progress
Chuck Short (zulcss)
Changed in openldap2.3:
status: In Progress → Fix Released
Revision history for this message
Pierre Paysant-Le Roux (pplr) wrote :

Anderson, I tested the 2.4.9-0ubuntu0.8.04 and the bug is gone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.