Novell LINUX ENTERPRISE DESKTOP 11, Manual, Page: 374 / 450

28.4 Troubleshooting
This section lists the most common problems and error messages that may occur using
Novell AppArmor.
28.4.1 How to React to odd Application
Behavior?
If you notice odd application behavior or any other type of application problem, you
should first check the reject messages in the log files to see if AppArmor is too closely
constricting your application. To check reject messages, start YaST > Novell AppArmor
and go to AppArmor Reports. Select View Archive and App Aud for the application audit
report. You can filter dates and times to narrow down the specific periods when the
unexpected application behavior occurred.
If you detect reject messages that indicate that your application or service is too closely
restricted by AppArmor, update your profile to properly handle your use case of the
application. Do this with the Update Profile Profile Wizard in YaST, as described in
Section 23.5, “Updating Profiles from Log Entries” (page 281).
If you decide to run your application or service without AppArmor protection, remove
the application's profile from
/etc/apparmor.d
or move it to another location.
28.4.2 My Profiles do not Seem to Work
Anymore …
If you have been using previous versions of AppArmor and have updated your system,
but kept your old set of profiles, you might notice some applications behaving
strangely or not working at all which seemed to work perfectly before you updated.
This version of AppArmor introduces a set of new features to the profile syntax and
the AppArmor tools that might cause trouble with older versions of the AppArmor
profiles. The features concerned are:
• File Locking
360 Security Guide