Your message dated Thu, 28 Feb 2019 21:58:09 +0100
with message-id <[email protected]>
and subject line Re: Logs in /run/log/journal not readable by group adm
has caused the Debian Bug report #920035,
regarding Logs in /run/log/journal not readable by group adm
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
920035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920035
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 240-4
I recently lost the ability to read the logs of my user services
with journalctl --user-unit or, well, systemctl --user status.
At first I thought it was #843310 ("user service logs are not
available to normal users unless persistent Storage is used") and,
sure enough, moving to persistent storage fixed the issue.
However, I couldn't understand why this would be working before. I
don't think I had ever enabled persistant storage, but even if I
had, then /var/log/journal would have to have disappeared in order
for volatile storage to come back.
Anyway.
I finally realized that, with persistant storage, I could read the
whole journal as my user (not only my services). But that's
because I'm in the adm group too.
So perhaps /run/log/journal used to be readable by adm, but no
longer is? That would explain why it worked for me *before* (I was
able to read my logs not because of my UID, but because of having
the adm GID).
Alas, 843310 says:
> the files in /run/log/journal are owned root:systemd-journal,
> and only have an acl permitting group reading by group "adm".
In my case, not even the former is true:
$ sudo ls -ld /run/log/journal{,/ef...}
drwxr-xr-x 3 root root 60 Jan 21 16:24 /run/log/journal
drwxr-x--- 2 root root 60 Jan 21 16:24 /run/log/journal/ef...
It would be great to see group ownership and ACLs fixed for
/run/log/journal, so that this works again.
Many thanks for considering,
-d
--- End Message ---
--- Begin Message ---
Version: 241-1
Am 28.02.19 um 20:01 schrieb Michael Biebl:
> Hi dato,
>
> On Mon, 21 Jan 2019 16:34:43 -0300 Dato <[email protected]> wrote:
>
>> $ sudo ls -ld /run/log/journal{,/ef...}
>> drwxr-xr-x 3 root root 60 Jan 21 16:24 /run/log/journal
>> drwxr-x--- 2 root root 60 Jan 21 16:24 /run/log/journal/ef...
>>
>> It would be great to see group ownership and ACLs fixed for
>> /run/log/journal, so that this works again.
>
> If you can still reproduce this issue (with 241-1), would you mind
> filing this upstream at https://github.com/systemd/systemd/issues ?
Looks like this issue is fixed in v241
(I could reproduce the issue in a buster VM using 240-5)
So closing the bug report.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
