7.4.4 How to Resolve Issues with Apache?
Apache is not starting properly or it is not serving Web pages and you just installed a
new module or made a configuration change. When you install additional Apache
modules (like
apache2-mod_apparmor
) or make configuration changes to Apache,
you should profile Apache again to catch any additional rules that need to be added to
the profile.
7.4.5 Why are the Reports not Sent by
E-Mail?
When the reporting feature generates an HTML or CSV file that exceeds the default
size, the file is not sent. Mail servers have a default, hard limit for e-mail size. This
limitation can impede AppArmor's ability to send e-mails that are generated for reporting
purposes. If your mail is not arriving, this could be why. Consider the mail size limits
and check the archives if e-mails have not been received.
7.4.6 How to Exclude Certain Profiles from
the List of Profiles Used?
AppArmor always loads and applies all profiles that are available in its profile directory
(
/etc/apparmor.d/
). If you decide not to apply a profile to a certain application,
delete the appropriate profile or move it to another location where AppArmor would
not check for it.
7.4.7 Can I Manage Profiles for Applications
not Installed on my System?
Managing profiles with AppArmor requires you to have access to a the system's log
the application is running on. So you do not need to run the application on your profile
build host as long as you have access to the machine that runs the application. You can
run the application on one system, transfer the logs (
/var/log/audit.log
or, if
audit
is not installed,
/var/log/messages
) to your profile build host and run
aa-logprof -f
path_to_logfile
.
Support
123