httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 44865] New: mod_dav' s lock database becomes consistently corrupt
Date Wed, 23 Apr 2008 17:19:28 GMT

           Summary: mod_dav's lock database becomes consistently corrupt
           Product: Apache httpd-2
           Version: 2.2.8
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_dav

I am seeing the following errors in my apache logs:

[Wed Apr 23 09:58:33 2008] [error] [client] Could not LOCK
/user/27afdfe55a109f3c9bd486328c548e5c10f14ae2/ due to a failed precondition
(e.g. other locks).  [500, #0]
[Wed Apr 23 09:58:33 2008] [error] [client] The locks could not be
queried for verification against a possible "If:" header.  [500, #0]
[Wed Apr 23 09:58:33 2008] [error] [client] (2)No such file or
directory: The lock database was found to be corrupt. An indirect lock's direct
lock could not be found.  [500, #402]

This typically happens about 5 - 20 min after deleting the lock database.

The server is "high volume" running a max of about 24 dav req/s and averages
about 4.11 dav req/s.

The lock database is sitting on a ext3 partition.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message