From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Upgrade to PVE8, logcheck, error on journalctl...
Date: Mon, 12 Aug 2024 17:52:09 +0200 [thread overview]
Message-ID: <7mnpok-r8h2.ln1@leia.lilliput.linux.it> (raw)
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
next reply other threads:[~2024-08-12 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 15:52 Marco Gaiarin [this message]
2024-08-15 7:28 ` Alwin Antreich via pve-user
2024-08-18 19:58 ` Marco Gaiarin
2024-08-19 5:35 ` Alwin Antreich via pve-user
[not found] ` <71a3501c3734603857ff73e84dd1ab3683cbc0a2@antreich.com>
2024-08-19 8:52 ` Marco Gaiarin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7mnpok-r8h2.ln1@leia.lilliput.linux.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox