Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1176449

Summary: httpd.conf is missing DAVLockDB configuration
Product: Red Hat Enterprise Linux 7 Reporter: Kurt Seifried <kurt>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Martin Frodl <mfrodl>
Severity: low Docs Contact: Lenka Špačková <lkuprova>
Priority: unspecified    
Version: 7.2CC: draeuftl, isenfeld, jkaluza, jorton, kseifried
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: httpd-2.4.6-32.el7 Doc Type: Bug Fix
Doc Text:
The `mod_dav` lock database is now enabled by default in the *mod_dav_fs* module The `mod_dav` lock database is now enabled by default if the Apache HTTP *mod_dav_fs* module is loaded. The default location `ServerRoot/davlockdb` can be overridden using the `DAVLockDB` configuration directive.
Story Points: ---
Clone Of:
: 1653009 (view as bug list) Environment:
Last Closed: 2015-11-19 04:36:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
proposed patch none

Description Kurt Seifried 2014-12-21 22:51:10 UTC
Description of problem:

In RHEL 6 this was in httpd.conf by default:

#
# WebDAV module configuration section.
#
<IfModule mod_dav_fs.c>
 # Location of the WEBDav lock database.
 DAVLockDB /var/lib/dav/lockdb
</IfModule>

this section is missing in RHEL 7 httpd.conf by default. Thus you get:

A lock database was not specified with the DAVLockDB directive. One must be specified to use the locking functionality.

in the httpd error log when you try to use WebDAV locking.

Version-Release number of selected component (if applicable):

httpd-2.4.6-18.el7

How reproducible:

Always

Steps to Reproduce:
1. install httpd
2. enable WebDAV
3. try to us something that needs WebDAV locking, see error in httpd log files

Actual results:

WebDAV locking fails to work

Expected results:

WebDAV locking works by default (like it did in RHEL 6)

Additional info:

Comment 2 Joe Orton 2015-02-18 08:32:33 UTC
We should patch this upstream to make the default path hard-coded in mod_dav_fs, or at least a config-time option for that.

Comment 5 Jan Kaluža 2015-03-19 10:31:21 UTC
Created attachment 1003779 [details]
proposed patch

Add davlockdb to config.layout.

Comment 11 Kurt Seifried 2015-11-04 14:32:04 UTC
Ah sorry I thought this had already gone out in 7.1.x, my mistake. It's not letting me reopen it, grrr.

Comment 14 errata-xmlrpc 2015-11-19 04:36:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2194.html