[Date Prev][Date Next]
Re: creating a memory leak with slapd (ITS#287)
At 02:14 AM 9/14/99 GMT, email@example.com wrote:
>Full_Name: Aaron C. DuMar
>Submission from: (NULL) (184.108.40.206)
>This isn't a problem, just a note about a problem I had moving from a CSO/PH db
>ldap. I'm hoping that this will help others that see similar behavior.
>Some time back, I convinced our guys to move to an LDAP solution for mail
>etc. (our little Solaris machine running CSO/PH has seen better days). Anyways,
>dumped our data (using a perl script) from the PH server into an ldif format.
>using the ldif2ldbm binary from OpenLDAP built the db. Everything seemed fine,
>except after a few days, slapd would eat up all of our memory and the machine
>worthless (that made our email users quite unhappy :). So, I set up a script to
>restart slapd hourly to handle this until I got the problem solved.
>Well, I've finally figured out the memory leak problem. It seems the problem
>with the database (which I assume came from the transition from CSO/PH to
>I'm using the ldbm database, and when I export it to ldif format, I see entries
>dn: cn=, ou=Department of Physics, o=Texas A&M University, st=TX, c=US
>and nothing else (with the exception of the normal well formatted entries).
>There were about 15 of these things. No "cn", no other attributes. Must have
>been a bug in the db move.
Garbage db entries are commonly resultant of garbage input to
ldif2ldbm(8). ldif2ldbm(8) is designed to be used with pristine
LDIF, such as produced by ldbmcat(8) (assuming you never run ldif2ldbm).
New entries should only be added using ldapadd(1) (or via ldap_add(3)).