Sponsored Content
Operating Systems Linux Could not open the lock database - Apache WebDAV setup Post 302563482 by majid.merkava on Tuesday 11th of October 2011 12:04:06 PM
Old 10-11-2011
Could not open the lock database - Apache WebDAV setup

I configured a WebDAV server using Apache. Here is my configuration:
Code:
DAVLockDB /var/www/DAVLock.db
<Location /majid>
    AllowOverride None
    Options +Indexes
    DAV On     
    AuthUserFile 
    /var/www/users.db     
    AuthName Authentication     
    AuthType Basic     
    <Limit GET PUT DELETE PROPFIND PROPPATCH MKCOL COPY MOVE LOCK UNLOCK>
        Require user majid
    </Limit> 
</Location>
 
Alias /majid /var/www/dav/majid

`/var/www/DAVLock.db` is owned by apache user and group. I can access WebDAV share via browser.
I have configured a WebFolder in Windows XP SP3. But I can't create file and folders. `error_log` file says:
Code:
[Tue Oct 11 17:05:12 2011] [error] [client 192.168.1.2] File does not exist: /var/www/dav/majid/New Folder 
[Tue Oct 11 17:05:12 2011] [error] [client 192.168.1.2] The locks could not be queried for verification against a possible "If:" header.  [500, #0] 
[Tue Oct 11 17:05:12 2011] [error] [client 192.168.1.2] Could not open the lock database.  [500, #400] [Tue Oct 11 17:05:12 2011] [error] [client 192.168.1.2] (13)Permission denied: Could not open property database.  [500, #1]

Can anyone help? Another question is: Do we need `Options +Indexes` for WebDAV clients to list files and folders or it is only for web access using browser?

---------- Post updated at 07:34 PM ---------- Previous update was at 06:14 PM ----------

I removed this line:
Code:
DAVLockDB /var/www/DAVLock.db

and use the default configuration of Apache:
Code:
<IfModule mod_dav_fs.c>     # Location of the WebDAV lock database.     DAVLockDB /var/lib/dav/lockdb </IfModule>

It is now working perfectly. But I don't know the reason yet.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problems with Apache setup

I downloaded Apache 1.3.27.tar.gz into my SCO u/install directory. However, to begin with, I couldn't untar the file using the " tar xvf apache-1.3.27.tar.gz" command, so I used winzip from a windows computer on our network. Winzip untarred the file and I transferred the files to the SCO... (2 Replies)
Discussion started by: cstovall
2 Replies

2. UNIX for Dummies Questions & Answers

Problems with Apache setup

I posted a problem with the forum on 11/18/02. Unfortunately, I have been out of town. Today is the first chance I've had to try the suggestions that were made. Here is the output from the ls -l configure* command: -rw-r--r-- 1root sys 58230 May 21 2002 configure When I type " sh... (2 Replies)
Discussion started by: cstovall
2 Replies

3. UNIX for Dummies Questions & Answers

Create Folder and setup Apache

Hi, I'm a new person in here and also newbie. When I create a home folder for User and let them install any things they want in their own folder but there is one problem and i don't know how to resolved it. I post with a captured picture about this problem ... (1 Reply)
Discussion started by: cthinh
1 Replies

4. UNIX for Dummies Questions & Answers

How to setup Apache + mod_fcgi + suphp?

Hello. Could you please post an example of configuration of Apache + mod_fcgi + suphp? Till now I can get to work only either mod_fcgi or suphp, but not together. As I understand, suphp binary should be called from FCGIWrapper directive, but it always says, that SCRIPT_NAME variable is not... (0 Replies)
Discussion started by: FractalizeR
0 Replies

5. UNIX for Advanced & Expert Users

Testing privileges -lock lockfile /var/lock/subsys/..- Permission denied

Hi all, I have to test some user priviliges. The goal is to be sure that an unauthorized user can't restart some modules (ssh, mysql etc...). I'm trying to automate it with a shell script but in same cases I got the syslog broadcast message. Is there any way to simply get a return code... (3 Replies)
Discussion started by: Dedalus
3 Replies

6. Red Hat

apache httpd virtual hosts setup keep hitting the same VirtualHost

I'm trying to set up two virtual hosts. Here's my httpd config: <Directory /Users/userX/dev/sandbox-2> Order deny,allow deny from All Allow from localhost </Directory> NameVirtualHost 127.0.0.1 <VirtualHost 127.0.0.1> DocumentRoot "/Users/userX/dev/sandbox-2" ... (0 Replies)
Discussion started by: GlideK
0 Replies

7. AIX

Cannot get shared lock on database for rpm on AIX 6.1

Hello, I was trying to install python on aix and it was taking too long and I closed the terminal. Now when i issue the command rpm -qa instead of getting all the rpms installed I'm getting the following error. root:stud -> $ rpm -qa cannot get shared lock on database rpmQuery: rpmdbOpen()... (2 Replies)
Discussion started by: gaugeta
2 Replies

8. Web Development

Apache users from MySQL database

Hi team, How can I implement a users in MySQL database for Apache users, assuming that I'm using RHEL6. That is to say, how can I design this database and how let's Apache server know those user in this database. Thanks in advance.. (3 Replies)
Discussion started by: leo_ultra_leo
3 Replies

9. AIX

0514-516 Device Configuration Database Lock Service

Hello guys, on one of our AIX VIO LPARs I can not remove hdiskpower devices, which seemed to presented to the VIO in an incorrect way and behaviour (not all paths can be seen, pseudo device name is unknown etc.) Therefor I decided to deattach the hdiskpower device from PowerPath controll by: ... (5 Replies)
Discussion started by: tomek79
5 Replies

10. UNIX for Advanced & Expert Users

Can't open nodes-6379.conf in order to acquire a lock: Permission denied

I am getting error on redis server on linux 7.5 after change the default path /var/lib/redis to /redisdata, and enable cluster-enabled yes. It would be really appreciate if some one can check and suggest on this issue. error code: 1240:C 09 Sep 2018 13:53:51.058 # oO0OoO0OoO0Oo Redis is... (3 Replies)
Discussion started by: nadeemrafikhan
3 Replies
wfsctl(8)						    BSD System Manager's Manual 						 wfsctl(8)

NAME
wfsctl -- WebDAV File Sharing control utility SYNOPSYS
wfsctl command [arg] OVERVIEW
The wfsctl utility allows administrators to start, stop, and check the status of the WebDAV File Sharing service (WFS). It also allows admin- istrators to create and delete WebDAV share points. It operates by configuring the Apache httpd server. The wfsctl command requires root privileges. COMMANDS
wfsctl provides the following commands: start Enable the WFS configuration, and either start or restart the Apache web server to pick it up. If necessary, this action will create an SSL Identity matching the machine's host name as determined by the hostname(1) command, and place it in the System keychain. It will also update, if necessary, environment variable definitions for use by param- eterized httpd config files. (Note that starting the Apache web server is the equivalent of "apachectl start" which loads a launch job for the httpd process.) stop Disable the WFS configuration, and restart Apache if it's already running. status Display the status of WFS, either "enabled" or "disabled", whether or not Apache is running. shares Display existing WebDAV share points. share path Create a WebDAV share point for the specified file system path. unshare path | name Disable WebDAV for the share point at the specified file system path or share point name, and delete the share point if no other file sharing service (AFP or SMB) was enabled on that share point. diagnose Display detailed status of Apache and WebDAV-related processes. DETAILS
WebDAV File Sharing operates by: 1. Recognizing WebDAV clients when they send OPTIONS or PROPFIND directives 2. Requiring such clients to provide OD credentials 3. Assigning those authenticated users an HTTP cookie to recognize them as WebDAV clients 4. Launching an instance of the Apache httpd process on behalf of that user, configured as a WebDAV server 5. Reverse-proxying HTTP traffic to that user-specific instance of httpd, so that the WebDAV client (typically an iWork app on iOS) can access the home directory and share points on the server machine with privileges of the authenticated user 6. Recognizing share points that are marked as WebDAV share points. Depending on how Apache is configured, this can coexist with other Apache web service functions. NOTES
o WebDAV File Sharing requires SSL, and uses Basic authentication, with credentials that would otherwise be sent in the clear over the net- work. Also note that it uses Apache modules mod_ssl for SSL, and mod_authnz_od_apple for Basic authentication with OpenDirectory creden- tials. o The name "webdav" is reserved (it triggers special handling of URLs), so share point paths named "/webdav" or containing "webdav" as a subpath are not allowed. And folders named "webdav" within share points won't be usable. There are no restrictions on case variants such as "WebDAV", or other variants such as "webdav.d". o DropBox folders cannot be accessed via WebDAV File Sharing. CONFIGURABLE SETTINGS
Certain settings are kept in /etc/wfs/wfs.plist and are configurable by the administrator, including: ServerName The host name the Apache web server should use, and also the Common Name of the identity certificate. If this is not configured, or set to an empty string, the hostname(1) of the machine is used. ServerAddr The IP address the Apache web server should use to listen for HTTPS requests. Default is "*", which means all addresses. ServerPort The TCP port the Apache web server should use to listen for HTTPS requests. Default is the standard HTTPS port, 443. AccessGroup The Open Directory group allowed access to the WebDAV File Sharing service. The default is "everyone", which gives access to any authenticated user. Administrators can change this setting to restrict access further. Authenticated users will have, at most, the privileges they are normally allowed by file system permissions. There is no provision for guest access, so unauthenticated users have no access. SynthesizeSharePointForUserHomeDir Whether to allow remote WebDAV clients to see their home directory as a share point. Default is True. The Apache config file for WebDAV File Sharing is parameterized, and the httpd server is managed by the httpd-wrapper utility, which passes parameters to httpd. This is normally transparent, but note that to check the Apache config file syntax, do not use "apachectl configtest" or "httpd -t". Instead, use "httpd-wrapper -t". RETURN VALUES
wfsctl returns a status code of 0 for success. In the event of failure it returns a non-zero status, and may also dump additional diagnostic information. WEBDAV CLIENTS
o WebDAV clients must be properly configured to access WebDAV Shares on a remote host. o WebDAV clients include certain iOS apps, like Numbers, Keynote, and Pages, and the macOS Finder's Connect-to-Server. (Note that the iOS Files app does not find WebDAV File Sharing locations.) o WebDAV clients must usually be configured with a full URL of the host, with a scheme of https (since an http->https redirect is not gen- erally compatible with WebDAV operations). It's not necessary to specify /webdav in the path. So for example, the "Server Name" might be specified as: https://hostname.example.com o The configurable virtual host behavior provided by macOS Server is not available, so WebDAV clients may not be able to use alternate host names in their URLs. FILES
/etc/wfs/httpd_webdavsharing.conf The parameterized Apache config file for the main instance of httpd /etc/wfs/httpd_webdavsharing_template.conf The parameterized Apache config file for the user-specific instances of httpd /etc/wfs/httpd_webdavsharing_sharepoints.conf The Apache config file providing directives specific to each share point; dynamically generated when share points are modified by wfsctl /etc/wfs/wfs.plist The file where admin-configurable settings for WFS are stored. /Library/Server/Web/Config/apache2/WebConfigProperties.plist If macOS Server is installed and promoted, WebDAVSharing settings in this file take precedence over those in /etc/wfs/wfs.plist. /etc/apache2/env.plist The file where environment variable definitions are managed automatically; these variables are passed to httpd for use in parameter- ized config files. /Library/Logs/WebDAVFileSharing.log The main WebDAV File Sharing log file /etc/apache2/other/httpd_webdavsharing.conf A symlink seen by Apache when WebDAV File Sharing is enabled. When WebDAV File Sharing is disabled, this symlink is moved aside. /var/run/webdavsharing/<username>/ A directory created on the behalf of each authenticated user to store user-specific WebDAV File Sharing logs. /usr/share/sandbox/wfs.sb The parameterized sandbox profile for user-specific httpd instances. /etc/wfs/wfs.sb The dynamically generated portion of the sandbox profile SERVER APP
When macOS Server is installed and promoted, WebDAV File Sharing is reconfigured to support the WebDAV behaviors presented by Server: 1. macOS Server provides HTTP-based services (for Profile Manager) on standard HTTP/S TCP ports 80 and 443. So to avoid port conflict, the desktop Apache configuration (including the configuration for WebDAV File Sharing) is switched to port 81, on localhost only, and WFS traffic is reverse proxied to localhost:81. 2. macOS Server manages its own SSL certificates, and provides the SSL endpoint. So the desktop Apache configuration for WebDAV File Shar- ing is switched to non-SSL. When macOS Server is installed and promoted, it is still possible to use wfsctl to manage WebDAV share points, e. g.: sudo wfsctl share /Volumes/Data/Share1 3. Any share points created in the UI on versions of macOS Server that predate High Sierra remain across updates, and those that were marked as WebDAV share points should continue to be available after the update to High Sierra, whether or not macOS Server is installed. When macOS Server is removed or demoted, the port changes and SSL changes made at Server promotion time are reversed. SEE ALSO
httpd(8) httpd-wrapper(8) macOS Sept. 20, 2017 macOS
All times are GMT -4. The time now is 02:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy