Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAndreas Freudenreich
2017-02-02 22:26:57 UTC
Created attachment 1247256[details]
output from audit2allow -a
Description of problem:
I tried to set up a zabbix userparameter which uses redis-cli to retrieve redis stats. The zabbix GUI complains with "could not connect to redis at 127.0.0.1:6379: permission denied". When I turn of selinux, it works. Setting the "zabbix_can_network"sebool to "on" does not help.
audit2allow shows a missing type enforcement allow rule from zabbix_agent_t to redis_port_t:tcp_socket
Version-Release number of selected component (if applicable):
selinux-policy 3.13.1-102.el7_3.13
zabbix-agent 2.4.6-1.el7
redis 3.2.4-1
How reproducible: always
Steps to Reproduce:
1.setup zabbix userparameter using the redis-cli
2.set up and observe a zabbix item for redis in the zabbix server
Actual results:
Zabbix server GUI shows error: "could not connect to redis at 127.0.0.1:6379: permission denied"
Expected results:
No error - zabbix should have access to the redis tcp port
Additional info:
Comment 1Andreas Freudenreich
2017-02-02 22:28:35 UTC
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/RHBA-2018:3111
Created attachment 1247256 [details] output from audit2allow -a Description of problem: I tried to set up a zabbix userparameter which uses redis-cli to retrieve redis stats. The zabbix GUI complains with "could not connect to redis at 127.0.0.1:6379: permission denied". When I turn of selinux, it works. Setting the "zabbix_can_network"sebool to "on" does not help. audit2allow shows a missing type enforcement allow rule from zabbix_agent_t to redis_port_t:tcp_socket Version-Release number of selected component (if applicable): selinux-policy 3.13.1-102.el7_3.13 zabbix-agent 2.4.6-1.el7 redis 3.2.4-1 How reproducible: always Steps to Reproduce: 1.setup zabbix userparameter using the redis-cli 2.set up and observe a zabbix item for redis in the zabbix server Actual results: Zabbix server GUI shows error: "could not connect to redis at 127.0.0.1:6379: permission denied" Expected results: No error - zabbix should have access to the redis tcp port Additional info: