RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1198439 - [Gluster] Selinux blocks execution of gluster-nagios plugins in the glusterfs node
Summary: [Gluster] Selinux blocks execution of gluster-nagios plugins in the glusterfs...
Keywords:
Status: CLOSED DUPLICATE of bug 1198436
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: selinux-policy
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Miroslav Grepl
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1169221
TreeView+ depends on / blocked
 
Reported: 2015-03-04 07:10 UTC by Timothy Asir
Modified: 2015-07-21 11:40 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-03 09:32:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Timothy Asir 2015-03-04 07:10:12 UTC
Description of problem:
Selinux blocks execution of gluster-nagios plugins in the glusterfs node

Steps to Reproduce:
1. In the gluster-nagios server and glusterfs nodes installed setup,
   create a gluster volume and set cluster.server-quorum-type to server
2. bring down one node and check for Cluster-Quorum passive check service
   status information.

Actual results:
Its just displays "OK" in an selinux enabled system.

Expected results:
It should display an appropriate message when all the nodes are down or some nodes or up.

Additional info:
type=AVC msg=audit(1425377014.260:527): avc:  denied  { name_connect } for  pid=4416 comm="send_nsca" dest=5667 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
type=SYSCALL msg=audit(1425377014.260:527): arch=c000003e syscall=42 success=yes exit=0 a0=1 a1=7fffe7a9fdc0 a2=10 a3=1999999999999999 items=0 ppid=4407 pid=4416 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="send_nsca" exe="/usr/sbin/send_nsca" subj=system_u:system_r:syslogd_t:s0 key=(null)


It works for us when we enable the selinux policy using the following selinux policy:

module nsca 1.0;

require {
	type syslogd_t;
	type port_t;
	class tcp_socket name_connect;
}

#============= syslogd_t ==============

#!!!! This avc can be allowed using the boolean 'allow_ypbind'
allow syslogd_t port_t:tcp_socket name_connect;

Comment 2 Miroslav Grepl 2015-04-03 09:32:10 UTC

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

Comment 3 Sahina Bose 2015-04-07 13:14:44 UTC
Hi Miroslav,
This bug is to do with SELinux issues on the gluster node running the nrpe and nsca plugins, whereas Bug 1198436 is to do with issues on Nagios server.

Would both these issues be fixed with the same policy?


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