httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bruno.roh...@css.ch
Subject [users@httpd] Antwort: Re: [users@httpd] cannot write to mod_dav, locks cannot be queried?
Date Fri, 20 Feb 2004 13:42:12 GMT
(cd libneon && make) || exit 1
make[1]: Entering directory `/tools/usr_local/src/litmus-0.9.4/libneon'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/tools/usr_local/src/litmus-0.9.4/libneon'
gcc  -o basic src/basic.o -L. -ltest -Llibneon -lneon -lnsl -lsocket 
-L/usr/kerberos/lib -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lsocket 
-lnsl -lresolv -R/usr/lib -lxml2 -lz -lpthread -lm -lsocket -lnsl 
lib/getopt.o lib/getopt1.o
gcc  -o copymove src/copymove.o -L. -ltest -Llibneon -lneon -lnsl -lsocket 
 -L/usr/kerberos/lib -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lsocket 
-lnsl -lresolv -R/usr/lib -lxml2 -lz -lpthread -lm -lsocket -lnsl 
lib/getopt.o lib/getopt1.o
gcc  -o props src/props.o -L. -ltest -Llibneon -lneon -lnsl -lsocket 
-L/usr/kerberos/lib -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lsocket 
-lnsl -lresolv -R/usr/lib -lxml2 -lz -lpthread -lm -lsocket -lnsl 
lib/getopt.o lib/getopt1.o
gcc  -o locks src/locks.o -L. -ltest -Llibneon -lneon -lnsl -lsocket 
-L/usr/kerberos/lib -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lsocket 
-lnsl -lresolv -R/usr/lib -lxml2 -lz -lpthread -lm -lsocket -lnsl 
lib/getopt.o lib/getopt1.o
gcc  -o http src/http.o -L. -ltest -Llibneon -lneon -lnsl -lsocket 
-L/usr/kerberos/lib -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lsocket 
-lnsl -lresolv -R/usr/lib -lxml2 -lz -lpthread -lm -lsocket -lnsl 
lib/getopt.o lib/getopt1.o
-> running `basic':
 0. init.................. pass
 1. begin................. FAIL (Could not create new collection 
`/web_iet/litmus/' for tests: 500 Internal Server Error
Server must allow `MKCOL /web_iet/litmus/' for tests to proceed)
<- summary for `basic': of 2 tests run: 1 passed, 1 failed. 50.0%
See debug.log for network/debug traces.
make: *** [check] Error 1 

Apache Log Conf File:
<VirtualHost ietadmin.css.ch:80>
        ServerName      ietadmin.css.ch
        DocumentRoot    /intradata/htdocs/web_iet
        ErrorLog /tools/apache/current/logs/ietadmin.css.ch/error_log
        CustomLog /tools/apache/current/logs/ietadmin.css.ch/access_log 
combined
        <Location />
        DAV on
        <Limit POST PUT DELETE CONNECT OPTIONS PATCH PROPFIND PROPPATCH 
MKCOL COPY MOVE LOCK UNLOCK>
                AuthType        Basic
                AuthName        IET
                AuthUserFile    /tools/apache/current/conf/ietusers
                require user  xxxx
        </Limit> 
        </Location>
        DAVLockDB       /tools/apache/current/tmp/ietadmin.css.ch/LockDB
</VirtualHost>

Thanks

Bruno
___________________________________________________________________





Saqib Ali <saqib@seagate.com>
22.01.2004 17:50
Bitte antworten an users

 
        An:     users@httpd.apache.org
        Kopie:  bruno.rohrer@css.ch, afm@othello.ch
        Thema:  Re: [users@httpd] cannot write to mod_dav, locks cannot be queried?


Bruno,

Please run the litmus test ( http://www.webdav.org/neon/litmus/ ) and post
the results back on this mailing list

Thanks

Saqib Ali
-------------
http://validate.sf.net <---- DocBook XML -> HTML Convertor



On Thu, 22 Jan 2004 bruno.rohrer@css.ch wrote:

> Hello everyone,
>
> we experience some problems with mod_dav in httpd2.0.48. Whenever we try
> to
> publish a file, we find the following error message in the error_log:
>
> The locks could not be queried for verification against a possible "If:"
> header.
>
> We have tried several versions of httpd (2.0.44 works for us on some 
other
> machine,
> but 2.0.47-48 never do), and we have switched DBM libraries several 
times
> (from
> sdbm to ndbm to gdbm). The error remains the same.
>
> From some seemingly related messages found in some mailing list 
archives,
> we
> haven't been able to fix the problem. Since it doesn't really matter 
what
> type
> of client we use, it is difficult to argue that this was not an Apache
> problem.
> But we are clueless enough to not understand what causes it. The LockDB
> files are around, and are writeable by the Apache processes, the
> directories are
> readable, and allow/deny directives are currently as liberal as 
possible,
> everybody
> could modify the pages right now.
>
> Can someone shed some light what could be wrong with mod_dav, and how
> to fix this? Thanks in advance
>
>                                 Bruno Rohrer
> __
>
> CSS Versicherung
> Bruno Rohrer
> Rösslimattstrasse 40, CH-6002 Luzern
> bruno.rohrer@css.ch

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
"   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org




Mime
View raw message