| 2017-12-07 18:00:30 |
Klaus Bielke |
bug |
|
|
added bug |
| 2017-12-07 18:01:58 |
Klaus Bielke |
description |
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'. |
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu 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'. |
|
| 2017-12-07 18:02:39 |
Klaus Bielke |
description |
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu 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'. |
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and ureadahead.service. Sometimes udisks2.service fails 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'. |
|
| 2017-12-07 18:03:54 |
Klaus Bielke |
affects |
apparmor (Ubuntu) |
linux (Ubuntu) |
|
| 2017-12-07 18:08:39 |
Klaus Bielke |
description |
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and ureadahead.service. Sometimes udisks2.service fails 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'. |
With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and ureadahead.service. Sometimes udisks2.service fails too.
$ uname -a
Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25 UTC 2017 i686 i686 i686 GNU/Linux
$ 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'. |
|
| 2017-12-07 18:30:04 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2018-01-04 03:12:33 |
Klaus Bielke |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2018-03-22 21:49:46 |
Dragutsan Alexandr |
bug |
|
|
added subscriber Dragutsan Alexandr |
