FS#48399 - [libvirt] failed to connect to monitor socket: No such process

Attached to Project: Community Packages
Opened by nerdix (nerdix) - Wednesday, 02 March 2016, 10:12 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 10 March 2016, 17:36 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 19
Private No

Details

Description: libvirt/kvm guests does not start up anymore after upgradeing to libvirt-1.3.2-1-x86_64


Additional info:
* libvirt-1.3.2-1-x86_64


Steps to reproduce:

- Upgrade libvirt from 1.3.1-2-x86_64 to 1.3.2-1-x86_64, reboot system or run systemctl daemon-reload && systemctl restart libvirt
- try to start up any libvirt managed kvm guest
- check with systemctl status libvirtd


Downgrading back to libvirt-1.3.1-2-x86_64 fixes the issue.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 10 March 2016, 17:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  service type changed from notify to simple
Comment by nerdix (nerdix) - Wednesday, 02 March 2016, 10:29 GMT
Here is an excerpt from the log:


libvirtd[755]: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked th$
virtlogd[1960]: libvirt version: 1.3.2
kernel: traps: libvirtd[817] general protection ip:7f4bc48674b0 sp:7f4bbb1508e8 error:0 in libvirt.so.0.1003.2[7f4bc47bc000+361000]
virtlogd[1960]: hostname: arch64
virtlogd[1960]: End of file while reading data: Input/output error


libvirtd[2030]: failed to connect to monitor socket: No such process
virtlogd[1960]: End of file while reading data: Input/output error

libvirtd[2573]: internal error: End of file from monitor
virtlogd[1960]: End of file while reading data: Input/output error
Comment by nerdix (nerdix) - Wednesday, 02 March 2016, 15:23 GMT
Here is the thread where other Arch users experienced the same issue after upgrading to libvirt-1.3.2-1

https://bbs.archlinux.org/viewtopic.php?id=209588
Comment by nerdix (nerdix) - Thursday, 03 March 2016, 08:33 GMT

I confirm the following workaround is working for libvirt-1.3.2-1-x86_64 (Thanks to: ihad for posting this solution):

* copy /usr/lib/systemd/system/libvirtd.service to /etc/systemd/system and comment out the line Type=notify in the copy
* reload: systemctl daemon-reload
* start libvirtd: systemctl start libvirtd
Comment by deusstultus (deusstultus) - Friday, 04 March 2016, 23:11 GMT
Underlying issue identified in  FS#48440 
Sockets are not opened appropriately because it hangs in service installation which lead to the observed issues.

Loading...