Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Upgrading buster => bullseye. Canonicalization of /var/log/journal.
664 views
Skip to first unread message
pe...@easthope.ca
Sep 28, 2021, 1:10:06 PM9/28/21
to
Hi,
Here the upgrade was completed except for the problem indicated in the
following transcript.
This page appears relevant.
https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
/var/log/journal exists here.
The command "systemd-tmpfiles --create --prefix /var/log/journal" gives
complaints similar to those in the transcript.
Likely the solution is obvious once the problem is understood. What is
unsafe about the path transition? How is systemd journaling meant to
work?
Thx, ... P.
===============================
root@joule:~# apt update
Hit:1 https://mirror.it.ubc.ca/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@joule:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
9 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up systemd (247.3-6) ...
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
dpkg: dependency problems prevent configuration of libpam-systemd:i386:
libpam-systemd:i386 depends on systemd (= 247.3-6); however:
Package systemd is not configured yet.
dpkg: error processing package libpam-systemd:i386 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of policykit-1:
policykit-1 depends on default-logind | logind; however:
Package default-logind is not installed.
Package libpam-systemd:i386 which provides default-logind is not configured yet.
Package logind is not installed.
Package libpam-systemd:i386 which provides logind is not configured yet.
dpkg: error processing package policykit-1 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of policykit-1-gnome:
policykit-1-gnome depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package policykit-1-gnome (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of plymouth:
plymouth depends on systemd (>= 232-8~); however:
Package systemd is not configured yet.
dpkg: error processing package plymouth (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mate-polkit:i386:
mate-polkit:i386 depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package mate-polkit:i386 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of lxpolkit:
lxpolkit depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package lxpolkit (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of modemmanager:
modemmanager depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package modemmanager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of plymouth-label:
plymouth-label depends on plymouth (= 0.9.5-3); however:
Package plymouth is not configured yet.
dpkg: error processing package plymouth-label (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
libpam-systemd:i386
policykit-1
policykit-1-gnome
plymouth
mate-polkit:i386
lxpolkit
modemmanager
plymouth-label
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@joule:~#
===============================
--
48.7693 N 123.3053 W
mobile: +1 778 951 5147
VoIP: +1 604 670 0140
Here the upgrade was completed except for the problem indicated in the
following transcript.
This page appears relevant.
https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
/var/log/journal exists here.
The command "systemd-tmpfiles --create --prefix /var/log/journal" gives
complaints similar to those in the transcript.
Likely the solution is obvious once the problem is understood. What is
unsafe about the path transition? How is systemd journaling meant to
work?
Thx, ... P.
===============================
root@joule:~# apt update
Hit:1 https://mirror.it.ubc.ca/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
root@joule:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
9 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up systemd (247.3-6) ...
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
dpkg: dependency problems prevent configuration of libpam-systemd:i386:
libpam-systemd:i386 depends on systemd (= 247.3-6); however:
Package systemd is not configured yet.
dpkg: error processing package libpam-systemd:i386 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of policykit-1:
policykit-1 depends on default-logind | logind; however:
Package default-logind is not installed.
Package libpam-systemd:i386 which provides default-logind is not configured yet.
Package logind is not installed.
Package libpam-systemd:i386 which provides logind is not configured yet.
dpkg: error processing package policykit-1 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of policykit-1-gnome:
policykit-1-gnome depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package policykit-1-gnome (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of plymouth:
plymouth depends on systemd (>= 232-8~); however:
Package systemd is not configured yet.
dpkg: error processing package plymouth (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of mate-polkit:i386:
mate-polkit:i386 depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package mate-polkit:i386 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of lxpolkit:
lxpolkit depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package lxpolkit (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of modemmanager:
modemmanager depends on policykit-1; however:
Package policykit-1 is not configured yet.
dpkg: error processing package modemmanager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of plymouth-label:
plymouth-label depends on plymouth (= 0.9.5-3); however:
Package plymouth is not configured yet.
dpkg: error processing package plymouth-label (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
libpam-systemd:i386
policykit-1
policykit-1-gnome
plymouth
mate-polkit:i386
lxpolkit
modemmanager
plymouth-label
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@joule:~#
===============================
--
48.7693 N 123.3053 W
mobile: +1 778 951 5147
VoIP: +1 604 670 0140
Nils
Sep 28, 2021, 1:40:04 PM9/28/21
to
Hi,
Are you sure you still need these journals? Might be some nasty bug and my way to work around it would be to just delete those logs.
I mean, it's kind of a hacky solution but I'm absolutely sure this allows the upgrade to continue.
Hope it's a viable solution to you,
Tuxifan
Are you sure you still need these journals? Might be some nasty bug and my way to work around it would be to just delete those logs.
I mean, it's kind of a hacky solution but I'm absolutely sure this allows the upgrade to continue.
Hope it's a viable solution to you,
Tuxifan
Am 28. September 2021 17:55:59 MESZ schrieb pe...@easthope.ca:
Hi,
Here the upgrade was completed except for the problem indicated in the
following transcript.
This page appears relevant.
https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
/var/log/journal exists here.
The command "systemd-tmpfiles --create --prefix /var/log/journal" gives
complaints similar to those in the transcript.
Likely the solution is obvious once the problem is understood. What is
unsafe about the path transition? How is systemd journaling meant to
work?
Thx, ... P.
Greg Wooledge
Sep 28, 2021, 1:50:05 PM9/28/21
to
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> Hi,
> Here the upgrade was completed except for the problem indicated in the
> following transcript.
>
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
>
> /var/log/journal exists here.
What does it look like?
> Hi,
> Here the upgrade was completed except for the problem indicated in the
> following transcript.
>
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
>
> /var/log/journal exists here.
ls -ld / /var /var/log /var/log/journal
> The command "systemd-tmpfiles --create --prefix /var/log/journal" gives
> complaints similar to those in the transcript.
>
> Likely the solution is obvious once the problem is understood. What is
> unsafe about the path transition? How is systemd journaling meant to
> work?
> Setting up systemd (247.3-6) ...
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> dpkg: error processing package systemd (--configure):
> installed systemd package post-installation script subprocess returned error exit status 73
<https://github.com/systemd/systemd/issues/11282> suggests an ownership
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> Detected unsafe path transition / -> /var during canonicalization of /var/log/journal/82516769d28444b49bf2553c1a9d8b27/system.journal.
> dpkg: error processing package systemd (--configure):
> installed systemd package post-installation script subprocess returned error exit status 73
misconfiguration could be responsible. Thus, seeing the output of the ls
command may help.
Andrew M.A. Cater
Sep 28, 2021, 2:40:05 PM9/28/21
to
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
worth rebooting and running dpkg -C to configure anything that is unpacked
but remains unconfigured.
All the best, as ever,
Andy Cater
Greg Wooledge
Sep 28, 2021, 2:50:05 PM9/28/21
to
> If this appears to be complete apart from the errors you have: it may be
> worth rebooting and running dpkg -C to configure anything that is unpacked
> but remains unconfigured.
This would not be my advice. For two reasons:
> worth rebooting and running dpkg -C to configure anything that is unpacked
> but remains unconfigured.
1) If the underlying problem isn't fixed, there is no reason to expect
that "dpkg -C" is going to fix things. It should just run the same
post-inst scripts again, and produce the same errors again.
2) With systemd in a possibly messed-up state, rebooting is risky.
I would focus on fixing the underlying issue, starting with looking at
the things that it complained about.
pe...@easthope.ca
Sep 29, 2021, 4:30:04 PM9/29/21
to
From: Greg Wooledge <gr...@wooledge.org>
Date: Tue, 28 Sep 2021 13:41:05 -0400
drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
root@joule:/# ls -lR /var/log/journal
/var/log/journal:
total 4
drwxr-xr-x 2 root root 4096 Sep 29 06:46 82516769d28444b49bf2553c1a9d8b27
/var/log/journal/82516769d28444b49bf2553c1a9d8b27:
total 32776
-rw-r----- 1 root root 25165824 Sep 29 06:49 system.journal
-rw-r-----+ 1 root root 8388608 Sep 29 06:54 user-1000.journal
The two files contain binary data. Any chance they are file system
journals?
Thx, ... P.
Date: Tue, 28 Sep 2021 13:41:05 -0400
> What does it look like?
>
> ls -ld / /var /var/log /var/log/journal
root@joule:/# ls -ld / /var /var/log
>
> ls -ld / /var /var/log /var/log/journal
drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
root@joule:/# ls -lR /var/log/journal
/var/log/journal:
total 4
drwxr-xr-x 2 root root 4096 Sep 29 06:46 82516769d28444b49bf2553c1a9d8b27
/var/log/journal/82516769d28444b49bf2553c1a9d8b27:
total 32776
-rw-r----- 1 root root 25165824 Sep 29 06:49 system.journal
-rw-r-----+ 1 root root 8388608 Sep 29 06:54 user-1000.journal
The two files contain binary data. Any chance they are file system
journals?
Thx, ... P.
pe...@easthope.ca
Sep 29, 2021, 4:30:04 PM9/29/21
to
From: Nils <tux...@posteo.de>
Date: Tue, 28 Sep 2021 17:16:30 +0000
> ... my way to work around it would be to just delete those logs.
Did that and rebooted. System behaviour is unchanged.
plymouth-label was the last package reported unconfigured. So ...
root@joule:~# apt-get --reinstall install plymouth-label
The i386 archive is defective? The sources.list here doesn't rely on
one site.
root@joule:~# cat /etc/apt/sources.list
#deb http://mirror.it.ubc.ca/debian/ bullseye main
deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
deb http://ftp.ca.debian.org/debian/ bullseye main contrib non-free
deb-src http://ftp.ca.debian.org/debian/ bullseye main contrib non-free
deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-fr
ee
deb-src http://deb.debian.org/debian-security/ bullseye-security main contrib no
n-free
Has anyone installed or upgraded to bullseye on a 32 bit PC?
Thx, ... P.
Date: Tue, 28 Sep 2021 17:16:30 +0000
> Are you sure you still need these journals?
I don't know.
> ... my way to work around it would be to just delete those logs.
Did that and rebooted. System behaviour is unchanged.
plymouth-label was the last package reported unconfigured. So ...
root@joule:~# apt-get --reinstall install plymouth-label
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Building dependency tree... Done
Reading state information... Done
9 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for plymouth-label:i386
After this operation, 0 B of additional disk space will be used.
The i386 archive is defective? The sources.list here doesn't rely on
one site.
root@joule:~# cat /etc/apt/sources.list
#deb http://mirror.it.ubc.ca/debian/ bullseye main
deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
deb http://ftp.ca.debian.org/debian/ bullseye main contrib non-free
deb-src http://ftp.ca.debian.org/debian/ bullseye main contrib non-free
deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-fr
ee
deb-src http://deb.debian.org/debian-security/ bullseye-security main contrib no
n-free
Has anyone installed or upgraded to bullseye on a 32 bit PC?
Thx, ... P.
Greg Wooledge
Sep 29, 2021, 4:50:07 PM9/29/21
to
On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge <gr...@wooledge.org>
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
> drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
The ownership of the / directory is wrong. It should be root:root,
> From: Greg Wooledge <gr...@wooledge.org>
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
> drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
not peter:peter.
chown root:root /
Everything else looks OK at the moment.
Charles Curley
Sep 29, 2021, 9:30:04 PM9/29/21
to
On Wed, 29 Sep 2021 08:01:00 -0700
pe...@easthope.ca wrote:
> root@joule:~# cat /etc/apt/sources.list
> #deb http://mirror.it.ubc.ca/debian/ bullseye main
> deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
> deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
>
> deb http://ftp.ca.debian.org/debian/ bullseye main contrib
> non-free deb-src http://ftp.ca.debian.org/debian/ bullseye main
> contrib non-free
>
> deb http://deb.debian.org/debian-security/ bullseye-security main
> contrib non-fr ee
> deb-src http://deb.debian.org/debian-security/ bullseye-security main
> contrib no n-free
>
> Has anyone installed or upgraded to bullseye on a 32 bit PC?
Yes, several times.
pe...@easthope.ca wrote:
> root@joule:~# cat /etc/apt/sources.list
> #deb http://mirror.it.ubc.ca/debian/ bullseye main
> deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
> deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
>
> deb http://ftp.ca.debian.org/debian/ bullseye main contrib
> non-free deb-src http://ftp.ca.debian.org/debian/ bullseye main
> contrib non-free
>
> deb http://deb.debian.org/debian-security/ bullseye-security main
> contrib non-fr ee
> deb-src http://deb.debian.org/debian-security/ bullseye-security main
> contrib no n-free
>
> Has anyone installed or upgraded to bullseye on a 32 bit PC?
Looking at your sources.list, you can probably remove either the ubc
stanza or the ca.debian.org stanza. I suspect that lags between mirrors
could cause referential integrity issues.
However, it may be simpler to use deb.debian.org, which will assign a
mirror, reducing your reliance on any one mirror. Mine look like so:
root@freeman:~# cat /etc/apt/sources.list
# deb cdrom:[Debian GNU/Linux 11.0.0 _Bullseye_ - Official i386 NETINST 20210814-10:03]/ bullseye main
#deb cdrom:[Debian GNU/Linux 11.0.0 _Bullseye_ - Official i386 NETINST 20210814-10:03]/ bullseye main
deb http://deb.debian.org/debian bullseye main contrib non-free
# deb-src http://deb.debian.org/debian bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main
# deb-src http://security.debian.org/debian-security bullseye-security main
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
root@freeman:~#
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
David Wright
Sep 29, 2021, 11:40:05 PM9/29/21
to
but even worse (there, it was only group ownership that was wrong).
It does appear that there's a subset of people who immediately
recognise this warning message as meaning "wrong ownership",
Greg (possibly), Kushal and of course Poettering:
https://github.com/systemd/systemd/issues/11282
Would it be sensible for the message to actually mention ownership,
or can it apply to very different circumstances (beyond permissions,
that is)? I've failed to find any other cause, but see a lot of
people messing up their ownership.
Is this being done by people, say, untarring archives as root, or
are there some buggy programs out there? One person claimed it
happened through formatting a partition with some gnome program.
Is that likely?
Cheers,
David.
Nils
Sep 30, 2021, 12:00:04 AM9/30/21
to
>From my experience gnome-disks automatically chowns / to the executing user when creating a filesystem.
But I don't think Peter did that.
I'd rather say it's been caused by some installation script, those are usually buggy when it comes to file ownership.
Peter, did you install anything via a .run or .sh file?
Nils
--
Nils <tux...@posteo.de>
But I don't think Peter did that.
I'd rather say it's been caused by some installation script, those are usually buggy when it comes to file ownership.
Peter, did you install anything via a .run or .sh file?
Nils
Nils <tux...@posteo.de>
Greg Wooledge
Sep 30, 2021, 7:20:05 AM9/30/21
to
On Wed, Sep 29, 2021 at 10:35:35PM -0500, David Wright wrote:
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their ownership.
That would be a good question to ask the systemd developers.
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their ownership.
Kushal Kumaran
Oct 2, 2021, 1:10:04 AM10/2/21
to
On Wed, Sep 29 2021 at 10:35:35 PM, David Wright <deb...@lionunicorn.co.uk> wrote:
> On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
>> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
>> > From: Greg Wooledge <gr...@wooledge.org>
>> > Date: Tue, 28 Sep 2021 13:41:05 -0400
>> > > What does it look like?
>> > >
>> > > ls -ld / /var /var/log /var/log/journal
>> >
>> > root@joule:/# ls -ld / /var /var/log
>> > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
>> > drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
>> > drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
>>
>> The ownership of the / directory is wrong. It should be root:root,
>> not peter:peter.
>>
>> chown root:root /
>>
>> Everything else looks OK at the moment.
>
> Similar to https://lists.debian.org/debian-user/2021/07/msg00907.html
> but even worse (there, it was only group ownership that was wrong).
> It does appear that there's a subset of people who immediately
> recognise this warning message as meaning "wrong ownership",
> Greg (possibly), Kushal and of course Poettering:
>
FWIW, that email was the first I'd ever heard of the problem. My
> On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
>> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
>> > From: Greg Wooledge <gr...@wooledge.org>
>> > Date: Tue, 28 Sep 2021 13:41:05 -0400
>> > > What does it look like?
>> > >
>> > > ls -ld / /var /var/log /var/log/journal
>> >
>> > root@joule:/# ls -ld / /var /var/log
>> > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
>> > drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
>> > drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
>>
>> The ownership of the / directory is wrong. It should be root:root,
>> not peter:peter.
>>
>> chown root:root /
>>
>> Everything else looks OK at the moment.
>
> Similar to https://lists.debian.org/debian-user/2021/07/msg00907.html
> but even worse (there, it was only group ownership that was wrong).
> It does appear that there's a subset of people who immediately
> recognise this warning message as meaning "wrong ownership",
> Greg (possibly), Kushal and of course Poettering:
>
solution was based on a web search, which probably led me to the
following link, but I neglected to include that in my email.
> https://github.com/systemd/systemd/issues/11282
>
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their ownership.
https://github.com/systemd/systemd/blob/dd4c15296cce001287d03a6647a751f253de2a51/src/basic/fs-util.c#L736,
the message has been updated three months ago to include ownership of
the offending directories. At this point, we'd need to wait for a newer
version of systemd to migrate into debian repos.
Andrei POPESCU
Oct 2, 2021, 3:50:04 AM10/2/21
to
On Mi, 29 sep 21, 07:05:37, pe...@easthope.ca wrote:
> From: Greg Wooledge <gr...@wooledge.org>
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
> drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
Please include also the output for /var/log/journal (as already
> From: Greg Wooledge <gr...@wooledge.org>
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
> drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
> drwxr-xr-x 10 root root 4096 Sep 29 06:39 /var/log
requested by Greg), and if you have the 'acl' package already installed
the output of `getfacl` for it.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
0 new messages