It would be cool, actually, to have the metrics working in 18.2.2, for IPv6
only
Otherwise, everything works fine on my side.
Cordialement,
*David CASIER*
Le jeu. 25 janv. 2024 à
Gotcha !
I've got the point, after restarting the CA certificate creation with :
ceph restful create-self-signed-cert
I get this error :
Module 'cephadm' has failed: Expected 4 octets in
'fd30:::0:1101:2:0:501'
*Ouch 4 octets = IP4 address expected... some nice code in perspective.*
I
According to sources, the certificates are generated automatically at
startup. Hence my question if the service started correctly.
I also had problems with IPv6 only, but I don't immediately have more info
Cordialement,
*David CASIER*
IPv6 only : Yes, the -ms_bind_ipv6=true is already set-
I had tried a rotation of the keys for node-exporter and I get this :
2024-01-23T16:43:56.098796+ mgr.srv06-r2b-fl1.foxykh (mgr.342408) 87074
: cephadm [INF] Rotating authentication key for node-exporter.srv06-r2b-fl1
Is the cephadm http server service starting correctly (in the mgr logs)?
IPv6 ?
Cordialement,
*David CASIER*
Le mar. 23 janv. 2024 à 16:29, Nicolas FOURNIL
a écrit :
> Hello,
Hello,
Thanks for advice but Prometheus cert is ok, (Self signed) and tested with
curl and web navigator.
it seems to be the "Service discovery" certificate from cephadm who is
missing but I cannot figure out how to set it.
There's in the code a function to create this certificate inside the
Hello Nicolas,
I don't know if it's an update issue.
If this is not a problem for you, you can consider redeploying
grafana/prometheus.
It is also possible to inject your own certificates :
https://docs.ceph.com/en/latest/cephadm/services/monitoring/#example
