From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-user-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id E85D11FF173 for <inbox@lore.proxmox.com>; Thu, 15 Aug 2024 09:28:40 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 81B487E1; Thu, 15 Aug 2024 09:28:53 +0200 (CEST) Date: Thu, 15 Aug 2024 09:28:44 +0200 In-Reply-To: <7mnpok-r8h2.ln1@leia.lilliput.linux.it> References: <7mnpok-r8h2.ln1@leia.lilliput.linux.it> MIME-Version: 1.0 Message-ID: <mailman.273.1723706932.302.pve-user@lists.proxmox.com> List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Post: <mailto:pve-user@lists.proxmox.com> From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com> Precedence: list Cc: Alwin Antreich <alwin@antreich.com>, pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 X-BeenThere: pve-user@lists.proxmox.com List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> Reply-To: Proxmox VE user list <pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> Subject: Re: [PVE-User] Upgrade to PVE8, logcheck, error on journalctl... Content-Type: multipart/mixed; boundary="===============3708514330676294711==" Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" <pve-user-bounces@lists.proxmox.com> --===============3708514330676294711== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <alwin@antreich.com> X-Original-To: pve-user@lists.proxmox.com Delivered-To: pve-user@lists.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 91D88C4783 for <pve-user@lists.proxmox.com>; Thu, 15 Aug 2024 09:28:51 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 70C36755 for <pve-user@lists.proxmox.com>; Thu, 15 Aug 2024 09:28:51 +0200 (CEST) Received: from mx.antreich.com (mx.antreich.com [173.249.42.230]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Thu, 15 Aug 2024 09:28:50 +0200 (CEST) Received: from mail2.antreich.com (unknown [172.16.9.25]) by mx.antreich.com (Postfix) with ESMTPS id 00D386E2E1B for <pve-user@lists.proxmox.com>; Thu, 15 Aug 2024 09:28:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antreich.com; s=2018; t=1723706924; h=from:from:reply-to:subject:subject:date:date:message-id:message-id:to: cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=d/v88/HS3vPXHgktTjBEiloesMJB3hGtFwC1+zp5X/4=; b=KXXH8GOhbu+wmPn0o0wt73e0gLKL+gr1SGpy7Y2j0XhqbI7JWXJ9qL84z9QyAcq8ofumZZ z2uPMKa2Btfqtgi+KKZmNgoREYgD7nvI3a0S4EE/qurOX/VCpd53B+QZDhDAFZOa+peInT tOHn8ka8fIzExMkZWrHZXIYA7LaofTnIEpvhGkii6ksVMx5Lq4kPwrWqyNlnkl5KWNjceC gUhxo2uKVp5z5mwIzlE/uy5tAbTfIeV0pJ7P/oCLyWXwnXyYFRQmgVsSMQjbdSpa4Wk1Ls izrkJ14m1+IOtoe4b3EEtJObGDb8PpGvz820fqw3ZiyGmW8THngbPolQbVt14w== Date: Thu, 15 Aug 2024 09:28:44 +0200 From: Alwin Antreich <alwin@antreich.com> CC: pve-user@lists.proxmox.com Subject: Re: [PVE-User] Upgrade to PVE8, logcheck, error on journalctl... In-Reply-To: <7mnpok-r8h2.ln1@leia.lilliput.linux.it> References: <7mnpok-r8h2.ln1@leia.lilliput.linux.it> Message-ID: <E8672964-2E25-454C-944E-B8E151F70DE2@antreich.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL -0.389 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy MISSING_HEADERS 1.021 Missing To: header 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_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - On August 12, 2024 5:52:09 PM GMT+02:00, Marco Gaiarin <gaio@lilliput=2Elin= ux=2Eit> wrote: > >I extensively use 'logcheck' on my servers=2E > >I've just upgrade a server to PVE8 (a little test standalone server) and >logcheck start complain: > > Logcheck failed: Your log entries may not have been checked=2E >=20 > Details: > Could not run journalctl or save output >=20 > To identify the cause you may wish to: > - Check temporary directory: /tmp/logcheck=2EN0YsPV >=20 > - verify that the logcheck user can read all > logfiles specified in; > /etc/logcheck/logcheck=2Elogfiles > /etc/logcheck/logcheck=2Elogfiled=2Ed/*=2Elogfiles > >i've tried: > > root@lisei:/etc/logcheck# su -s /bin/bash - logcheck > logcheck@lisei:~$ journalctl=20 > No journal files were opened due to insufficient permissions=2E > >but: > > root@lisei:/etc/logcheck# id logcheck > uid=3D112(logcheck) gid=3D118(logcheck) groups=3D118(logcheck),4(adm) > >so logcheck user seems have correct permission Did you already look at apparmor, might it be blocked by it? You should se= e that in the dmesg=2E Cheers, Alwin Hi Marco, --===============3708514330676294711== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user --===============3708514330676294711==--