Bug 736388
Summary: | SELinux is preventing /usr/sbin/pulse from executing /usr/sbin/fos | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Milos Malik <mmalik> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | dwalsh, ksrot |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.7.19-112.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 10:18:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Milos Malik
2011-09-07 15:06:26 UTC
I am fixing a bug in the policy. Fixed in selinux-policy-3.7.19-110.el6 Is this a default port? # rpm -qf /etc/sysconfig/ha/web/secure/help.php piranha-0.8.5-7.el6.x86_64 # rpm -V piranha # grep -A 3 -i "heartbeat runs on port" /etc/sysconfig/ha/web/secure/help.php Heartbeat runs on port: It is possible to alter the port that heartbeat runs on. The default if not set is 1050. Normally you should not have to touch this. </PRE> # cma 1050/udp # CORBA Management Agent We currently have corenet_udp_bind_apertus_ldp_port(piranha_pulse_t) corenet_udp_bind_cma_port(piranha_pulse_t) Should we label this port as either of these? (In reply to comment #7) > We currently have > > corenet_udp_bind_apertus_ldp_port(piranha_pulse_t) > corenet_udp_bind_cma_port(piranha_pulse_t) This is a fix which I added to Fedora. Will add to RHEL6. > > > Should we label this port as either of these? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1511.html |