Bug 1229406 - AVC: osa dispatcher doesn't start on Fedora 22
Summary: AVC: osa dispatcher doesn't start on Fedora 22
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space24
TreeView+ depends on / blocked
 
Reported: 2015-06-08 15:45 UTC by Pavel Studeník
Modified: 2015-10-08 13:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-08 13:26:11 UTC
Embargoed:


Attachments (Terms of Use)

Description Pavel Studeník 2015-06-08 15:45:32 UTC
Description of problem:
Service osa dispatcher is not running on Fedora 22 when mode of SELinux is enforcing.

Version-Release number of selected component (if applicable):
spacewalk-selinux-2.3.2-1.fc22.noarch

How reproducible:
always on Fedora 22

Steps to Reproduce:
1. install spacewalk on fedora 22
2. systemctl status osa-dispatcher.service


Actual results:
# tail /var/log/audit/audit.log

ptype=USER_AVC msg=audit(1433777936.337:3115): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc:  received setenforce notice (enforcing=0)  exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
type=AVC msg=audit(1433777937.592:3116): avc:  denied  { execmem } for  pid=21114 comm="osa-dispatcher" scontext=system_u:system_r:osa_dispatcher_t:s0 tcontext=system_u:system_r:osa_dispatcher_t:s0 tclass=process permissive=1
type=SERVICE_START msg=audit(1433777937.675:3117): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=osa-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'


Expected results:
osa dispatcher works with selinux

Additional info:
● osa-dispatcher.service - OSA Dispatcher daemon
   Loaded: loaded (/usr/lib/systemd/system/osa-dispatcher.service; enabled; vendor preset: disabled)
   Active: failed (Result: core-dump) since Po 2015-06-08 11:41:10 EDT; 2s ago
  Process: 21166 ExecStart=/usr/sbin/osa-dispatcher --pid-file /var/run/osa-dispatcher.pid (code=dumped, signal=SEGV)
  Process: 21163 ExecStartPre=/bin/rm -f /var/run/osa-dispatcher.pid (code=exited, status=0/SUCCESS)
 Main PID: 21118 (code=killed, signal=TERM)

čen 08 11:41:09 hp-dl360pgen8-09.khw.lab.eng.bos.redhat.com systemd[1]: Starting OSA Dispatcher daemon...
čen 08 11:41:10 hp-dl360pgen8-09.khw.lab.eng.bos.redhat.com systemd[1]: osa-dispatcher.service: control process exited, code=dumped status=11
čen 08 11:41:10 hp-dl360pgen8-09.khw.lab.eng.bos.redhat.com systemd[1]: Failed to start OSA Dispatcher daemon.
čen 08 11:41:10 hp-dl360pgen8-09.khw.lab.eng.bos.redhat.com systemd[1]: Unit osa-dispatcher.service entered failed state.
čen 08 11:41:10 hp-dl360pgen8-09.khw.lab.eng.bos.redhat.com systemd[1]: osa-dispatcher.service failed.

Comment 1 Tomáš Kašpárek 2015-07-09 13:47:40 UTC
spacewalk.git(master): 3025ed827e87d53a63c1e25177bc98d3c1ba3b6a

Comment 2 Jan Dobes 2015-10-08 13:26:11 UTC
Spacewalk 2.4 has been released.


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