We have been running with a custom build of the package, that adds __thread to the relevant variables as suggested in that bug, and haven't seen any crashes in this module since.
> On 13 Dec 2016, at 16:30, ChristianEhrhardt <email address hidden> wrote:
>
> Given the pre-analysis I agree with Maik, reassigning to libnss-
> extrausers
>
> ** Package changed: libvirt (Ubuntu) => libnss-extrausers (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1602264
>
> Title:
> libvirtd crashes with double free or corruption (out)
>
> Status in libnss-extrausers package in Ubuntu:
> New
>
> Bug description:
> I saw libvirtd crash with the attached error when someone tried to
> start a VM via openstack nova.
>
> Anyone with hints howto debug this further?
>
> Thanks,
> Tom
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libnss-extrausers/+bug/1602264/+subscriptions
Note that this is https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 831390.
We have been running with a custom build of the package, that adds __thread to the relevant variables as suggested in that bug, and haven't seen any crashes in this module since.
> On 13 Dec 2016, at 16:30, ChristianEhrhardt <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1602264 /bugs.launchpad .net/ubuntu/ +source/ libnss- extrausers/ +bug/1602264/ +subscriptions
>
> Given the pre-analysis I agree with Maik, reassigning to libnss-
> extrausers
>
> ** Package changed: libvirt (Ubuntu) => libnss-extrausers (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> libvirtd crashes with double free or corruption (out)
>
> Status in libnss-extrausers package in Ubuntu:
> New
>
> Bug description:
> I saw libvirtd crash with the attached error when someone tried to
> start a VM via openstack nova.
>
> Anyone with hints howto debug this further?
>
> Thanks,
> Tom
>
> To manage notifications about this bug go to:
> https:/