Giters

ceph / ceph-container

Docker files and images to run Ceph in containers

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

RadosGW Initialization timeout, failed to initialize

evolvtyon opened this issue · comments

commented

Is this a bug report or feature request?

  • Bug Report

Bug Report

What happened: Trying to deploy rgw with ceph daemon container image version 7.0.1

What you expected to happen: Successfully initialize rgw and obtain lock

How to reproduce it (minimal and precise):
I'm deploying this in a vCenter Server VM

Have 3 vDisks attached, each with 100GB

/dev/sdc
/dev/sdd
/dev/sde

They are mounted respectively at:

/var/lib/ceph/ceph-0
/var/lib/ceph/ceph-1
/var/lib/ceph/ceph-2

Major issue: cannot initialize calling OSD as there is no ceph-disk binary.
Configuring it manually with ceph-osd -i $ID says :

2023-01-31T15:32:21.773+0000 7f05a9d17700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2]
failed to fetch mon config (--no-mon-config to skip)

After following steps in https://docs.ceph.com/en/latest/install/manual-deployment/. Only way I can make OSDs work and bring them up is if I run them directly in the /root partition (so not a different attached disk) but even so, cannot bring rgw up:
Loops with:

2023-01-31T15:35:07.821+0000 7ff59b65d5c0  1 -- <IP_ADDR>:0/1981171637 --> [v2:<IP_ADDR>:3300/0,v1:<IP_ADDR>:6789/0] -- mon_subscribe({osdmap=16}) v3 -- 0x55b32b024000 con 0x55b32a198c00
2023-01-31T15:35:07.821+0000 7ff59b65d5c0  5 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:3300/0,v1:<IP_ADDR>:6789/0] conn(0x55b32a198c00 0x55b32a2deb00 secure :-1 s=READY pgs=696 cs=0 l=1 rev1=1 crypto rx=0x55b32af4ed50 tx=0x55b32a2127e0 comp rx=0 tx=0).send_message enqueueing message m=0x55b32b024000 type=15 mon_subscribe({osdmap=16}) v3
2023-01-31T15:35:07.821+0000 7ff5991dd700  5 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:3300/0,v1:<IP_ADDR>:6789/0] conn(0x55b32a198c00 0x55b32a2deb00 secure :-1 s=READY pgs=696 cs=0 l=1 rev1=1 crypto rx=0x55b32af4ed50 tx=0x55b32a2127e0 comp rx=0 tx=0).write_message sending message m=0x55b32b024000 seq=5 mon_subscribe({osdmap=16}) v3
2023-01-31T15:35:07.825+0000 7ff5989dc700  1 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] conn(0x55b32a199800 0x55b32a2df600 unknown :-1 s=BANNER_CONNECTING pgs=0 cs=0 l=1 rev1=0 crypto rx=0 tx=0 comp rx=0 tx=0)._handle_peer_banner_payload supported=3 required=0
2023-01-31T15:35:07.825+0000 7ff5989dc700  5 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] conn(0x55b32a199800 0x55b32a2df600 unknown :-1 s=HELLO_CONNECTING pgs=0 cs=0 l=1 rev1=1 crypto rx=0 tx=0 comp rx=0 tx=0).handle_hello received hello: peer_type=16 peer_addr_for_me=v2:<IP_ADDR>:57512/0
2023-01-31T15:35:07.825+0000 7ff5989dc700  5 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] conn(0x55b32a199800 0x55b32a2df600 unknown :-1 s=HELLO_CONNECTING pgs=0 cs=0 l=1 rev1=1 crypto rx=0 tx=0 comp rx=0 tx=0).handle_hello getsockname says I am <IP_ADDR>:57512 when talking to v2:<IP_ADDR>:6800/80
2023-01-31T15:35:07.825+0000 7ff5989dc700  5 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] conn(0x55b32a199800 0x55b32a2df600 unknown :-1 s=AUTH_CONNECTING pgs=0 cs=0 l=1 rev1=1 crypto rx=0 tx=0 comp rx=0 tx=0).handle_auth_reply_more auth reply more len=32
2023-01-31T15:35:07.825+0000 7ff5989dc700  5 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] conn(0x55b32a199800 0x55b32a2df600 secure :-1 s=SESSION_CONNECTING pgs=0 cs=0 l=1 rev1=1 crypto rx=0x55b32a223f80 tx=0x55b32a212b40 comp rx=0 tx=0).send_client_ident sending identification: addrs=<IP_ADDR>:0/1981171637 target=v2:<IP_ADDR>:6800/80 gid=4778 global_seq=2 features_supported=3f01cfbf7ffdffff features_required=800000000001000 flags=1 cookie=0
2023-01-31T15:35:07.825+0000 7ff5989dc700  5 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] conn(0x55b32a199800 0x55b32a2df600 secure :-1 s=SESSION_CONNECTING pgs=0 cs=0 l=1 rev1=1 crypto rx=0x55b32a223f80 tx=0x55b32a212b40 comp rx=0 tx=0).handle_server_ident received server identification: addrs=[v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] gid=4677 global_seq=41 features_supported=3f01cfbf7ffdffff features_required=800000000000000 flags=1 cookie=0
2023-01-31T15:35:07.825+0000 7ff5989dc700  1 --2- <IP_ADDR>:0/1981171637 >> [v2:<IP_ADDR>:6800/80,v1:<IP_ADDR>:6801/80] conn(0x55b32a199800 0x55b32a2df600 secure :-1 s=READY pgs=41 cs=0 l=1 rev1=1 crypto rx=0x55b32a223f80 tx=0x55b32a212b40 comp rx=0 tx=0).ready entity=mgr.4677 client_cookie=0 server_cookie=0 in_seq=0 out_seq=0

could really use some guidance on this...

Environment:

  • OS (e.g. from /etc/os-release): SUSE Linux Enterprise Server 15 SP3
  • Kernel (e.g. uname -a): Linux 5.3.18-57-default
  • Docker version (e.g. docker version): 20.10.9-ce
  • Ceph version (e.g. ceph -v): 17.2.4 quincy stable
commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

commented

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.