Bug 1043490

Summary: SELinux is preventing /usr/sbin/sensord from 'add_name' accesses on the directory sensord.rrd.
Product: [Fedora] Fedora Reporter: steinach2810
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dominick.grift, dwalsh, lvrabec, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cc541b86d7074c583f78b9bad4ca0a405e08094295a43ddfd05a341a6749efcd
Fixed In Version: selinux-policy-3.12.1-74.16.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-05 12:33:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description steinach2810 2013-12-16 13:03:42 UTC
Description of problem:
sudo service sensord start


Redirecting to /bin/systemctl start  sensord.service
Warning: Unit file of sensord.service changed on disk, 'systemctl --system daemon-reload' recommended.
Job for sensord.service failed. See 'systemctl status sensord.service' and 'journalctl -xn' for details.


sudo systemctl status sensord.service


sensord.service - Sensor Information Logging
   Loaded: loaded (/usr/lib/systemd/system/sensord.service; disabled)
   Active: failed (Result: exit-code) since Mon 2013-12-16 15:01:05 EET; 57s ago
  Process: 20946 ExecStart=/usr/sbin/sensord -i $INTERVAL -l $LOG_INTERVAL --rrd-file /var/log/sensord.rrd (code=exited, status=1/FAILURE)

Dec 16 15:01:05 localhost.localdomain sensord[20946]: Creating round robin database
Dec 16 15:01:05 localhost.localdomain sensord[20946]: Error creating RRD file: /var/log/sensord.rrd: creating '/var/log/sensord.rrd...denied
Dec 16 15:01:05 localhost.localdomain systemd[1]: sensord.service: control process exited, code=exited status=1
Dec 16 15:01:05 localhost.localdomain systemd[1]: Failed to start Sensor Information Logging.
Dec 16 15:01:05 localhost.localdomain systemd[1]: Unit sensord.service entered failed state.

Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended.
SELinux is preventing /usr/sbin/sensord from 'add_name' accesses on the directory sensord.rrd.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that sensord should be allowed add_name access on the sensord.rrd directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep sensord /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:sensord_t:s0
Target Context                system_u:object_r:var_log_t:s0
Target Objects                sensord.rrd [ dir ]
Source                        sensord
Source Path                   /usr/sbin/sensord
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           lm_sensors-sensord-3.3.3-3.fc19.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-74.15.fc19.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.11.10-200.fc19.x86_64 #1 SMP Mon
                              Dec 2 20:28:03 UTC 2013 x86_64 x86_64
Alert Count                   4
First Seen                    2013-12-16 14:55:57 EET
Last Seen                     2013-12-16 15:01:05 EET
Local ID                      ba9a9356-8162-4ba0-ab84-d4af0bfaf94a

Raw Audit Messages
type=AVC msg=audit(1387198865.925:749503): avc:  denied  { add_name } for  pid=20946 comm="sensord" name="sensord.rrd" scontext=system_u:system_r:sensord_t:s0 tcontext=system_u:object_r:var_log_t:s0 tclass=dir


type=SYSCALL msg=audit(1387198865.925:749503): arch=x86_64 syscall=open success=no exit=EACCES a0=7fff329f2f10 a1=242 a2=1b6 a3=7fff329eff70 items=0 ppid=1 pid=20946 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=sensord exe=/usr/sbin/sensord subj=system_u:system_r:sensord_t:s0 key=(null)

Hash: sensord,sensord_t,var_log_t,dir,add_name

Additional info:
reporter:       libreport-2.1.9
hashmarkername: setroubleshoot
kernel:         3.11.10-200.fc19.x86_64
type:           libreport

Comment 1 Daniel Walsh 2013-12-16 16:26:09 UTC
467432ba9dea4c700b28a81a75908a2042a8c7a7 fixes this in git.

Comment 2 Daniel Walsh 2013-12-16 16:36:29 UTC
*** Bug 1043486 has been marked as a duplicate of this bug. ***

Comment 3 Lukas Vrabec 2013-12-17 10:04:35 UTC
back ported.

Comment 4 Fedora Update System 2013-12-20 10:14:14 UTC
selinux-policy-3.12.1-74.16.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-74.16.fc19

Comment 5 Fedora Update System 2013-12-21 02:09:42 UTC
Package selinux-policy-3.12.1-74.16.fc19:
* should fix your issue,
* was pushed to the Fedora 19 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.12.1-74.16.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-23691/selinux-policy-3.12.1-74.16.fc19
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-01-05 12:33:17 UTC
selinux-policy-3.12.1-74.16.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.