Version-Release number of selected component:
cmdline: /usr/bin/python /usr/bin/vdsm-tool nwfilter
libvirt.py:102:openAuth:libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
Traceback (most recent call last):
File "/usr/bin/vdsm-tool", line 143, in <module>
File "/usr/bin/vdsm-tool", line 140, in main
File "/usr/lib/python2.7/site-packages/vdsm/tool/nwfilter.py", line 35, in main
conn = libvirtconnection.get(None, False)
File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 132, in get
conn = utils.retry(libvirtOpenAuth, timeout=10, sleep=0.2)
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 903, in retry
File "/usr/lib/python2.7/site-packages/libvirt.py", line 102, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
Local variables in innermost frame:
auth: [[2, 5], <function req at 0xb707c1b4>, None]
Potential duplicate: bug 957335
Created attachment 850481 [details]
Created attachment 850482 [details]
a bit of details might help here. what is the scenario? just run /usr/bin/python /usr/bin/vdsm-tool nwfilter and it happens? is libvirt service up when you run the command?
(In reply to Yaniv Bronhaim from comment #3)
> a bit of details might help here. what is the scenario? just run
> /usr/bin/python /usr/bin/vdsm-tool nwfilter and it happens? is libvirt
> service up when you run the command?
Yes, libvirt was running. Sorry to say that I can't help much now since I have a reinstalled a different setup on that system now.
I need more information to understand this issue. what exactly did you do, how reproducible is that, what was the status on the host, with what versions did you work? can you try to gather this information and fill the bug report with it? logs also can help (libvirt.log and vdsms).
the description just says that you tried to run "vdsm-tool nwfilter" command while libvirtd service was stopped (the uds socket was not exist in /var/run/libvirt/)
except that I can't see anything wrong or what can lead to that
Failed to connect socket to '/var/run/libvirt/libvirt-sock'
means that libvirtd service was not running when vdsmd has started. This might be yet another issue with `vdsm-tool libvirt-configure`.
Are there any vdsm or libvirt hints in journalctl?
I understand that the description is what provided by ABRT service. The reporter can't reproduce it and doesn't know more than what described by him above.
I suspect libvirt service was down, or something was corrupted in libvirtd.conf during the vdsm-tool command that ran (nwfilter) which tries to communicate with libvirt socket.
It might be related to some last changes or might be fixed in latest 3.3.
Without further information I'm currently closing this bug as INSUFFICIENT_DATA. if the issue occurs again please reopen asap.