Bug#1138184: systemd: Also seems to affect logcheck.service

[David Witbrodt]

Package: systemd
Followup-For: Bug #1138184
Control: found 1138184 261.2-1


I tested the latest version (261.2-1) to make sure the bug (libopenal 
broken on my desktop) is still there.  It is.

Lately, I've noticed that sometimes 'top' is showing a runaway 'sed' 
process.  It never occurred to me that it could be related to this bug; 
I guessed that an upgrade of 'sed' (or some package using sed) might 
have introduced a bug, and that a later update (hopefully) would fix it.

At some point, I noticed that the runaway 'sed' was happening 
immediately upon booting, so then I decided to look into it more.  I 
quickly discovered that 'sed' was being run by logcheck, and this was 
being run by systemd.

When things are working correctly, upon boot/reboot I can see this 
output from 'systemctl status':

     # systemctl status logcheck.service

     ○ logcheck.service - logcheck
          Loaded: loaded (/usr/lib/systemd/system/logcheck.service; static)
     [...]
     Jul 24 14:02:01 desktop systemd[1]: Starting logcheck.service - 
logcheck...
     Jul 24 14:02:23 desktop systemd[1]: logcheck.service: Deactivated 
successfully.
     Jul 24 14:02:23 desktop systemd[1]: Finished logcheck.service - 
logcheck.
     Jul 24 14:02:23 desktop systemd[1]: logcheck.service: Consumed 
6.139s CPU time over 22.090s wall clock time, 781.2M memory peak.


So, in this example the process terminated normally in about 20 seconds.

When the bug is affecting things, I see this:

     # systemctl status logcheck.service

     ○ logcheck.service - logcheck
          Loaded: loaded (/usr/lib/systemd/system/logcheck.service; static)
     [...]
     Jul 24 14:02:01 desktop systemd[1]: Starting logcheck.service - 
logcheck...


and the process is hung (never terminates).

I realize now that the pattern is:  each time I test a new systemd from 
the Debian repository, libopenal is broken and the logcheck.service 
hangs at boot time.  When I install my own locally built packages which 
have commit a05fe6684a reverted, both libopenal and logcheck.service 
work correctly.

I have now verified that a revert of commit a05fe6684a on top of 261.2-1 
still fixes the bug for me (as with previous versions mentioned in 
earlier messages in this bug report).


-- System Information:
Debian Release: forky/sid
   APT prefers unstable
   APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 7.1.4+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd is related to:
ii  dbus-user-session  1.16.2-5+b1
pn  dracut             <none>
ii  initramfs-tools    0.151
ii  libnss-systemd     261.2+revert.a05fe6684a-1+dwlocal1
ii  libpam-systemd     261.2+revert.a05fe6684a-1+dwlocal1
ii  udev               261.2+revert.a05fe6684a-1+dwlocal1