Re: (ITS#5979) ppolicy & access log crashes server

Peter Giesin wrote:

Since the database was corrupted (we were getting a Segmentation Fault when restarting the server) we simply removed the database. I guess if we recovered the database instead we would have gotten the same results.

Recovery is preformed automatically on startup. Wiping the DB and starting over isn't necessary; if the disks holding the transaction logs don't burn up/fail then corruption simply isn't an issue.

Thanks for the quick fix.

You're welcome...

Pete

On Fri, Feb 27, 2009 at 10:44 PM, Howard Chu <hyc@symas.com mailto:hyc@symas.com> wrote:

pgiesin@gmail.com <mailto:pgiesin@gmail.com> wrote:

    Full_Name: Peter Giesin
    Version: 2.4.13
    OS: Red Hat 5.2
    URL: ftp://ftp.openldap.org/incoming/
    Submission from: (NULL) (24.187.213.234)


    Enabled both accesslog and ppolicy overlays (configurations
    included below). All
    attempts to bind with an invalid password causes the server to
    crash and
    database to be corrupted. If you disable either of the overlays
    or just the
    "logold" setting of the accesslog the behavior is no longer noticed.


Interesting, for me only the first attempt crashed; after restarting
the same attempt just failed normally. Anyway, thanks for the
report, this is now fixed in HEAD.