boot.apparmor - failed to load..failed

This document (7018745) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)
SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)

Situation

During boot, errors from AppArmor such as below can be seen:

boot.apparmor[562]: mkstemp: No such file or directory
boot.apparmor[562]: /etc/apparmor.d/sbin.klogd failed to load..failed
boot.apparmor[562]: mkstemp: No such file or directory
boot.apparmor[562]: /etc/apparmor.d/sbin.syslog-ng failed to load..failed

This is seen on systems with /var on a separate partition.

Resolution

The apparmor update to apparmor-2.8.2-54.1 released May 2017 includes the solution to resolve this problem. Please install the recommended update.

Instead to symlink to /var/cache/apparmor /var/lib/apparmor/cache is used now and apparmor.service includes an "After=var-lib.mount var.mount" unit.

Cause

AppArmor is starting early before /var is mounted. /etc/apparmor.d/cache is a symlink to /var/cache/apparmor. So when /var is on a separate partition, AppArmor won't start.

Additional Information

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.