From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Upgrade to PVE8, logcheck, error on journalctl...
Date: Mon, 19 Aug 2024 10:52:43 +0200 [thread overview]
Message-ID: <ZsMH220U3d2x0xwa@sv.lnf.it> (raw)
In-Reply-To: <71a3501c3734603857ff73e84dd1ab3683cbc0a2@antreich.com>
Mandi! Alwin Antreich
In chel di` si favelave...
> Then, the user logcheck is running as really can't access the journal from the
> system, as it has no permission. Like the error message says.
> For the permission you need to use systemd-journal, it has changed since Debian
> 8 (Jessie). Members of this group can use the command journalctl and read log
> files of systemd (in /var/log/journal).
The problem is exactly that. 'logcheck' is a member of group 'adm', and in
'plain' Debian 12 can access journal, in PVE 8 no.
So, seems a specific 'PVE bug'; the apparmor hint was a good hint (because
AFAIK Debian does not enable apparmor by default), but seems not that...
> Maybe you also have a look at journalcheck instead? It seems to be a
> replacement for logcheck.
You meant this?:
https://github.com/lynix/journalcheck
seems not just packaged... and logcheck support journal!
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-08-19 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 15:52 Marco Gaiarin
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 [this message]
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=ZsMH220U3d2x0xwa@sv.lnf.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