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 1510287 - "virtlogd failed to connect to socket /run/dbus/system_bus_socket" logged when start a guest
Summary: "virtlogd failed to connect to socket /run/dbus/system_bus_socket" logged whe...
Keywords:
Status: CLOSED DUPLICATE of bug 1547250
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Erik Skultety
QA Contact: Yanqiu Zhang
URL:
Whiteboard:
: 1523187 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-07 06:30 UTC by yafu
Modified: 2018-06-29 09:47 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-29 09:47:23 UTC
Target Upstream Version:
Embargoed:
yanqzhan: needinfo-

Attachments (Terms of Use)

Description yafu 2017-11-07 06:30:54 UTC 
Description of problem:
"Failed to connect to socket /run/dbus/system_bus_socket: Permission denied" logged when start a guest.

Version-Release number of selected component (if applicable):
libvirt-3.9.0-1.el7.x86_64
3.10.0-768.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Start a guest:
#virsh start rhel7.3-min
Domain rhel7.3-min started

2.Check the log in syslog:
#cat /var/log/messages
...
Nov  7 14:17:59 dhcp-66-71-72 virtlogd: 2017-11-07 06:17:59.018+0000: 31823: error : virDBusGetSystemBus:109 : internal error: Unable to get DBus system bus connection: Failed to connect to socket /run/dbus/system_bus_socket: Permission denied
...

Actual results:
Error log report.

Expected results:
No error log report.

Additional info:
Comment 2 Ján Tomko 2017-12-07 11:52:26 UTC 
*** Bug 1523187 has been marked as a duplicate of this bug. ***
Comment 3 Erik Skultety 2018-05-21 11:45:23 UTC 
Can you still reproduce the issue with libvirt 4.3.0?
Comment 4 Erik Skultety 2018-06-28 12:29:12 UTC 
Ping, can you still reproduce this issue with libvirt 4.5.0?
Comment 5 Yanqiu Zhang 2018-06-28 14:40:12 UTC 
I can't even reproduce with the original libvirt-3.9.0-1.el7.x86_64 in comment 0, or latest libvirt-4.4.0-2.el7.x86_64.
yafu, are there any missing steps to reproduce it? Could you provide your test result pls if possible?
Comment 6 Yanqiu Zhang 2018-06-29 09:25:18 UTC 
1.Try to reproduce:
(1). Can reproduce with：
kernel-3.10.0-768.el7.x86_64
qemu-kvm-rhev-2.10.0-21.el7_5.4.x86_64
libvirt-3.9.0-1.el7.x86_64
python-slip-dbus-0.4.0-4.el7.noarch
dbus-libs-1.10.24-3.el7.x86_64
dbus-1.10.24-3.el7.x86_64
dbus-python-1.1.1-9.el7.x86_64
dbus-glib-0.100-7.el7.x86_64
selinux-policy-3.13.1-175.el7.noarch

(2). Not reproduced after only update libvirt version:
libvirt-3.9.0-14.el7_5.6.x86_64
===================********===============================
Updated:
  libvirt.x86_64 0:3.9.0-14.el7_5.6                                                                                                   

Dependency Updated:
  libvirt-client.x86_64 0:3.9.0-14.el7_5.6                           libvirt-daemon.x86_64 0:3.9.0-14.el7_5.6                        
  libvirt-daemon-config-network.x86_64 0:3.9.0-14.el7_5.6            libvirt-daemon-config-nwfilter.x86_64 0:3.9.0-14.el7_5.6        
  libvirt-daemon-driver-interface.x86_64 0:3.9.0-14.el7_5.6          libvirt-daemon-driver-lxc.x86_64 0:3.9.0-14.el7_5.6             
  libvirt-daemon-driver-network.x86_64 0:3.9.0-14.el7_5.6            libvirt-daemon-driver-nodedev.x86_64 0:3.9.0-14.el7_5.6         
  libvirt-daemon-driver-nwfilter.x86_64 0:3.9.0-14.el7_5.6           libvirt-daemon-driver-qemu.x86_64 0:3.9.0-14.el7_5.6            
  libvirt-daemon-driver-secret.x86_64 0:3.9.0-14.el7_5.6             libvirt-daemon-driver-storage.x86_64 0:3.9.0-14.el7_5.6         
  libvirt-daemon-driver-storage-core.x86_64 0:3.9.0-14.el7_5.6       libvirt-daemon-driver-storage-disk.x86_64 0:3.9.0-14.el7_5.6    
  libvirt-daemon-driver-storage-gluster.x86_64 0:3.9.0-14.el7_5.6    libvirt-daemon-driver-storage-iscsi.x86_64 0:3.9.0-14.el7_5.6   
  libvirt-daemon-driver-storage-logical.x86_64 0:3.9.0-14.el7_5.6    libvirt-daemon-driver-storage-mpath.x86_64 0:3.9.0-14.el7_5.6   
  libvirt-daemon-driver-storage-rbd.x86_64 0:3.9.0-14.el7_5.6        libvirt-daemon-driver-storage-scsi.x86_64 0:3.9.0-14.el7_5.6    
  libvirt-libs.x86_64 0:3.9.0-14.el7_5.6  
===================********===============================

