Novell APPARMOR 1.2, Administration Manual, Page: 120 / 130

To check reject messages, start YaST → Novell AppArmor and go to AppArmor
Reports. Select View Archive and App Aud for the applications audit report. You
can filter dates and times to narrow down the specific periods when application
behavior began.
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 mod_change_hat) or make
configuration changes to Apache, you should run through profiling Apache again
to catch any additional rules they need to be added to the profile.
Reports are not being sent via 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.
Users must be aware of the mail size limits and should check their archives if e-
mails have not been received.
Excluding certain profiles from the list of profiles used
AppArmor always loads and applies all profiles that are available in its profile di-
rectory (
/etc/subdomain.d/
). If you decide not to apply a profile to a certain
application, either delete the appropriate profile or move it to another location
where AppArmor would not check for it.
AppArmor operation can generate various errors. Here is a list of possible errors and
how to resolve them.
Can’t find subdomain_parser
If you run logprof as a non-root user, such as tux, you are likely to see this error:
tux@localhost:~> /usr/sbin/logprof
Can’t find subdomain_parser.
NOTE
You should run logprof only as root.
120