From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <m.sandoval@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id D58F293689 for <pve-devel@lists.proxmox.com>; Tue, 9 Apr 2024 11:48:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AFD3B1AAF4 for <pve-devel@lists.proxmox.com>; Tue, 9 Apr 2024 11:48:08 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Tue, 9 Apr 2024 11:48:07 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 6E60642EF1 for <pve-devel@lists.proxmox.com>; Tue, 9 Apr 2024 11:48:07 +0200 (CEST) From: Maximiliano Sandoval <m.sandoval@proxmox.com> To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> In-Reply-To: <20240402145523.683008-1-m.carrara@proxmox.com> (Max Carrara's message of "Tue, 2 Apr 2024 16:55:12 +0200") References: <20240402145523.683008-1-m.carrara@proxmox.com> User-Agent: mu4e 1.12.3; emacs 29.2 Date: Tue, 09 Apr 2024 11:48:06 +0200 Message-ID: <s8o5xwqrhnt.fsf@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain X-SPAM-LEVEL: Spam detection results: 0 AWL 0.013 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH v5 pve-storage, pve-manager 00/11] Fix #4759: Configure Permissions for ceph-crash.service X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Tue, 09 Apr 2024 09:48:38 -0000 Max Carrara <m.carrara@proxmox.com> writes: > Fix #4759: Configure Permissions for ceph-crash.service - Version 5 > =================================================================== I tested this patch series on a testing cluster updated to no-subscription with ceph-base 18.2.2-pve1. For the purposes of testing I removed the version check against 0.0.0. The following things were working as expected: - There are no more ceph-crash errors in the journal - /etc/pve/ceph.conf contains: ``` [client.crash] keyring = /etc/pve/ceph/$cluster.$name.keyring ``` - The new keyring is the right place at ``` # ls /etc/pve/ceph ceph.client.crash.keyring ``` - After a few minutes the crash reports at /var/lib/ceph/crash/ were moved to /var/lib/ceph/crash/posted. One thing that was broken is running the ceph-crash binary directly: ``` # ceph-crash INFO:ceph-crash:pinging cluster to exercise our key 2024-04-09T11:42:31.591+0200 7009fca926c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied 2024-04-09T11:42:31.595+0200 7009fca926c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied 2024-04-09T11:42:31.595+0200 7009fca926c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied 2024-04-09T11:42:31.595+0200 7009fca926c0 -1 auth: unable to find a keyring on /etc/pve/priv/ceph.client.admin.keyring: (13) Permission denied 2024-04-09T11:42:31.595+0200 7009fca926c0 -1 monclient: keyring not found [errno 13] RADOS permission denied (error connecting to the cluster) INFO:ceph-crash:monitoring path /var/lib/ceph/crash, delay 600s ``` -- Maximiliano