Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=968128.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-05-29T03:31:10+00:00 Luwen wrote: Description of problem: After configuration qemu-lockd.conf , libvirtd will fail to restart because error Failed to connect socket to '/var/run/libvirt/virtlockd-sock': No such file or directory ,but the socket file is named virtlockd.sock and located at /var/run/libvirt/virtlockd/virtlockd.sock Version-Release number of selected component (if applicable): libvirt-1.0.5-2.el7.x86_64 qemu-kvm-1.5.0-2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. #systemctl start virtlockd.service 2. #tail -1 /etc/libvirt/qemu.conf lock_manager = "lockd" #tail -3 /etc/libvirt/qemu-lockd.conf auto_disk_leases = 1 require_lease_for_disks = 1 file_lockspace_dir = "/var/lib/libvirt/lockd/files" 3. #systemctl restart libvirtd.service libvirtd wil report error below and can't start Failed to connect socket to '/var/run/libvirt/virtlockd-sock': No such file or directory Actual results: the function doesn't work Expected results: can use Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1263162/comments/0 ------------------------------------------------------------------------ On 2013-06-04T13:28:09+00:00 Ján wrote: I proposed a patch changing the socket path in the systemd config file: https://www.redhat.com/archives/libvir-list/2013-June/msg00085.html Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1263162/comments/1 ------------------------------------------------------------------------ On 2013-06-05T11:58:43+00:00 Ján wrote: The socket path fix is now pushed upstream: commit 70fe129546545f9683ce57e6946dd80a08b54d2b Author: Ján Tomko <[email protected]> AuthorDate: 2013-06-04 13:36:56 +0200 Commit: Ján Tomko <[email protected]> CommitDate: 2013-06-05 10:17:28 +0200 virtlockd: fix socket path Change the socket path to match the one used by lockd driver. But it still fails with selinux enabled: Jun 5 07:41:51 456rhel setroubleshoot: SELinux is preventing /usr/sbin/libvirtd from connectto access on the unix_stream_socket /run/libvirt/virtl ockd-sock. For complete SELinux messages. run sealert -l 8ab78190-8e08-45f5-8d2e-02862d493dea Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1263162/comments/2 ------------------------------------------------------------------------ On 2013-07-04T03:43:18+00:00 Luwen wrote: Now , the virtlockd can start and no selinux's issue with packages selinux-policy-3.12.1-56.el7.noarch libvirt-1.1.0-1.el7.x86_64 , But when generate lease file , the virtlockd's daemon will show End of file while reading data: Input/output error , and no related file or directory created. I will file another bug for it later, and set this one Verify first. Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1263162/comments/3 ------------------------------------------------------------------------ On 2014-06-13T09:56:41+00:00 Ludek wrote: This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. Reply at: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1263162/comments/8 ** Changed in: libvirt Status: Unknown => Fix Released ** Changed in: libvirt Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263162 Title: libvirt missing sanlock plugin To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1263162/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
