search

rucio / containers

Containers for Rucio
Apache License 2.0
9 stars 55 forks source link

webdav issue on PUT #265

Closed elehcim closed 4 months ago

elehcim commented 11 months ago

Hello, I have a k8s installation with a webdav rse using the webdav container.

If I try to do rucio upload of a file to the webdav rse I get this error

2023-11-08 16:05:59,619 WARNING Upload attempt failed
2023-11-08 16:05:59,619 INFO    Exception: RSE does not support requested operation.
Details: The requested service is not available at the moment.
Details: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

whereas in the webdav pod:

BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
BDB0004 fop_read_meta: /var/lib/dav/DavLock: unexpected file type or format
[Wed Nov 08 15:05:57.797496 2023] [dav:error] [pid 13:tid 140338500978432] [client 10.42.0.0:21132] Unable to PUT new contents for /rucio/test/c1/ed/p1.rucio.upload.  [403, #0]
[Wed Nov 08 15:05:57.797496 2023] [dav:error] [pid 13:tid 140338500978432] [client 10.42.0.0:21132] Unable to PUT new contents for /rucio/test/c1/ed/p1.rucio.upload.  [403, #0]
[Wed Nov 08 15:05:57.797519 2023] [dav:error] [pid 13:tid 140338500978432] (2)No such file or directory: [client 10.42.0.0:21132] An error occurred while opening a resource.  [409, #0]
[Wed Nov 08 15:05:57.797519 2023] [dav:error] [pid 13:tid 140338500978432] (2)No such file or directory: [client 10.42.0.0:21132] An error occurred while opening a resource.  [409, #0]
[Wed Nov 08 15:05:57.797598 2023] [:error] [pid 13:tid 140338500978432] AH: ctx->lock_filename: /test.lock.
[Wed Nov 08 15:05:57.797598 2023] [:error] [pid 13:tid 140338500978432] AH: ctx->lock_filename: /test.lock.
[Wed Nov 08 15:05:57.797647 2023] [:error] [pid 13:tid 140338500978432] AH: Unable to open lock file /test.lock.
[Wed Nov 08 15:05:57.797647 2023] [:error] [pid 13:tid 140338500978432] AH: Unable to open lock file /test.lock.

I saw this issue: https://github.com/docker-library/httpd/issues/201

Do you have any idea about how to workaround this issue?

erlingstaff commented 4 months ago

Hey, sorry for not responding to this earlier. However, this was inadvertently fixed a few months ago in this commit, in which the webdav container was changed to use ubuntu:noble instead of httpd:latest, along with a new Dockerfile. At the time of this issue being filed, httpd:latest pointed to httpd@sha256:4e24356b4b0aa7a961e7dfb9e1e5025ca3874c532fa5d999f13f8fc33c09d1b7 (can be found here). By pulling and using the old httpd image, as well as the old Dockerfile, I reproduced the issue you encountered, but could not reproduce it on the new webdav container.

In the image below, web2 is the old httpd image and old Dockerfile, while web1 uses the new Dockerfile and ubuntu:noble image. Closing this issue.

image