[libvirt-users] error : virPidFileAcquirePath:345 : Failed to acquire pid file '/home/corey/.libvirt/libvirtd.pid': Resource temporarily unavailable
Michal Privoznik
mprivozn at redhat.com
Wed Oct 31 07:35:09 UTC 2012
On 31.10.2012 02:41, 何鑫 wrote:
> Hi all,
> When I try to start libvirtd, using "libvirtd -d", error
> notification shown below:
> error : virPidFileAcquirePath:345 : Failed to acquire pid file
> '/$HOME/.libvirt/libvirtd.pid': Resource temporarily unavailable
> Using "libvirtd -v", show:
> "libvirtd: error: Unable to obtain pidfile. Check /var/log/messages
> or run without --daemon for more info."
> The file "libvirtd.pid" only contains "2010" without any other
> infomation.
That means either there already is another libvirtd running or the
previous one died unexpectedly without removing this PID file. You can
distinguish these two via 'pgrep libvirtd' which either gives you the
very same PID as the one in the PID file (=libvirtd is running) or
nothing and than you should be safe to remove the file and start
libvirtd again. However, if libvirtd keeps failing to initialize, there
might be a misconfiguration problem (and libvirt bug as well since we
ought to remove PID file before quiting).
Michal
More information about the libvirt-users
mailing list