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.
I have installed the latest policy (3.7.19-251) with Zabbix 2.2.5-1. The Zabbix source rpm was taken from fc21 and repackaged for el6 - I pretty much followed/implemented the changes applied to the Zabbix22 package available from EPEL with a few minor differences.
This seems to resolve all the problems I was previously getting with the denials for the agent. However, I did get one denial for the server:
type=AVC msg=audit(1408552583.666:87): avc: denied { read } for pid=1504 comm="zabbix_server" name="zabbix_server.log" dev=dm-2 ino=524322 scontext=system_u:system_r:zabbix_t:s0 tcontext=unconfined_u:object_r:var_log_t:s0 tclass=file
This was resolved with the following:
semanage fcontext -a -t zabbix_log_t "/var/log/zabbixsrv(/.*)?"
restorecon -Rv /var/log/zabbixsrv
Looks like the rule for labelling the 'new/separate' server log directory and files needs to be added to the policy.
Many Thanks,
Dan H
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-2014-1568.html