Bug 957335
Summary: | [abrt] vdsm-4.10.3-10.fc18: libvirt.py:102:openAuth:libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Iulian <iv_i170511> | ||||||||||
Component: | vdsm | Assignee: | Yaniv Bronhaim <ybronhei> | ||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 18 | CC: | dougsland, fsimonce, virt-maint | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | i686 | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | abrt_hash:a16e1da893e2e9a6913e1ca66e9868db4dc11127 infra | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2013-04-29 17:51:03 UTC | Type: | --- | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | --- | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Attachments: |
|
Description
Iulian
2013-04-27 09:55:32 UTC
Created attachment 740743 [details]
File: backtrace
Created attachment 740744 [details]
File: core_backtrace
Created attachment 740745 [details]
File: dso_list
Created attachment 740746 [details]
File: environ
I'm not sure that I understand the description correctly, Are you trying to run "python /usr/share/vdsm/nwfilter.pyc" and get this exception? This command runs each restart of vdsmd service, if it throws exception vdsm deamon does not start and we restart libvirt service that should fix this socket error (by creating new one). If this exception is raised during vdsm run and you see that in the log, Bug 852956 fixes it and you can close this bug as duplicate. *** This bug has been marked as a duplicate of bug 852956 *** |