Can you share 'ceph orch ls prometheus --export'? And if it has been deployed successfully but is currently not running, the logs should show why that is the case.

To restart prometheus, you can just run this to restart the entire prometheus service (which would include all instances if you had multiple, but currently you only have one in the specs):

ceph orch restart prometheus

or only a specific daemon:

ceph orch daemon restart prometheus.<hostname>

And usually, cephadm does create systemd units, for example:

cephadm ls --no-detail | grep prometheus
        "name": "prometheus.nautilus",
"systemd_unit": "ceph-201a2fbc-ce7b-44a3-9ed7-39427972083b@prometheus.nautilus"


Zitat von Tim Holloway <t...@mousetech.com>:

I don't think there is failure to deploy. For one thing, I did have, as mentioned 3 Prometheus-related containers running at one point on the machine. Also checked for port issues and there are none. Nothing listens on 9095.

One thing that does concern me is that the docs sau changes in settings require "restarting prometheus", but not what command does that. Given that there are no systemd units to address and that the orchestrator claims that there is no "prometheus service" even as it shows that there's 1 service, stopped, it's quite frustrating.

On 3/26/25 07:26, Eugen Block wrote:
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 <t...@mousetech.com>:

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@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io


_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io


_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Reply via email to