Setup Ceph object storage with S3

robert.s

Member
Sep 16, 2021
7
0
6
39
Hello, I'm looking for help on below points
1) Installing and configuring the RADOS Gateway
2) How to create a RADOS Gateway user for the S3 access
3) Configuring DNS & S3 client to access ceph object storage.

Update: I followed steps given in below post but not able to access gateway on port 7480
Adding S3 capabilities to Proxmox
 
Last edited:
client.radosgw.node1.log

2021-09-20T11:18:06.370+0530 7f6950e326c0 0 ceph version 16.2.5 (9b9dd76e12f1907fe5dcc0c1fadadbb784022a42) pacific (stable), process radosgw, pid 4490
2021-09-20T11:18:06.370+0530 7f6950e326c0 0 framework: beast
2021-09-20T11:18:06.370+0530 7f6950e326c0 0 framework conf key: port, val: 7480
2021-09-20T11:18:06.370+0530 7f6950e326c0 1 radosgw_Main not setting numa affinity
2021-09-20T11:18:06.370+0530 7f6950e326c0 0 pidfile_write: ignore empty --pid-file
2021-09-20T11:18:16.062+0530 7f6950e326c0 0 framework: beast
2021-09-20T11:18:16.062+0530 7f6950e326c0 0 framework conf key: ssl_certificate, val: config://rgw/cert/$realm/$zone.crt
2021-09-20T11:18:16.062+0530 7f6950e326c0 0 framework conf key: ssl_private_key, val: config://rgw/cert/$realm/$zone.key
2021-09-20T11:18:16.062+0530 7f6950e326c0 0 starting handler: beast
2021-09-20T11:18:16.090+0530 7f6950e326c0 1 mgrc service_daemon_register rgw.174198 metadata {arch=x86_64,ceph_release=pacific,ceph_version=ceph version 16.2.5 (9b9dd76e12f1907fe5dcc0c1fadadbb784022a42) pacific (stable),ceph_version_short=16.2.5,cpu=Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz,distro=debian,distro_description=Debian GNU/Linux 11 (bullseye),distro_version=11,frontend_config#0=beast port=7480,frontend_type#0=beast,hostname=node1,id=radosgw.node1,kernel_description=#1 SMP PVE 5.11.22-8 (Fri, 27 Aug 2021 11:51:34 +0200),kernel_version=5.11.22-4-pve,mem_swap_kb=6422524,mem_total_kb=8111300,num_handles=1,os=Linux,pid=4499,zone_id=f136cb48-aac1-4c4d-97f4-16a0de127ea2,zone_name=default,zonegroup_id=56f08066-6900-4104-977c-32fc552cdb0c,zonegroup_name=default}
2021-09-20T11:24:41.271+0530 7f68c47e0700 1 failed to read header: bad method
2021-09-20T11:24:41.271+0530 7f68c47e0700 1 ====== req done http_status=400 ======
2021-09-20T11:24:50.243+0530 7f68c4fe1700 1 ====== starting new request req=0x7f694c14d820 =====
2021-09-20T11:24:50.243+0530 7f68bc7d0700 1 req 1 0.000000000s op->ERRORHANDLER: err_no=-2002 new_err_no=-2002
2021-09-20T11:24:50.243+0530 7f68b8fc9700 1 ====== req done req=0x7f694c14d820 op status=0 http_status=404 latency=0.000000000s ======
2021-09-20T11:24:50.243+0530 7f68b8fc9700 1 beast: 0x7f694c14d820: 192.168.42.1 - anonymous [20/Sep/2021:11:24:50.243 +0530] "GET / HTTP/1.1" 404 217 - "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0" - latency=0.000000000s
2021-09-20T11:24:50.311+0530 7f68bf7d6700 1 ====== starting new request req=0x7f694c14d820 =====
2021-09-20T11:24:50.311+0530 7f68bf7d6700 1 req 2 0.000000000s op->ERRORHANDLER: err_no=-2002 new_err_no=-2002
2021-09-20T11:24:50.311+0530 7f68b27bc700 1 ====== req done req=0x7f694c14d820 op status=0 http_status=404 latency=0.000000000s ======
2021-09-20T11:24:50.311+0530 7f68b27bc700 1 beast: 0x7f694c14d820: 192.168.42.1 - anonymous [20/Sep/2021:11:24:50.311 +0530] "GET /favicon.ico HTTP/1.1" 404 217 "http://node1:7480/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0" - latency=0.000000000s
2021-09-20T11:25:55.314+0530 7f68b77c6700 1 failed to read header: The socket was closed due to a timeout
2021-09-20T11:25:55.314+0530 7f68ad7b2700 1 ====== req done http_status=400 ======
2021-09-20T11:27:23.777+0530 7f68af7b6700 1 ====== starting new request req=0x7f694c14d820 =====
2021-09-20T11:27:23.777+0530 7f689ef95700 1 ====== req done req=0x7f694c14d820 op status=0 http_status=200 latency=0.000000000s ======
2021-09-20T11:27:23.777+0530 7f689ef95700 1 beast: 0x7f694c14d820: 192.168.42.1 - anonymous [20/Sep/2021:11:27:23.777 +0530] "GET / HTTP/1.1" 200 231 - "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0" - latency=0.000000000s
2021-09-20T11:27:23.833+0530 7f68ab7ae700 1 ====== starting new request req=0x7f694c14d820 =====
2021-09-20T11:27:23.833+0530 7f6896f85700 1 req 4 0.000000000s op->ERRORHANDLER: err_no=-2002 new_err_no=-2002
2021-09-20T11:27:23.833+0530 7f6895f83700 1 ====== req done req=0x7f694c14d820 op status=0 http_status=404 latency=0.000000000s ======
2021-09-20T11:27:23.833+0530 7f6895f83700 1 beast: 0x7f694c14d820: 192.168.42.1 - anonymous [20/Sep/2021:11:27:23.833 +0530] "GET /favicon.ico HTTP/1.1" 404 223 "http://192.168.42.131:7480/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:92.0) Gecko/20100101 Firefox/92.0" - latency=0.000000000s
2021-09-20T11:28:28.836+0530 7f6898788700 1 failed to read header: The socket was closed due to a timeout
2021-09-20T11:28:28.836+0530 7f6898788700 1 ====== req done http_status=400 ======
2021-09-20T11:35:00.366+0530 7f694fa57700 -1 received signal: Terminated from start-stop-daemon --stop -x /bin/radosgw --oknodo -R 120 (PID: 9987) UID: 0
2021-09-20T11:35:00.366+0530 7f694fa57700 1 handle_sigterm
2021-09-20T11:35:00.366+0530 7f694fa57700 1 handle_sigterm set alarm for 120
2021-09-20T11:35:00.366+0530 7f6950e326c0 -1 shutting down
2021-09-20T11:35:00.606+0530 7f6950e326c0 1 final shutdown
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!