public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Dominik Rusovac <d.rusovac@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-manager v2] fix #7011: ceph monitor: set ownership of monitor logs
Date: Wed, 11 Mar 2026 14:22:32 +0100	[thread overview]
Message-ID: <s8oms0e8prb.fsf@toolbox> (raw)
In-Reply-To: <20251217083819.33912-1-d.rusovac@proxmox.com> (Dominik Rusovac's message of "Wed, 17 Dec 2025 09:38:19 +0100")

Dominik Rusovac <d.rusovac@proxmox.com> writes:

> Ownership of the ceph monitor log file is now set to ceph:ceph after the
> creation of a new monitor and before the new monitor starts. Hence,
> effective ceph monitor logging on freshly set up ceph clusters no longer
> depends on the first upgrade of ceph-common.
>
> For setups (still) affected by #7011 it is required that ownership of
> the ceph monitor log file is set to ceph:ceph (either manually or due to
> some ceph-common upgrade), followed by a monitor restart.
>
> Signed-off-by: Dominik Rusovac <d.rusovac@proxmox.com>

I tested the following on a fresh Promxox VE 9.1 host:

- yes | pveceph install --repository=no-subscription
- pveceph init
- pveceph mon create
- ls -la /var/log/ceph/ceph-mon.$(hostname).log

Before this patch the owner would be set to root:ceph. After rolling
back the VM, applying the changes in this patch, and redoing the list
above the owner would be set correctly to ceph:ceph.

This issue has came up in enterprise support a couple of times. Please
consider this.

Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Tested-by: Maximiliano Sandoval <m.sandoval@proxmox.com>

-- 
Maximiliano




      parent reply	other threads:[~2026-03-11 13:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17  8:38 Dominik Rusovac
2025-12-17  9:13 ` Dominik Rusovac
2026-01-27 10:43 ` Dominik Rusovac
2026-03-11 13:22 ` Maximiliano Sandoval [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=s8oms0e8prb.fsf@toolbox \
    --to=m.sandoval@proxmox.com \
    --cc=d.rusovac@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal