From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: superseded: [pve-devel] [PATCH pve-manager v3 0/6] Fix #6816: Prevent ceph-exporter Daemon from Crashing on Startup - v3
Date: Tue, 23 Jun 2026 15:48:11 +0200 [thread overview]
Message-ID: <DJGH59KK1QDV.MFV055HV9JS7@proxmox.com> (raw)
In-Reply-To: <20251223153419.507507-1-m.carrara@proxmox.com>
On Tue Dec 23, 2025 at 4:33 PM CET, Max R. Carrara wrote:
> Fix #6816: Prevent ceph-exporter Daemon from Crashing on Startup - v3
> =====================================================================
>
> tl;dr: Stop ceph-exporter.service from ending up in a crash loop by
> handing it a custom keyring file and setting its group to `www-data`,
> similar to what we did for ceph-crash.service [0] before.
>
> [...]
Superseded-by: https://lore.proxmox.com/pve-devel/20260623134454.710441-1-m.carrara@proxmox.com/T/#t
prev parent reply other threads:[~2026-06-23 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 15:33 [pve-devel] [PATCH pve-manager v3 0/6] Fix #6816: Prevent ceph-exporter Daemon from Crashing on Startup - v3 Max R. Carrara
2025-12-23 15:34 ` [pve-devel] [PATCH pve-manager v3 1/6] ceph: tools: add helper sub for creating or updating keyring files Max R. Carrara
2025-12-23 15:34 ` [pve-devel] [PATCH pve-manager v3 2/6] fix #6816: api: ceph: create 'client.exporter' w/ keyring Max R. Carrara
2025-12-23 15:34 ` [pve-devel] [PATCH pve-manager v3 3/6] fix #6816: bin: add pve-ceph-keyring helper and call it in postinst Max R. Carrara
2025-12-23 15:34 ` [pve-devel] [PATCH pve-manager v3 4/6] ceph: tools: simplify helper sub for crash keyring file Max R. Carrara
2025-12-23 15:34 ` [pve-devel] [PATCH pve-manager v3 5/6] bin: make pve-init-ceph-crash call pve-ceph-keyring Max R. Carrara
2025-12-23 15:34 ` [pve-devel] [PATCH ceph v3 6/6] fix #6816: patches: make ceph-exporter use custom keyring Max R. Carrara
2026-06-23 13:48 ` Max R. Carrara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DJGH59KK1QDV.MFV055HV9JS7@proxmox.com \
--to=m.carrara@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox