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 [IPv6:2a01:7e0:0:424::9])
by lore.proxmox.com (Postfix) with ESMTPS id 0FCE51FF15F
for <inbox@lore.proxmox.com>; Mon, 12 Aug 2024 18:10:10 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 9FA9136A1F;
Mon, 12 Aug 2024 18:10:18 +0200 (CEST)
From: Marco Gaiarin <gaio@lilliput.linux.it>
Date: Mon, 12 Aug 2024 17:52:09 +0200
Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!!
Message-ID: <7mnpok-r8h2.ln1@leia.lilliput.linux.it>
X-Trace: eraldo.lilliput.linux.it 1723477971 21412 192.168.1.45 (12 Aug 2024
15:52:51 GMT)
X-Mailer: tin/2.6.4-20240224 ("Banff") (Linux/6.8.0-39-generic (x86_64))
X-Gateway-System: SmartGate 1.4.5 <news.lilliput.linux.it>
To: pve-user@lists.proxmox.com
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.332 Adjusted score from AWL reputation of From: address
BAYES_00 -1.9 Bayes spam probability is 0 to 1%
DMARC_PASS -0.1 DMARC pass policy
JMQ_SPF_NEUTRAL 0.5 SPF set to ?all
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
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 -
Subject: [PVE-User] Upgrade to PVE8, logcheck, error on journalctl...
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
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/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>,
<mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE user list <pve-user@lists.proxmox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-user-bounces@lists.proxmox.com
Sender: "pve-user" <pve-user-bounces@lists.proxmox.com>
I extensively use 'logcheck' on my servers.
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.
Details:
Could not run journalctl or save output
To identify the cause you may wish to:
- Check temporary directory: /tmp/logcheck.N0YsPV
- verify that the logcheck user can read all
logfiles specified in;
/etc/logcheck/logcheck.logfiles
/etc/logcheck/logcheck.logfiled.d/*.logfiles
i've tried:
root@lisei:/etc/logcheck# su -s /bin/bash - logcheck
logcheck@lisei:~$ journalctl
No journal files were opened due to insufficient permissions.
but:
root@lisei:/etc/logcheck# id logcheck
uid=112(logcheck) gid=118(logcheck) groups=118(logcheck),4(adm)
so logcheck user seems have correct permission.
I've upgraded some plain debian VMs and containers to Bookworm, and i've not
hit troubles on logcheck. So seems something PVE specific...
Someone can help me? Thanks.
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user