Hi,
I cannot reproduce this on xenial with
ii libvirt-bin 1.3.1-1ubuntu10 amd64
programs for the libvirt library
Could you show the result of 'journalctl -u libvirt-bin' ?
On Thu, May 19, 2016 at 4:26 PM, David Shaughnessy
<[email protected]> wrote:
> Public bug reported:
>
> When restarting the libvirt-bin service the unix socket is not created.
> A work around is to stop then start the service rather than restart.
>
> Description: Ubuntu 16.04 LTS
> Release: 16.04
>
> libvirt-bin:
> Installed: 1.3.1-1ubuntu10
> Candidate: 1.3.1-1ubuntu10
> Version table:
> *** 1.3.1-1ubuntu10 500
> 500 http://ie.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
> 100 /var/lib/dpkg/status
>
> What I expect:
> 1. $ ls /var/run/libvirt/libvirt-sock
> /var/run/libvirt/libvirt-sock
>
> 2. $ sudo service libvirt-bin restart
>
> 3. $ ls /var/run/libvirt/libvirt-sock
> /var/run/libvirt/libvirt-sock
>
>
> What happened instead:
> 1. $ ls /var/run/libvirt/libvirt-sock
> /var/run/libvirt/libvirt-sock
>
> 2. $ sudo service libvirt-bin restart
>
> 3. $ ls /var/run/libvirt/libvirt-sock
> ls: cannot access '/var/run/libvirt/libvirt-sock': No such file or directory
>
> ** Affects: libvirt (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Ubuntu
> Xen Team, which is subscribed to libvirt in Ubuntu.
> https://bugs.launchpad.net/bugs/1583688
>
> Title:
> libvirt-sock not recreated on service restart
>
> Status in libvirt package in Ubuntu:
> New
>
> Bug description:
> When restarting the libvirt-bin service the unix socket is not created.
> A work around is to stop then start the service rather than restart.
>
> Description: Ubuntu 16.04 LTS
> Release: 16.04
>
> libvirt-bin:
> Installed: 1.3.1-1ubuntu10
> Candidate: 1.3.1-1ubuntu10
> Version table:
> *** 1.3.1-1ubuntu10 500
> 500 http://ie.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
> 100 /var/lib/dpkg/status
>
> What I expect:
> 1. $ ls /var/run/libvirt/libvirt-sock
> /var/run/libvirt/libvirt-sock
>
> 2. $ sudo service libvirt-bin restart
>
> 3. $ ls /var/run/libvirt/libvirt-sock
> /var/run/libvirt/libvirt-sock
>
>
> What happened instead:
> 1. $ ls /var/run/libvirt/libvirt-sock
> /var/run/libvirt/libvirt-sock
>
> 2. $ sudo service libvirt-bin restart
>
> 3. $ ls /var/run/libvirt/libvirt-sock
> ls: cannot access '/var/run/libvirt/libvirt-sock': No such file or directory
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583688/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583688
Title:
libvirt-sock not recreated on service restart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583688/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
