Your message dated Thu, 12 Jan 2017 03:10:20 +0100
with message-id <[email protected]>
and subject line Re: Bug#847448: systemd: wrong permissions on non-persistent
/run/log/journal
has caused the Debian Bug report #847448,
regarding systemd: wrong permissions on non-persistent /run/log/journal
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.)
--
847448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847448
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u5
Severity: important
Dear Maintainer,
I tried to run `sudo -u nobody -g systemd-journal journalctl
--unit=some-system-unit.service`, but journalctl replied "No journal files were
found.". If I change the group argument to "root", I can read the journal of
that unit. I would expect that some non-root user could
read the journal, though, in this case to run a script as non-root that is
supposed to send part of the journal via email.
The cause appears to be that /run/log/journal is owned by root:root instead of
root:systemd-journal. There exists an older bug (bug #746279) where this was
fixed in systemd 208-6, but the issue is back in systemd-215-17.
Best regards,
Dennis
-- Package-specific info:
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-6
ii libc6 2.19-18+deb8u6
ii libcap2 1:2.24-8
ii libcap2-bin 1:2.24-8
ii libcryptsetup4 2:1.6.6-5
ii libgcrypt20 1.6.3-2+deb8u2
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libpam0g 1.1.8-3.1+deb8u1+b1
ii libselinux1 2.3-2
ii libsystemd0 215-17+deb8u5
ii mount 2.25.2-6
ii sysv-rc 2.88dsf-59
ii udev 215-17+deb8u5
ii util-linux 2.25.2-6
Versions of packages systemd recommends:
ii dbus 1.8.20-0+deb8u1
ii libpam-systemd 215-17+deb8u5
Versions of packages systemd suggests:
pn systemd-ui <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, 8 Dec 2016 12:47:33 +0100 Michael Biebl <[email protected]> wrote:
> Control: tags -1 moreinfo unreproducible
>
> Am 08.12.2016 um 11:31 schrieb Dennis Schridde:
> > Package: systemd
> > Version: 215-17+deb8u5
> > Severity: important
> >
> > Dear Maintainer,
> >
> > I tried to run `sudo -u nobody -g systemd-journal journalctl
> > --unit=some-system-unit.service`, but journalctl replied "No journal files
> > were found.". If I change the group argument to "root", I can read the
> > journal of that unit. I would expect that some non-root user could
> > read the journal, though, in this case to run a script as non-root that is
> > supposed to send part of the journal via email.
> >
> > The cause appears to be that /run/log/journal is owned by root:root instead
> > of root:systemd-journal. There exists an older bug (bug #746279) where this
> > was fixed in systemd 208-6, but the issue is back in systemd-215-17.
>
> I can't reproduce the problem.
> I've checked several jessie systems (with a volatile journal), some of
> them on real hardware, some are VMs, all of them have
> root:systemd-journal owned journal files.
>
> This looks like something which is specific to your system.
>
> Can you reproduce the reproduce the problem with a clean installation of
> jessie? Do you have any custom configuration which might override the
> default configuration?
Since no further information was provided and I'm unable to reproduce
the issue with the available information, I'm going to close this bug
report.
Please reopen if you still encounter this issue and you are available
for further debugging.
Regards,
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]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
