Created attachment 524001 [details] Additional messages issued by snmpd Description of problem: When I try to start up snmpd with "systemctl start snmpd.service", the command hangs for a while, and then says the job failed. I see one AVC after the attempt: time->Tue Sep 20 13:04:33 2011 type=SYSCALL msg=audit(1316516673.513:6358): arch=c000003e syscall=46 success=no exit=-13 a0=b a1=7fffe27a2c90 a2=4000 a3=7fffe27a2a10 items=0 ppid=1 pid=16675 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="snmpd" exe="/usr/sbin/snmpd" subj=system_u:system_r:snmpd_t:s0 key=(null) type=AVC msg=audit(1316516673.513:6358): avc: denied { write } for pid=16675 comm="snmpd" name="notify" dev=tmpfs ino=7734 scontext=system_u:system_r:snmpd_t:s0 tcontext=system_u:object_r:init_var_run_t:s0 tclass=sock_file The "notify" sock_file it tries to talk to apparently is /var/run/systemd/notify; it has inode number 7734. The "type" in snmpd.service is "notify", and in /var/log/messages there are these messages: Sep 20 13:06:01 mimmi systemd[1]: snmpd.service operation timed out. Terminating. Sep 20 13:06:01 mimmi snmpd[16675]: Received TERM or STOP signal... shutting down... Sep 20 13:06:01 mimmi systemd[1]: Unit snmpd.service entered failed state. Version-Release number of selected component (if applicable): selinux-policy-targeted-3.10.0-28.fc16.noarch net-snmp-5.7-6.fc16.x86_64 systemd-35-1.fc16.x86_64 How reproducible: Every time Steps to Reproduce: 1. systemctl start snmpd.service Actual results: Job failed. See system logs and 'systemctl status' for details. Expected results: Snmpd up and running. Additional info: There are additional messages from snmpd in /var/log/messages. I don't BELIEVE these are the reason for the problems. If I start snmpd from the command line, these messages also show up, but snmpd seems to work anyway. But just in case, I attach those messages too.
Fixed in selinux-policy-targeted-3.10.0-31.fc16.noarch
Miroslav I think we should add this for all init domains.
Yes, this is needed.
selinux-policy-3.10.0-36.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-36.fc16
Package selinux-policy-3.10.0-36.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-36.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-36.fc16 then log in and leave karma (feedback).
selinux-policy-3.10.0-38.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.