Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #240503

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

From "Andrew M.A. Cater" <amacater@einval.com>
Newsgroups linux.debian.user
Subject Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.
Date 2021-09-28 20:40 +0200
Message-ID <D2qbf-hM-7@gated-at.bofh.it> (permalink)
References <D2oMa-81I-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Sep 28, 2021 at 08:55:59AM -0700, peter@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.
> 
> 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
> 

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.

All the best, as ever,

Andy Cater

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Upgrading buster => bullseye.  Canonicalization of /var/log/journal. peter@easthope.ca - 2021-09-28 19:10 +0200
  Re: Upgrading buster => bullseye.  Canonicalization of /var/log/journal. Nils <tuxifan@posteo.de> - 2021-09-28 19:40 +0200
    Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. peter@easthope.ca - 2021-09-29 22:30 +0200
      Re: Upgrading buster => bullseye. Canonicalization of  /var/log/journal. Charles Curley <charlescurley@charlescurley.com> - 2021-09-30 03:30 +0200
  Re: Upgrading buster => bullseye.  Canonicalization of  /var/log/journal. Greg Wooledge <greg@wooledge.org> - 2021-09-28 19:50 +0200
    Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. peter@easthope.ca - 2021-09-29 22:30 +0200
      Re: Upgrading buster => bullseye. Canonicalization of  /var/log/journal. Greg Wooledge <greg@wooledge.org> - 2021-09-29 22:50 +0200
        Re: Upgrading buster => bullseye. Canonicalization of  /var/log/journal. David Wright <deblis@lionunicorn.co.uk> - 2021-09-30 05:40 +0200
          Re: Upgrading buster => bullseye. Canonicalization of  /var/log/journal. Nils <tuxifan@posteo.de> - 2021-09-30 06:00 +0200
          Re: Upgrading buster => bullseye. Canonicalization of  /var/log/journal. Greg Wooledge <greg@wooledge.org> - 2021-09-30 13:20 +0200
          Re: Upgrading buster => bullseye. Canonicalization of  /var/log/journal. Kushal Kumaran <kushal@locationd.net> - 2021-10-02 07:10 +0200
      Re: Upgrading buster => bullseye. Canonicalization of  /var/log/journal. Andrei POPESCU <andreimpopescu@gmail.com> - 2021-10-02 09:50 +0200
  Re: Upgrading buster => bullseye.  Canonicalization of  /var/log/journal. "Andrew M.A. Cater" <amacater@einval.com> - 2021-09-28 20:40 +0200
    Re: Upgrading buster => bullseye.  Canonicalization of  /var/log/journal. Greg Wooledge <greg@wooledge.org> - 2021-09-28 20:50 +0200

csiph-web