Le 2023-02-06 14:11, Eugen Block a écrit :
What does the active mgr log when you try to access the dashboard?
Please paste your rgw config settings as well.
Ah, Sorry to hijack, but I also can't access Object Storage menus in the
Dashboard since upgrading from 16.2.10 to 16.2.11.
Here are the MGR logs :
fcadmin@fidcllabs-oct-01:~$ sudo grep 8080
/var/log/ceph/ceph-mgr.fidcllabs-oct-01.log
2023-02-06T08:12:58.179+0000 7ffad4910700 0 [dashboard INFO rgw_client]
Found RGW daemon with configuration: host=fidcllabs-oct-03, port=8080,
ssl=False
2023-02-06T08:12:58.179+0000 7ffad4910700 0 [dashboard INFO rgw_client]
Found RGW daemon with configuration: host=fidcllabs-oct-01, port=8080,
ssl=False
2023-02-06T08:12:58.179+0000 7ffad4910700 0 [dashboard INFO rgw_client]
Found RGW daemon with configuration: host=fidcllabs-oct-02, port=8080,
ssl=False
2023-02-06T08:12:58.275+0000 7ffad4910700 0 [dashboard ERROR
rest_client] RGW REST API failed GET, connection error
(url=http://fidcllabs-oct-03:8080/admin/metadata/user?myself): [errno:
111] Connection refused
urllib3.exceptions.MaxRetryError:
HTTPConnectionPool(host='fidcllabs-oct-03', port=8080): Max retries
exceeded with url: /admin/metadata/user?myself (Caused by
NewConnectionError('<urllib3.connection.HTTPConnection object at
0x7ffac1e75160>: Failed to establish a new connection: [Errno 111]
Connection refused',))
requests.exceptions.ConnectionError:
HTTPConnectionPool(host='fidcllabs-oct-03', port=8080): Max retries
exceeded with url: /admin/metadata/user?myself (Caused by
NewConnectionError('<urllib3.connection.HTTPConnection object at
0x7ffac1e75160>: Failed to establish a new connection: [Errno 111]
Connection refused',))
The hostname is resolvable, but not on the same IP (management network)
than my RGW endpoints (public network).
In other cluster still on 16.2.10, I can see IPs in the corresponding
logs, not the hostname.
--
Gilles
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
