EGI check_webdav fails on https://eos.grif.fr:11000

1

Dear Elvin
check_webdav ( src · master · lcgdm / nagios-plugins-webdav · GitLab)
on EGI fails on https://eos.gri.fr:11000 http port with :

240415 13:52:46 time=1713181966.738609 func=Get level=INFO logid=static… unit=mgm@grid-72100.ijclab.in2p3.fr:1094 tid=00007f171f833700 source=HttpHandler:335 tident= sec=(null) uid=99 gid=99 name=- geo=“” method=GET dir=/eos/grif/dteam/
240415 13:52:46 time=1713181966.739259 func=HttpError level=INFO logid=static… unit=mgm@grid-72100.ijclab.in2p3.fr:1094 tid=00007f171f833700 source=HttpServer:401 tident= sec=(null) uid=99 gid=99 name=- geo=“” errc=403, retcode=403 errmsg=“Browsing is disabled and no index attribute is defined!”

some where thsi probe makes a GET DIR in test directory
and fails
mapping and acl are ok
I do not uderstand from where came the issue !
FYI
best
e.v.

2

Hi Emmanouil,

Yes, browsing is disabled by default but you can easily enable it by setting the follwing xattr on the directory which is receiving the request. For example in our ATLAS instance the following config provides the required functionality:

[root@eosatlas-ns-ip563 (mgm:master mq:master) ~]$ eos attr ls  /eos/atlas/opstest/egi/ | grep "index"
sys.http.index="/eos/atlas/opstest/egi/index.txt"
[root@eosatlas-ns-ip563 (mgm:master mq:master) ~]$ xrdcp "root://localhost//eos/atlas/opstest/egi/index.txt" -
index.txt
[10B/10B][100%][==================================================][10B/s]

Cheers,
Elvin

3

Hello Elvin
thanks
which process creates and fill the index.txt
we have ot write a kind of trigger ?
best
e.v.

4

Hi Emmanouil,

Just for consistency, through, I already replied to this in person: you can create the xattr and put a dummy file in place just as in the example I’ve given above and the probe should be happy.

Cheers,
Elvin

5

Hello Elvin
thank you for your hint it works !
just fro curl GET on the DIRECTORY
e.g.
curl -L -v --capath /etc/grid-security/certificates --cert $X509_USER_PROXY --cacert $X509_USER_PROXY --key $X509_USER_PROXY -X “GET” $ENDPOINT
I got
< HTTP/1.1 307 TEMPORARY_REDIRECT
< Connection: Keep-Alive
< Server: XrootD/5.5.10
< Content-Length: 0
< Date: Mon, 15 Apr 2024 18:25:02 GMT
< Location: /eoss/grif/opstest/egi/index.txt
< X-Accel-Redirect: /eos/grif/opstest/egi/index.txt
< X-Sendfile: /eos/grif/opstest/egi/index.txt
<
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0

GET /eoss/grif/opstest/egi/index.txt HTTP/1.1
User-Agent: curl/7.29.0
Host: eos.grif.fr:11000
Accept: /

a strange path /eoss/grif/opstest/egi/index.txt
I solve this as I crate a soft link eoss - ->eos
but I do not knwo from where came this

thanks
e.v.

6

Hi Emmanouil,

This is a misconfiguration of the probe, in the sense that it targets the wrong path. You should ask to have this fixed. Then you do not need the complication with the symlink.

Cheers,
Elvin