bonjour,
voici les messages:
Starting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed. See 'systemctl status apparmor.service' and 'journalctl -xn' for details.
failed!
systemctl status apparmor.service
? apparmor.service - LSB: AppArmor initialization
Loaded: loaded (/etc/init.d/apparmor)
Active: failed (Result: exit-code) since lun. 2015-01-26 16:05:13 CET; 24s ago
Process: 24196 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
janv. 26 16:05:13 debian apparmor[24196]: Starting AppArmor profiles:AppArmor parser error for /etc/apparmor.d/usr.sbin.cups-browsed in /etc/apparmor.d/usr.sbin.cups-bro...ups-browsed'
janv. 26 16:05:13 debian apparmor[24196]: AppArmor parser error for /etc/apparmor.d/usr.sbin.cups-browsed in /etc/apparmor.d/usr.sbin.cups-browsed at line 15: Could not ...ups-browsed'
janv. 26 16:05:13 debian apparmor[24196]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.dovecot
janv. 26 16:05:13 debian apparmor[24196]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld in /etc/apparmor.d/usr.sbin.mysqld at line 44: Could not open 'local/...sbin.mysqld'
janv. 26 16:05:13 debian apparmor[24196]: failed!
janv. 26 16:05:13 debian systemd[1]: apparmor.service: control process exited, code=exited status=123
janv. 26 16:05:13 debian systemd[1]: Failed to start LSB: AppArmor initialization.
janv. 26 16:05:13 debian systemd[1]: Unit apparmor.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
je ne sais pas s'il s'agit d'un bug ou d'un problème de configuration, sous Wheezy je n'avais pas ça, même constat sur les 2 noyaux:
3.2.57-custom ou 3.16.0-4-amd64
Dernière modification par nikau (27-01-2015 14:21:21)
Debian
Debian-France
Debian-Facile
Debian-fr.org
Forum-Debian.fr
Debian ?
Communautés
