From: Alwin Antreich via pve-user <pve-user@lists.proxmox.com>
To: gaio@lilliput.linux.it
Cc: Alwin Antreich <alwin@antreich.com>, pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Upgrade to PVE8, logcheck, error on journalctl...
Date: Mon, 19 Aug 2024 05:35:20 +0000 [thread overview]
Message-ID: <mailman.300.1724045728.302.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <7c0apk-kb83.ln1@leia.lilliput.linux.it>
[-- Attachment #1: Type: message/rfc822, Size: 4804 bytes --]
From: "Alwin Antreich" <alwin@antreich.com>
To: gaio@lilliput.linux.it
Cc: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Upgrade to PVE8, logcheck, error on journalctl...
Date: Mon, 19 Aug 2024 05:35:20 +0000
Message-ID: <71a3501c3734603857ff73e84dd1ab3683cbc0a2@antreich.com>
Hi Marco,
August 18, 2024 at 9:58 PM, "Marco Gaiarin" <gaio@lilliput.linux.it> wrote:
>
> Mandi! Alwin Antreich via pve-user
> In chel di` si favelave...
>
> >
> > Did you already look at apparmor, might it be blocked by it? You should see that in the dmesg.
> >
> No, nothing in logs...
>
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).
Maybe you also have a look at journalcheck instead? It seems to be a replacement for logcheck.
Cheers,
Alwin
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-08-19 5:35 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 [this message]
[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=mailman.300.1724045728.302.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=alwin@antreich.com \
--cc=gaio@lilliput.linux.it \
/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