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.
Bug 1308549 - Configuration file /etc/dbus-1/system.d/com.redhat.tuned.conf was not loaded on s390x
Summary: Configuration file /etc/dbus-1/system.d/com.redhat.tuned.conf was not loaded ...
Keywords:
Status: CLOSED DUPLICATE of bug 1258868
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dbus
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.3
Assignee: David King
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-15 13:41 UTC by Tereza Cerna
Modified: 2017-04-26 12:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-16 13:51:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tereza Cerna 2016-02-15 13:41:55 UTC 
Configuration file /etc/dbus-1/system.d/com.redhat.tuned.conf was not loaded.

Service tuned is dead after installation machine of architecture s390x. Restart of this service does not work. 

# journalctl -u dbus
...
úno 15 04:08:29 ibm-z10-56.rhts.eng.bos.redhat.com dbus[1100]: Encountered error 'Failed to open "/etc/dbus-1/system.d/com.redhat.tuned.conf": Permission denied' while parsing '/etc/dbus-1/system.d/com.redhat.tu
úno 15 04:08:29 ibm-z10-56.rhts.eng.bos.redhat.com dbus[1100]: [system] Reloaded configuration
úno 15 04:08:29 ibm-z10-56.rhts.eng.bos.redhat.com dbus-daemon[1100]: dbus[1100]: Encountered error 'Failed to open "/etc/dbus-1/system.d/com.redhat.tuned.conf": Permission denied' while parsing '/etc/dbus-1/sys
úno 15 04:08:29 ibm-z10-56.rhts.eng.bos.redhat.com dbus-daemon[1100]: dbus[1100]: [system] Reloaded configuration


Problem is solved when service dbus is restarted.


=== REPRODUCER ===

# rpm -q tuned dbus
tuned-2.5.1-4.el7_2.3.noarch
dbus-1.6.12-13.el7.s390x

# arch
s390x

# systemctl status tuned | grep Active
   Active: failed (Result: timeout) since Po 2016-02-15 07:24:50 EST; 18min ago
# systemctl start tuned
Job for tuned.service failed because a timeout was exceeded. See "systemctl status tuned.service" and "journalctl -xe" for details.

# tuned -D
...
2016-02-15 07:37:43,950 DEBUG    tuned.utils.plugin_loader: loading module tuned.plugins.plugin_disk
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/site-packages/tuned/exports/dbus_exporter.py", line 93, in _thread_code
    bus_name = dbus.service.BusName(self._bus_name, bus)
  File "/usr/lib64/python2.7/site-packages/dbus/service.py", line 131, in __new__
    retval = bus.request_name(name, name_flags)
  File "/usr/lib64/python2.7/site-packages/dbus/bus.py", line 303, in request_name
    'su', (name, flags))
  File "/usr/lib64/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.47" is not allowed to own the service "com.redhat.tuned" due to security policies in the configuration file
...

# rpm -qV tuned
# echo $?
0

# journalctl -u dbus 
...
úno 15 04:08:29 ibm-z10-56.rhts.eng.bos.redhat.com dbus[1100]: Encountered error 'Failed to open "/etc/dbus-1/system.d/com.redhat.tuned.conf": Permission denied' while parsing '/etc/dbus-1/system.d/com.redhat.tuned.conf'
...

=== SOLUTION ===

Problem was resolved by restart of dbus:

# systemctl status dbus | grep Active
   Active: active (running) since Po 2016-02-15 08:14:42 EST; 1min 4s ago
# systemctl status tuned | grep Active
   Active: failed (Result: timeout) since Po 2016-02-15 07:27:06 EST; 48min ago

# systemctl restart dbus
# systemctl restart tuned

# systemctl status tuned | grep Active
   Active: active (running) since Po 2016-02-15 08:16:05 EST; 2s ago

=== PROBLEM WAS NOT REPRODUCED WITH THE SAME VERSION OF DBUS AND OLDER VERSION OF TUNED ===

# rpm -q tuned dbus
tuned-2.5.1-4.el7_2.2.noarch
dbus-1.6.12-13.el7.s390x

# arch
s390x

# systemctl status tuned | grep Active
   Active: inactive (dead) since Po 2016-02-15 08:04:35 EST; 7min ago
# systemctl start tuned
# systemctl status tuned | grep Active
   Active: active (running) since Po 2016-02-15 08:12:36 EST; 2s ago
Comment 2 Jaroslav Škarvada 2016-02-15 14:27:10 UTC 
From the log it seems like some race, when RPM installs /etc/dbus-1/system.d/com.redhat.tuned.conf, it is sometimes not fully read and applied by dbus. Dbus restart seems to resolve the problem.
Comment 4 David King 2016-02-16 13:51:49 UTC 
Installing a new dbus configuration file does not automatically restart the daemon (and restarted the daemon can cause unexpected side effects, such as terminating graphical sessions), so this is in effect a duplicate of an RFE to load the new configuration file automatically.

*** This bug has been marked as a duplicate of bug 1258868 ***
Comment 5 Andrey Arapov 2017-04-26 12:39:07 UTC 
Not sure if this has been resolved already, since I have no access to see the bug 1258868. But ``killall -HUP dbus-daemon`` at the RPM's %post scriptlet should be sufficient.

I've hit a similar issue, but with the lightdm, see my comment https://bugzilla.redhat.com/show_bug.cgi?id=1428379#c9
Note You need to log in before you can comment on or make changes to this bug.