[Date Prev][Date Next]
Re: (ITS#5979) ppolicy & access log crashes server
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#5979) ppolicy & access log crashes server
- From: firstname.lastname@example.org
- Date: Sat, 28 Feb 2009 04:01:43 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
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.
> On Fri, Feb 27, 2009 at 10:44 PM, Howard Chu <email@example.com
> <mailto:firstname.lastname@example.org>> wrote:
> email@example.com <mailto:firstname.lastname@example.org> wrote:
> Full_Name: Peter Giesin
> Version: 2.4.13
> OS: Red Hat 5.2
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (220.127.116.11)
> 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.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/