The cephadm.log should show some details why it fails to deploy the
daemon. If there's not much, look into the daemon logs as well
(cephadm logs --name prometheus.ceph02.mousetech.com). Could it be
that there's a non-cephadm prometheus already listening on port 9095?
Zitat von Tim Holloway <timh@xxxxxxxxxxxxx>:
I finally got brave and migrated from Pacific to Reef, did some
banging and hammering and for the first time in a long time got a
complete "HEALTH OK" status.
However, the dashboard is still not happy. It cannot contact the
Prometheus API on port 9095.
I have redeployed Prometheus multiple times without result.
I'm pretty sure that at one time there were no less than 3 different
Prometheus containers running on one of the configured Prometheus
servers, but now all I can get is the node-exporter.
Worse, if I do:
ceph orch reconfig prometheus
I get:
Error EINVAL: No daemons exist under service name "prometheus". View
currently running services using "ceph orch ls"
But if I do:
ceph orch ls
I get:
prometheus ?:9095 0/1 -
116s ceph02.mousetech.com
Suggestions?
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
