From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id C7E411FF13B for ; Wed, 11 Mar 2026 14:23:14 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B65711BC5B; Wed, 11 Mar 2026 14:23:07 +0100 (CET) From: Maximiliano Sandoval To: Dominik Rusovac Subject: Re: [pve-devel] [PATCH pve-manager v2] fix #7011: ceph monitor: set ownership of monitor logs In-Reply-To: <20251217083819.33912-1-d.rusovac@proxmox.com> (Dominik Rusovac's message of "Wed, 17 Dec 2025 09:38:19 +0100") References: <20251217083819.33912-1-d.rusovac@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Wed, 11 Mar 2026 14:22:32 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1773235317798 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.961 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: EJXBXFR3H6RECMJ6KSRFXT7RBZXHLGUJ X-Message-ID-Hash: EJXBXFR3H6RECMJ6KSRFXT7RBZXHLGUJ X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: pve-devel@lists.proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Dominik Rusovac 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 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 Tested-by: Maximiliano Sandoval -- Maximiliano