Hide Forgot
$ rpm -qa mdadm* selinux* kernel* dracut* |sort dracut-011-15.git20110720.noarch kernel-3.0.0-1.fc16.x86_64 kernel-headers-3.0.0-1.fc16.x86_64 mdadm-3.2.2-6.fc16.x86_64 selinux-policy-3.10.0-10.fc16.noarch selinux-policy-targeted-3.10.0-10.fc16.noarch
Created attachment 515458 [details] screenshot
Could you execute after boot # dmesg |grep avc
[ 27.953316] type=1400 audit(1311758709.845:4): avc: denied { mmap_zero } for pid=624 comm="vbetool" scontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tcontext=system_u:system_r:vbetool_t:s0-s0:c0.c1023 tclass=memprotect [ 29.349767] type=1400 audit(1311758711.242:5): avc: denied { read } for pid=783 comm="mdadm" name="md1" dev=devtmpfs ino=9115 scontext=system_u:system_r:mdadm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:device_t:s0 tclass=blk_file [ 29.349786] type=1400 audit(1311758711.242:6): avc: denied { read } for pid=784 comm="mdadm" name="md0" dev=devtmpfs ino=1620 scontext=system_u:system_r:mdadm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:device_t:s0 tclass=blk_file [ 60.434086] type=1400 audit(1311758742.326:7): avc: denied { setattr } for pid=1113 comm="abrtd" name="abrt" dev=tmpfs ino=14877 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_run_t:s0 tclass=dir [ 61.599181] dbus[1155]: avc: netlink poll: error 4 [ 3541.519643] type=1400 audit(1311762223.412:8): avc: denied { setattr } for pid=3616 comm="abrtd" name="abrt" dev=tmpfs ino=14877 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_run_t:s0 tclass=dir [ 3575.594615] type=1400 audit(1311762257.486:9): avc: denied { unlink } for pid=3658 comm="abrtd" name="abrt.socket" dev=tmpfs ino=619612 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:var_run_t:s0 tclass=sock_file [ 3628.823278] type=1400 audit(1311762310.715:11): avc: denied { unlink } for pid=3812 comm="abrtd" name="abrt.socket" dev=tmpfs ino=619612 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:var_run_t:s0 tclass=sock_file Nice! But if they are logged, why sealert is ignoring them?
If the alerts happen before auditd is started, I guess they do not get sent to setroubleshoot. First I would remove vbetool if you do not need it. Probably you do not. The device and abrt directory are mislabeled. Is this the machine with the readonly /run?
(In reply to comment #4) > If the alerts happen before auditd is started, I guess they do not get sent to > setroubleshoot. > > First I would remove vbetool if you do not need it. Probably you do not. > > The device and abrt directory are mislabeled. Is this the machine with the > readonly /run? It's the only system I have. It's been relabeled a lot of times. That does not change the avcs
You have several bugs reporting the same thing. I have just changed the upstream policy to create the /dev/md* files with the correct label. The /var/run/abrt directory is getting created with the wrong label. Some entity other then abrt is creating this directory and labeling it incorrectly. If it is systemd, then systemd has a problem.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.