Description of problem: selinux denial on usage port 4568 this port is used when syncing more nodes in mysql cluster Version-Release number of selected component (if applicable): rh-mariadb101 How reproducible: always Steps to Reproduce: 1. there is need of sync two cluster nodes # see bug 1332995 which means: 2, node1: stop maria 3, node2: add db 4, node1: start maria which is 'cause of syncing' with node2 Actual results: name_bind and name_connect to port 4568 type=AVC msg=audit(1462366535.270:761): avc: denied { name_bind } for pid=24652 comm="mysqld" src=4568 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket type=AVC msg=audit(1462366768.614:772): avc: denied { name_bind } for pid=25517 comm="mysqld" src=4568 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket type=AVC msg=audit(1462367206.718:792): avc: denied { name_bind } for pid=26553 comm="mysqld" src=4568 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket type=AVC msg=audit(1462367843.196:808): avc: denied { name_bind } for pid=27514 comm="mysqld" src=4568 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket type=AVC msg=audit(1462368086.137:823): avc: denied { name_bind } for pid=28475 comm="mysqld" src=4568 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket type=AVC msg=audit(1462368212.164:830): avc: denied { name_bind } for pid=28971 comm="mysqld" src=4568 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket type=AVC msg=audit(1462368516.010:836): avc: denied { name_connect } for pid=29149 comm="mysqld" dest=4568 scontext=system_u:system_r:mysqld_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket Expected results: no denial Additional info:
port 4568 is listed here: http://galeracluster.com/documentation-webpages/firewallsettings.html
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. https://access.redhat.com/errata/RHEA-2016:1156