Bug 155874 - snmpd will not start under fc3 default
snmpd will not start under fc3 default
Status: CLOSED DUPLICATE of bug 155873
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-25 02:22 EDT by Rob Kearey
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-26 15:29:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Rob Kearey 2005-04-25 02:22:45 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
snmpd will not start under fc3 with targeted policy enabled. It starts fine when selinux is set to permissive mode.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-1.17.30-2.96

How reproducible:
Always

Steps to Reproduce:
1. set selinux to enforcing mode
2. start snmpd
3. ... watch it silently fail
  

Actual Results:  snmpd fails to start

Expected Results:  snmpd should start as normail

Additional info:

audit(1114408867.443:0): avc:  denied  { read } for  pid=3785 exe=/usr/sbin/snmpd name=config dev=dm-0 ino=488072 scontext=root:system_r:snmpd_t tcontext=system_u:object_r:selinux_config_t tclass=file
audit(1114408867.444:0): avc:  denied  { getattr } for  pid=3785 exe=/usr/sbin/snmpd path=/etc/selinux/config dev=dm-0 ino=488072 scontext=root:system_r:snmpd_t tcontext=system_u:object_r:selinux_config_t tclass=file
Comment 1 Sitsofe Wheeler 2005-04-26 13:31:28 EDT
This look like a dup of bug #155873
Comment 2 Daniel Walsh 2005-04-26 15:29:14 EDT

*** This bug has been marked as a duplicate of 155873 ***

Note You need to log in before you can comment on or make changes to this bug.