(3). Also not reproduced after only update libvirt version to libvirt-4.4.0-2.el7.x86_64.



2. Latest testing:
From part1, it seems that it only reproduces on the special match of kernel and libvirt.

Then tested on latest rhel7.5 and rhel7.6 for the match.

(1). RHEL7.5:
latest kernel-3.10.0-862.el7.x86_64 and libvirt-3.9.0-14.el7_5.6.x86_64. ===> Not reproduced.

(2). RHEL7.6:
latest kernel-3.10.0-915.el7.x86_64 and libvirt-4.4.0-2.el7.x86_64.   ===> Not reproduced.
Comment 7 Erik Skultety 2018-06-29 09:42:07 UTC 
(In reply to yanqzhan from comment #6)
> 1.Try to reproduce:
> (1). Can reproduce with：
> kernel-3.10.0-768.el7.x86_64
> qemu-kvm-rhev-2.10.0-21.el7_5.4.x86_64
> libvirt-3.9.0-1.el7.x86_64
> python-slip-dbus-0.4.0-4.el7.noarch
> dbus-libs-1.10.24-3.el7.x86_64
> dbus-1.10.24-3.el7.x86_64
> dbus-python-1.1.1-9.el7.x86_64
> dbus-glib-0.100-7.el7.x86_64
> selinux-policy-3.13.1-175.el7.noarch
> 
> (2). Not reproduced after only update libvirt version:
> libvirt-3.9.0-14.el7_5.6.x86_64
> ===================********===============================
> Updated:
>   libvirt.x86_64 0:3.9.0-14.el7_5.6                                         
> 
> 
> Dependency Updated:
>   libvirt-client.x86_64 0:3.9.0-14.el7_5.6                          
> libvirt-daemon.x86_64 0:3.9.0-14.el7_5.6                        
>   libvirt-daemon-config-network.x86_64 0:3.9.0-14.el7_5.6           
> libvirt-daemon-config-nwfilter.x86_64 0:3.9.0-14.el7_5.6        
>   libvirt-daemon-driver-interface.x86_64 0:3.9.0-14.el7_5.6         
> libvirt-daemon-driver-lxc.x86_64 0:3.9.0-14.el7_5.6             
>   libvirt-daemon-driver-network.x86_64 0:3.9.0-14.el7_5.6           
> libvirt-daemon-driver-nodedev.x86_64 0:3.9.0-14.el7_5.6         
>   libvirt-daemon-driver-nwfilter.x86_64 0:3.9.0-14.el7_5.6          
> libvirt-daemon-driver-qemu.x86_64 0:3.9.0-14.el7_5.6            
>   libvirt-daemon-driver-secret.x86_64 0:3.9.0-14.el7_5.6            
> libvirt-daemon-driver-storage.x86_64 0:3.9.0-14.el7_5.6         
>   libvirt-daemon-driver-storage-core.x86_64 0:3.9.0-14.el7_5.6      
> libvirt-daemon-driver-storage-disk.x86_64 0:3.9.0-14.el7_5.6    
>   libvirt-daemon-driver-storage-gluster.x86_64 0:3.9.0-14.el7_5.6   
> libvirt-daemon-driver-storage-iscsi.x86_64 0:3.9.0-14.el7_5.6   
>   libvirt-daemon-driver-storage-logical.x86_64 0:3.9.0-14.el7_5.6   
> libvirt-daemon-driver-storage-mpath.x86_64 0:3.9.0-14.el7_5.6   
>   libvirt-daemon-driver-storage-rbd.x86_64 0:3.9.0-14.el7_5.6       
> libvirt-daemon-driver-storage-scsi.x86_64 0:3.9.0-14.el7_5.6    
>   libvirt-libs.x86_64 0:3.9.0-14.el7_5.6  
> ===================********===============================
> 
> (3). Also not reproduced after only update libvirt version to
> libvirt-4.4.0-2.el7.x86_64.
> 
> 
> 
> 2. Latest testing:
> From part1, it seems that it only reproduces on the special match of kernel
> and libvirt.

Thanks for investigating this, the reason I asked about it was that libvirt 4-ish got a fix for a similar dbus issue, so I just wanted to make sure I can link the commit here and move the BZ to post.
Comment 8 Erik Skultety 2018-06-29 09:47:23 UTC 
Fixed upstream by:
commit f94e5b215720c91c60219f1694783a603f0b619c
Refs: v4.3.0-rc1-1-gf94e5b2157
Author:     Martin Kletzander <mkletzan>
AuthorDate: Thu Apr 26 12:17:03 2018 +0200
Commit:     Martin Kletzander <mkletzan>
CommitDate: Thu Apr 26 17:40:57 2018 +0200

    logging: Don't inhibit shutdown in system daemon

    That is a job of libvirtd and virtlogd has a dependency on it, so that will
    prevent it properly.  Doing it one extra time in virtlogd might also cause AVC
    denials because it is not allowed to call that dbus method.

    Caused by commit df34363d58bb.

    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1547250

    Signed-off-by: Martin Kletzander <mkletzan>
    Reviewed-by: Daniel P. Berrangé <berrange>

*** This bug has been marked as a duplicate of bug 1547250 ***
Note You need to log in before you can comment on or make changes to this bug.