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.
DescriptionAlex Williamson
2011-02-25 20:31:00 UTC
Description of problem:
/etc/init.d/dnsmasq.conf:
enable-dbus
$ service dnsmasq start
Starting dnsmasq:
dnsmasq: DBus error: Connection ":1.83" is not allowed to own the service "uk.org.thekelleys.dnsmasq" due to SELinux policy
[FAILED]
Version-Release number of selected component (if applicable):
dnsmasq-2.48-4.el6.x86_64
libselinux-2.0.94-3.el6.x86_64
libselinux-devel-2.0.94-3.el6.x86_64
selinux-policy-3.7.19-71.el6.noarch
selinux-policy-targeted-3.7.19-71.el6.noarch
libselinux-python-2.0.94-3.el6.x86_64
libselinux-utils-2.0.94-3.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Try to use enable-dbus option in dnsmasq
2.
3.
Actual results:
denied
Expected results:
supported
Additional info:
(In reply to comment #4)
> Can dnsmasq be autostarted by dbus?
I have no idea. I'm just trying to run a local dns caching/multiplexing server, starting via normal init scripts and using dbus to set and clear servers. I suppose it's possible to launch via dbus, but I've never tried it.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0526.html
Description of problem: /etc/init.d/dnsmasq.conf: enable-dbus $ service dnsmasq start Starting dnsmasq: dnsmasq: DBus error: Connection ":1.83" is not allowed to own the service "uk.org.thekelleys.dnsmasq" due to SELinux policy [FAILED] Version-Release number of selected component (if applicable): dnsmasq-2.48-4.el6.x86_64 libselinux-2.0.94-3.el6.x86_64 libselinux-devel-2.0.94-3.el6.x86_64 selinux-policy-3.7.19-71.el6.noarch selinux-policy-targeted-3.7.19-71.el6.noarch libselinux-python-2.0.94-3.el6.x86_64 libselinux-utils-2.0.94-3.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Try to use enable-dbus option in dnsmasq 2. 3. Actual results: denied Expected results: supported Additional info: