Ubuntu
linux package

  1. Bug #1737005
  2. Comment #0

Comment 0 for bug 1737005

Revision history for this message
Klaus Bielke (k-bielke) wrote :

With Ubuntu 16.04.3 LTS (Xenial Xerus), and mainline kernel 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and ureadahead.service. Sometimes udisks2.service failes too.

$ systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
● apparmor.service loaded failed failed LSB: AppArmor initialization
● udisks2.service loaded failed failed Disk Manager
● ureadahead.service loaded failed failed Read required files in advance

$ systemctl status apparmor.service
● apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, status=1/FAILURE)

Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor initialization...
Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles
Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel LSM.
Dez 07 18:04:51 lieselotte apparmor[689]: ...fail!
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process exited, code=exited status=1
Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor initialization.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed state.
Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 'exit-code'.