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.

Description of problem:
Bacula attempts to access postgres when configured for that as a back end, which is denied by default. By enabling 
setsebool daemons_enable_cluster_mode 1

Things work, however, I am unclear on whether this is to broad a hammer for this nail.

Version-Release number of selected component (if applicable):

selinux-policy-3.12.1-153.el7_0.10.noarch



Additional info:

#============= bacula_t ==============

#!!!! This avc is allowed in the current policy
allow bacula_t postgresql_t:unix_stream_socket connectto;
allow bacula_t postgresql_var_run_t:sock_file write;

Could you attach the AVCs?

Yes, the daemons_enable_cluster_mode boolean is to broad hammer for this nail :-)

Here you go:
node=example.com type=AVC msg=audit(1409171285.021:3863): avc:  denied  { write } for  pid=41802 comm="bacula-dir" name=".s.PGSQL.5432" dev="tmpfs" ino=1193189 scontext=system_u:system_r:bacula_t:s0 tcontext=system_u:object_r:postgresql_var_run_t:s0 tclass=sock_file

commit ac066dd52bb983c01d26002572200c1b717bee31
Author: Miroslav Grepl <mgrepl>
Date:   Tue Dec 2 14:04:10 2014 +0100

    Allow bacula to connect also to postgresql.

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://rhn.redhat.com/errata/RHBA-2015-0458.html