Your message dated Fri, 30 Aug 2019 23:23:14 +0000
with message-id <[email protected]>
and subject line Bug#920234: fixed in systemd 243~rc2-1
has caused the Debian Bug report #920234,
regarding systemd: insufficient log options when there is a bad /etc/crypttab 
entry
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.)


-- 
920234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920234
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 240-4
Severity: normal

When I have a bogus /etc/crypttab entry (for example when converting an
encrypted laptop to a virtual machine that's not encrypted) the boot process
hangs for 90 seconds for no obvious reason.

[    **] A start job is running for /dev/dis·9597-dbdb2fedbd1f (24s / 1min 30s)

When seeing the above anyone who doesn't know that "grep -R dbdb2fedbd1f /etc"
is necessary will have trouble determining the cause of this.

# systemd-analyze blame
Bootup is not yet finished 
(org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
# systemctl list-jobs
JOB UNIT                                                           TYPE  STATE  
181 dev-disk-by\x2duuid-…75\x2d410c\x2d9597\x2ddbdb2fedbd1f.device start running
179 systemd-cryptsetup@nvme0n1p2_crypt.service                     start waiting

2 jobs listed

The above commands run during the boot process makes the problem obvious.  But
what if the cryptsetup command completely fails before the sysadmin logs in?

# systemd-analyze blame|head
          1.051s ifupdown-wait-online.service
           958ms [email protected]
           753ms [email protected]
           494ms udisks2.service
           480ms networking.service
           445ms dev-vda.device
           260ms accounts-daemon.service
           245ms gdomap.service
           217ms systemd-timesyncd.service
           216ms auditd.service

I would hope to see a 90 second entry in the above, but we don't get one.

# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 31.348s
└─multi-user.target @1min 31.347s
  └─postfix.service @1min 31.339s +7ms
    └─[email protected] @1min 30.583s +753ms
      └─basic.target @1min 30.512s
        └─sockets.target @1min 30.506s
          └─dbus.socket @1min 30.505s
            └─sysinit.target @1min 30.492s
              └─systemd-update-utmp.service @902ms +41ms
                └─auditd.service @664ms +216ms
                  └─systemd-tmpfiles-setup.service @602ms +50ms
                    └─local-fs.target @598ms
                      └─run-user-0.mount @1min 45.931s
                        └─swap.target @940ms
                          └─dev-vdb.swap @909ms +27ms
                            └─dev-vdb.device @876ms

I expect to see something with +90s in the above, but it doesn't happen.
Something between systemd-update-utmp.service and sysinit.target took 90
seconds and there's no obvious way of discovering what it was.

-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages systemd depends on:
ii  adduser          3.118
ii  libacl1          2.2.52-3+b1
ii  libapparmor1     2.13.2-3
ii  libaudit1        1:2.8.4-2
ii  libblkid1        2.33.1-0.1
ii  libc6            2.28-5
ii  libcap2          1:2.25-1.2
ii  libcryptsetup12  2:2.0.6-1
ii  libgcrypt20      1.8.4-4
ii  libgnutls30      3.6.5-2
ii  libgpg-error0    1.33-3
ii  libidn11         1.33-2.2
ii  libip4tc0        1.8.2-3
ii  libkmod2         25-2
ii  liblz4-1         1.8.3-1
ii  liblzma5         5.2.2-1.3
ii  libmount1        2.33.1-0.1
ii  libpam0g         1.1.8-4
ii  libseccomp2      2.3.3-3
ii  libselinux1      2.8-1+b1
ii  libsystemd0      240-4
ii  mount            2.33.1-0.1
ii  util-linux       2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus            1.12.12-1
ii  libpam-systemd  240-4

Versions of packages systemd suggests:
ii  policykit-1        0.105-25
ii  systemd-container  240-4

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.132
ii  udev             240-4

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 243~rc2-1

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 31 Aug 2019 00:20:41 +0200
Source: systemd
Architecture: source
Version: 243~rc2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers 
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Closes: 807464 851402 904913 913222 920234
Changes:
 systemd (243~rc2-1) experimental; urgency=medium
 .
   * New upstream version 243~rc2
     - man: document that "systemd-analyze blame/critical-chain" is not useful
       to track down job latency. (Closes: #920234)
     - systemctl: process all units matched by a glob in the cat verb by
       default. (Closes: #904913)
     - units: automatically revert to /run logging on shutdown if necessary.
       Prevents /var staying busy on shutdown due to journald.
       (Closes: #851402)
     - bash-completion: don't sort syslog priorities. (Closes: #913222)
     - man: add example for setting multiple properties at once.
       (Closes: #807464)
   * Rebase patches
   * Update symbols file for libsystemd0
   * core: stop removing non-existent and duplicate lookup paths
   * Install static-nodes-permissions.conf tmpfile in udev
Checksums-Sha1:
 3ba3828b7ce02cc70dd4974564bf9bc95c564b57 4975 systemd_243~rc2-1.dsc
 d4bd44fcce10491b4d373420738c4560b8a324ef 8239802 systemd_243~rc2.orig.tar.gz
 5ed51f986836d1e46956ffc9a1676ef1940103e7 145236 systemd_243~rc2-1.debian.tar.xz
 8672ad41348d9f7b51267c68646d3bcd18e8381c 9472 
systemd_243~rc2-1_source.buildinfo
Checksums-Sha256:
 ee826d2076a8aea77e37174f8c5b4e51e129f3a25f4d219dd121c41a68089128 4975 
systemd_243~rc2-1.dsc
 ac0231e2ef59b5cf72e8f312ed399275aeb671adba69cb295333c646e6c950d5 8239802 
systemd_243~rc2.orig.tar.gz
 27c86752d8ed68ba39c726954ce8c4717f37325ddb7a7844da41da85b530dc06 145236 
systemd_243~rc2-1.debian.tar.xz
 17fe729f85ae5f742a4ae473c3e0fc35849daed110450a1ef3d9ba45a12d49be 9472 
systemd_243~rc2-1_source.buildinfo
Files:
 298b4eedd0d31e468beabd8bda0821e6 4975 admin optional systemd_243~rc2-1.dsc
 8afd4a6fa32a9269742e448b5a262189 8239802 admin optional 
systemd_243~rc2.orig.tar.gz
 596549e7ffdb97d41a24c25b4700890c 145236 admin optional 
systemd_243~rc2-1.debian.tar.xz
 381d02d585508003f20ff0745c897a82 9472 admin optional 
systemd_243~rc2-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl1pqhIACgkQauHfDWCP
ItwuXQ/9EpLj7W0gY/cjeC0dG9kFAZvgVBR9txtwydGpOKutZnIz8VmfYDDHk09U
e1CIvRWF83TdvWfGC9OuDtx35mp6Hd30r1yue53woYjgMDVJWCH/nDHttKhZlpse
FWnWT6GnTk7EQTs3DGsDLuP1htro1ivDWuSOlFsuwCAxnPS8srXuvk6+O/90HoM+
d3RIcJ75NACxc3VjOaKCkhpVO6cKMFgPliY6cPpmbWI0cG8aROGn0QFBFMYl6+jS
LLt17pPyD5DUGqUuTiM20sM8fpAj81cUmEKhEusH9u2GcyFtVRCyitbsktRJWgZO
/u62LXP70ortZsm+21cFW1ukZ6OXvwMvI+rctZqpQVGH0MqxaAynpBTO+PC12zDY
+T1aM6Rk/PXKTK2AnNHDpUWZpZUKQiz/ikHA6SucPCpbIqu4ajyfPOSmJmUnuuhx
knihGglsgjSQStFb2usIPEDKNkXt5vHjTGYQrkogKNtHVqB32aj5psUXwGhbAqLP
hYSZ9QUAX8UMt6yNaof25yUsuGaP98cFJ5ORy6J4XFqGEKPQ24UemihbmMa+6xir
wtCpjLRhJ0/MhUkve5ItYFM1+e/BQdI9CGv69mGWgkw6bxHFXFm/PK7KATpwGFb6
bt7PebOdjFGtMjrdLufH4CayX7gV8vYaRkpH67nR0cwS7WGQEr8=
=u1jT
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to