From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: Dominik Rusovac <d.rusovac@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager] fix #7011: ceph monitor: set ownership of monitor logs
Date: Wed, 17 Dec 2025 08:33:36 +0100 [thread overview]
Message-ID: <0be667bb-b771-434a-8dc7-26a1fe39b0d6@proxmox.com> (raw)
In-Reply-To: <s8o4ipq37ur.fsf@proxmox.com>
Am 16.12.25 um 13:54 schrieb Maximiliano Sandoval:
> For the sake of documenting my findings: the problem when giving
> ceph-mon the right ceph:ceph user (via the --set{user,group} optiosn) is
> that our keyring is at /etc/pve and while this fixes the permissions on
> the log file, the command (and task) would fail and the logs will end
> in:
>
> ```
> 2025-12-16T13:48:47.307+0100 7282faa52cc0 -1 mon.c0-pve-101@-1(???) e0 unable to find a keyring on /etc/pve/priv/ceph.mon.keyring: (13) Permission denied
> ```
>
> since the keyring has 600 permissions.
Ack, still sounds like it can be fixed in ceph-mon, but might be a bit
more involved; lets put that to the backlog for now.
>
> I think that one could simplify the proposed patch here to only chown
> /var/log/ceph/ceph-mon.$monid.log instead of using any glob.
In that case I'd be OK with a specific chown to just that file, ideally
accompanied with a comment that includes a short variant of the basic
reasoning, like:
# fix-up initial log file from freshly created monitor here, as currently
# we cannot instruct ceph-mon to create it with the correct ownership while
# not losing access to the mon keyring inside pmxcfs.
might need polishing language/grammar wise though.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-12-17 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 13:05 Dominik Rusovac
2025-12-12 15:38 ` Maximiliano Sandoval
2025-12-16 7:25 ` Thomas Lamprecht
2025-12-16 12:06 ` Maximiliano Sandoval
2025-12-16 12:14 ` Thomas Lamprecht
2025-12-16 12:54 ` Maximiliano Sandoval
2025-12-17 7:33 ` Thomas Lamprecht [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=0be667bb-b771-434a-8dc7-26a1fe39b0d6@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.rusovac@proxmox.com \
--cc=m.sandoval@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.