[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#6563) slapadd locks up shared memory segments



Full_Name: Aravind Gottipati
Version: 2.4.21
OS: RHEL 5.5
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (63.245.220.240)


I have enabled shared memory in my slapd.conf file.  With this setup, it appears
that slapadd does not release the shared memory segments once its done.  This
prevents the ldap server from starting up after, because it complains that these
shared memory segments are in use.

To reproduce:
With shm_key enabled in the slapd.conf file, slapdd a (hdb) database.
Try to then start up slapd.

Work around:
When you slapadd the database, turn off shared memory settings in the slapd.conf
file.  Re-enable it after slapadd is done.

I have tried cleaning up those segments with ipcrm, but ipcrm simply says that
the memory segments are already removed.  Its lying to you, those segments are
still there (ipcs lists them).

Please let me know if I can get any you any more information to help with the
troubleshooting.  I am not sure if you'd see the same issues with a bdb backend
(I use hdb, but afaik they are pretty similar).