23 Feb
2021
23 Feb
'21
5:47 p.m.
I increased the debug level to 20. There isn't anything additional being written:
2021-02-23 16:26:38.736642 7£2c45£3700 -1 Initialization timeout, failed to initialize
2021-02-23 16:26:38.931400 7f4d7bf4a000 0 deferred set uid:gid to 167:167 (ceph:ceph)
2021-02-23 16:26:38.931707 7f4d7bf4a000 0 ceph version 12.2.8-128.1. TEST. bz1742993.el7cp
(87ba41fa7b3bcb79d916fb0ca41a9dd90eb877f8)
luminous (stable), process radosgw, pid 7169
2021-02-23 16:31:38.931973 7f4d6b8e5700 -1 Initialization timeout, failed to initialize
2021-02-23 16:31:39.191898 7fa2fae31000 deferred set uid:gid to 167:167 (ceph:ceph)
2021-02-23 16:31:39.192119 7fa2fae31000 0 ceph version 12.2.8-128.1. TEST.bz1742993.el7cp
(87ba41fa7b3bcb79d916fb0ca41a9dd90eb877f8)
luminous (stable), process radosgw, pid 7204
Thank you,
Mathew
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, February 23, 2021 10:57 AM, Janne Johansson <icepic.dz(a)gmail.com>
wrote:
Den tis 23 feb. 2021 kl 16:53 skrev Mathew Snyder
mathew.snyder(a)protonmail.com:
We have a Red Hat installation of Luminuous (full
packages version: 12.2.8-128.1). We're experiencing an issue where the ceph-radosgw
service will timeout during initialization and cycle through attempts every five minutes
until it seems to just give up. Every other ceph service starts successfully.
I tried looking at the health of the cluster, but anytime I run a command, whether ceph
or radosgw-admin just to see a list of users, it seems to time out as well.
I've used strace when attempting to start radosgw directly and was presented with a
missing keyring error. I would be inclined to think that might be the problem, but
wouldn't that also impact all of the other services?
No, a missing rgw key would stop only it, and the radosgw-admin
command (if run on a box without a global admin key)
I haven't been able to find anything in the
logs that would lead me down any paths. Everything I've looked at (journalctl,
/var/log/messages, /var/log/ceph/ceph-rgw-server.log) all just say the same thing: the
service attempted to start, it failed to initialize, entered a failed state, service
stopped. This repeats.
See if you can bump the debug log level of the radosgw when starting it.
https://access.redhat.com/solutions/2085183
and
https://docs.ceph.com/en/latest/rados/troubleshooting/log-and-debug/#rados-…
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
May the most significant bit of your life be positive.