Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1301391

Summary:	Failed to acquire pid file '/run/user/1000/libvirt/libvirtd.pid': Resource temporarily unavailable
Product:	[Community] Virtualization Tools	Reporter:	David Caro <dcaroest>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	eedri, jtomko, rbalakri
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-28 12:22:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1287260

Description David Caro 2016-01-24 18:21:31 UTC

Description of problem:
On fc23 when connecting to libvirt (qemu:///session) as regular user it sometimes fails with the above message being shown in the logs.

The error is this:

Jan 24 18:47:32 akhos libvirtd[24143]: libvirt version: 1.2.18.2, package: 1.fc23 (Fedora Project, 2015-12-24-00:55:42, buildhw-12.phx2.fedoraproject.org)
Jan 24 18:47:32 akhos libvirtd[24143]: Failed to acquire pid file '/run/user/1000/libvirt/libvirtd.pid': Resource temporarily unavailable
Jan 24 18:47:32 akhos systemd[1]: Received SIGCHLD from PID 24143 (libvirtd).
Jan 24 18:47:32 akhos systemd[1]: Child 24143 (libvirtd) died (code=exited, status=1/FAILURE)

An example of failure:
dcaro@akhos$ virsh list
error: failed to connect to the hypervisor
error: no valid connection
error: Cannot write data: Transport endpoint is not connected

This happens when that pid file does not exist, but it's created a couple seconds after, and once it's there, the virsh command start working. Though after a minute or so it disappears again and it starts failing again.


Version-Release number of selected component (if applicable):
Jan 24 18:47:32 akhos libvirtd[24143]: libvirt version: 1.2.18.2, package: 1.fc23 (Fedora Project, 2015-12-24-00:55:42, buildhw-12.phx2.fedoraproject.org)


It seems that restarting the libvirtd daemon solves nothing

Thanks!

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 David Caro 2016-01-27 19:08:47 UTC

Might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1285368

Comment 2 Ján Tomko 2016-01-28 12:22:35 UTC


*** This bug has been marked as a duplicate of bug 1271183 ***