From: "Max R. Carrara" <m.carrara@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH ceph master/ceph squid/manager v4 0/7] Fix #6816: Prevent ceph-exporter Daemon from Crashing on Startup
Date: Tue, 23 Jun 2026 15:44:30 +0200 [thread overview]
Message-ID: <20260623134454.710441-1-m.carrara@proxmox.com> (raw)
Fix #6816: Prevent ceph-exporter Daemon from Crashing on Startup - v4
=====================================================================
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.
v2 contains the entire description; see below for a link.
Changes Since v3
----------------
- Rebase the patches
- Change the PVE version in the debian/postinst changes (patch #03)
to 9.2.4
- Add patch for Ceph Squid (patch #07)
Tested this for both Ceph Tentacle and Ceph Squid, but a quick smoke test here
would be much appreciated nevertheless.
Previous Versions
-----------------
v1: https://lore.proxmox.com/pve-devel/20250916172012.739807-1-m.carrara@proxmox.com/
v2: https://lore.proxmox.com/pve-devel/20251222141907.400926-1-m.carrara@proxmox.com/
v3: https://lore.proxmox.com/pve-devel/20251223153419.507507-1-m.carrara@proxmox.com/
References
----------
[0]: https://lore.proxmox.com/pve-devel/20240402145523.683008-11-m.carrara@proxmox.com/
Summary of Changes
------------------
pve-manager:
Max R. Carrara (5):
ceph: tools: add helper sub for creating or updating keyring files
fix #6816: api: ceph: create 'client.exporter' w/ keyring
fix #6816: bin: add pve-ceph-keyring helper and call it in postinst
ceph: tools: simplify helper sub for crash keyring file
bin: make pve-init-ceph-crash call pve-ceph-keyring
PVE/API2/Ceph/MON.pm | 9 ++
PVE/Ceph/Tools.pm | 108 ++++++++++++---
bin/Makefile | 1 +
bin/pve-ceph-keyring | 286 ++++++++++++++++++++++++++++++++++++++++
bin/pve-init-ceph-crash | 152 +--------------------
debian/postinst | 6 +
6 files changed, 397 insertions(+), 165 deletions(-)
create mode 100755 bin/pve-ceph-keyring
ceph master:
Max R. Carrara (1):
fix #6816: patches: make ceph-exporter use custom keyring
...orter-use-custom-keyring-and-set-gro.patch | 32 +++++++++++++++++++
patches/series | 1 +
2 files changed, 33 insertions(+)
create mode 100644 patches/0014-systemd-ceph-exporter-use-custom-keyring-and-set-gro.patch
ceph squid:
Max R. Carrara (1):
fix #6816: patches: make ceph-exporter use custom keyring
...orter-use-custom-keyring-and-set-gro.patch | 32 +++++++++++++++++++
patches/series | 1 +
2 files changed, 33 insertions(+)
create mode 100644 patches/0053-systemd-ceph-exporter-use-custom-keyring-and-set-gro.patch
Summary over all repositories:
10 files changed, 463 insertions(+), 165 deletions(-)
--
Generated by murpp 0.11.0
next reply other threads:[~2026-06-23 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 13:44 Max R. Carrara [this message]
2026-06-23 13:44 ` [PATCH pve-manager v4 1/7] ceph: tools: add helper sub for creating or updating keyring files Max R. Carrara
2026-06-23 13:44 ` [PATCH pve-manager v4 2/7] fix #6816: api: ceph: create 'client.exporter' w/ keyring Max R. Carrara
2026-06-23 13:44 ` [PATCH pve-manager v4 3/7] fix #6816: bin: add pve-ceph-keyring helper and call it in postinst Max R. Carrara
2026-06-23 13:44 ` [PATCH pve-manager v4 4/7] ceph: tools: simplify helper sub for crash keyring file Max R. Carrara
2026-06-23 13:44 ` [PATCH pve-manager v4 5/7] bin: make pve-init-ceph-crash call pve-ceph-keyring Max R. Carrara
2026-06-23 13:44 ` [PATCH ceph master v4 6/7] fix #6816: patches: make ceph-exporter use custom keyring Max R. Carrara
2026-06-23 13:44 ` [PATCH ceph squid v4 7/7] " Max R. Carrara
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=20260623134454.710441-1-m.carrara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.