📖 ~1 min read
Table of contents
Symptom & Impact
An application crashes or denies service because AppArmor blocks file or capability access.
Environment & Reproduction
Common on SLES 15 after upgrading a packaged service whose profile lags behind the binary.
Root Cause Analysis
Profile path patterns no longer match actual binary locations or new file dependencies.
Quick Triage
Check `aa-status` and `journalctl -k | grep DENIED` to find rejected operations.
Step-by-Step Diagnosis
Use `aa-logprof` to walk through learned events and propose policy updates.

Solution – Primary Fix
Adjust the profile, reload with `apparmor_parser -r /etc/apparmor.d/`, and validate.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Place the profile in complain mode temporarily with `aa-complain` while investigating.
Verification & Acceptance Criteria
Application runs without further `apparmor=”DENIED”` kernel messages.
Rollback Plan
Restore the previous profile from `/etc/apparmor.d` backup if regression occurs.
Prevention & Hardening
Track profile updates with each package upgrade in change control.
Related Errors & Cross-Refs
Pairs with `apparmor=”DENIED” operation=”open”` audit lines.
Related tutorial: View the step-by-step tutorial for sles-15.
View all sles-15 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
SUSE AppArmor administration and aa-logprof usage docs.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.