Hi,
Conclusion of the story... It seems I made something wrong when
recreating .rgw.root, ending up with a zonegroup "default" and a zone
"default" being created (in addition to the zonegroup/zone I explicitely
created). I guess it is because I forgot a --default option when
creating the zone or zonegroup, resulting in an incorrect configuration
(with the side effect of making impossible to update the period when
trying to fix the problem).
I guess it is difficult to provide more diagnostics about why the RGW
fails to start properly (in fact stops right after starting) but it
makes diagnostics of such trivial misconfiguration difficults...
Cheers,
Michel
Le 29/09/2022 à 14:04, Michel Jouvin a écrit :
Hi,
Unfortunately it was a wrong track. The problem remains the same, with
the same error messages, on another host with only one network address
in the Ceph cluster public network. BTW, "ceph shell --name
rgw_daemon" works and from the shell I can use radosgw-admin and ceph
command, suggesting that it is not the problem as both containers have
a similar network configuration (this is the so-called "host"
configuration that basically says there is no network virtualization
and that you just use what the host has).
I think I ran out of any idea where to look at. I forgot to mention
that SELinux is in permissive mode on this host so it is not the
source of problem either.
Thanks in advance if one of you has something to suggest. The absence
of any Rados-related errors in the logs doesn't help to identify the
problem...
Cheers,
Michel
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
