Closed foxpluto closed 2 weeks ago
Reading in the ceph cluster log I found the error which cause the problem:
2024-08-19 12:06:09 | 2024-08-19T10:06:09.752+0000 7f78235f1640 1 beast: 0x7f77f959c710: 10.0.25.12 - - [19/Aug/2024:10:06:09.752 +0000] "PUT /deb/focal/test/content/vol-33/chap-33/05015904-5e8b-431d-965e-fcf1a3e44588.properties HTTP/1.0" 403 219 - "aws-sdk-java/1.12.658 Linux/6.8.0-40-generic OpenJDK_64-Bit_Server_VM/17.0.12+7-LTS java/17.0.12 vendor/Red_Hat,_Inc. cfg/retry-mode/legacy" - latency=0.000000000s
-- | --
It seems that my cluster refuse with a 403 error the PUT of properties files.
The data file is in that directory but was written using a POST not a PUT.
I have no idea why ceph doesn't allow Nexus to use the PUT, I have double checked the user permissions and they seems to be ok.
I'll keep investigate
Actually some others PUT request goes fine:
2024-08-19 12:06:07 | 2024-08-19T10:06:07.660+0000 7f782c603640 1 beast: 0x7f77f959c710: 10.0.25.12 - fox [19/Aug/2024:10:06:07.468 +0000] "PUT /deb/focal/test/content/vol-33/chap-33/05015904-5e8b-431d-965e-fcf1a3e44588.bytes?uploadId=2%7E0P4_s4Rdg6ahwlONOhZDwT4Vs1nIQo9&partNumber=9 HTTP/1.0" 200 6119516 - "aws-sdk-java/1.12.658 Linux/6.8.0-40-generic OpenJDK_64-Bit_Server_VM/17.0.12+7-LTS java/17.0.12 vendor/Red_Hat,_Inc. cfg/retry-mode/legacy" - latency=0.191999570s
-- | --
doesn't seems a permission problem.
@foxpluto This isn't a supported feature of Repository, but we are monitoring demand to see when we reach critical mass to push it over the threshold to get onto the roadmap. I'm classifying this as an 'enhancement' for that reason.
Hi,
thanks for the reply, I had some other test and i found out the problem is an Nginx reverse proxy in front of my ceph repository. Using ceph without nginx it works perfectly. Do you have some documentation on how to configure reverse proxy in front of S3 ? My suspect is that Nginx drop some header and those are required to nexus.
Regards, S.
I have configured a deb repo, and I have tried first to configure the repo via a Blob Store based on file, the result is a fully functional deb repo. Now I would like to use a Ceph S3 storage I have exposed to internet which is an AWS S3 compatible storage which I already use with other software (i.e. CyberDuck works and others.) The configurations are:
The creation went fine and i see on the bucket the creation of 2 files:
then I try to upload a deb file (the same deb file which works if the Blob Store is based on file) with curl:
The upload doesn't goes fine and I receive a 500 Internal server error.
Looking at the nexus log I found:
I have tried many different options but the error is alwayse the same.