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 556341FF183 for ; Wed, 17 Dec 2025 09:37:46 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A57CB21634; Wed, 17 Dec 2025 09:38:31 +0100 (CET) From: Dominik Rusovac To: pve-devel@lists.proxmox.com Date: Wed, 17 Dec 2025 09:38:19 +0100 Message-ID: <20251217083819.33912-1-d.rusovac@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1765960698652 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.000 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.001 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.001 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.001 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [mon.pm] Subject: [pve-devel] [PATCH pve-manager v2] fix #7011: ceph monitor: set ownership of monitor logs X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Cc: Dominik Rusovac Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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 --- PVE/API2/Ceph/MON.pm | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/PVE/API2/Ceph/MON.pm b/PVE/API2/Ceph/MON.pm index 70fc158d..18407b1c 100644 --- a/PVE/API2/Ceph/MON.pm +++ b/PVE/API2/Ceph/MON.pm @@ -428,6 +428,15 @@ __PACKAGE__->register_method({ $mon_keyring, ]); run_command(['chown', 'ceph:ceph', '-R', $mondir]); + + eval { + # fix-up initial log file from freshly created monitor here, as currently + # we cannot instruct ceph-mon to create it with the correct ownership without + # losing access to the mon keyring inside pmxcfs. + run_command( + ['chown', 'ceph:ceph', "/var/log/ceph/ceph-mon.$monid.log"]); + }; + warn "$@" if $@; }; my $err = $@; unlink $monmap; -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel