[lxc-users] lxd process 100% CPU

[Paweł A. Gajda]

On Tue, Feb 14, 2017 at 2:56 PM, Stéphane Graber <stgraber at ubuntu.com>
wrote:

> On Tue, Feb 14, 2017 at 01:43:20PM +0100, Paweł A. Gajda wrote:
> > On Sat, Jan 28, 2017 at 4:35 PM, David Favor <david at davidfavor.com>
> wrote:
> >
> > > Colin Holywell wrote:
> > >
> > > I recently upgraded the lxd installation on my Ubuntu 16.04 system. I
> used
> > > the lxd-stable repo to update the packages Ubuntu provides (version
> 2.0 I
> > > think?) to version 2.7. Everything upgraded fine but now once or twice
> a
> > > day the lxd process starts gobbling up a bunch of CPU time. There is
> > > nothing in the /var/log/lxd/lxd.log or syslog to indicate what it is
> doing.
> > > If I restart the lxd service or wait a couple hours it will stops and
> go
> > > back to normal.
> > >
> > > Does any one know what it is doing? Can I downgrade back to the Ubuntu
> > > supplied lxd version and not loose my containers?
> > >
> > > Try connecting to the process pid with strace + see if that surfaces
> how
> > > to fix problem.
> > >
> >
> > Same with 2.8, 100% CPU, strace does not help much:
> >
> > # strace -p 2580
> > strace: Process 2580 attached
> > futex(0xfdcdf0, FUTEX_WAIT, 0, NULL
> >
> > Any hints? 2.2 works for months now in the same environent (PLD Linux,
> > kernel 4.8) without any problem.
>
> Anything in lxd.log? If it's easily reproducible for you, then starting
> the daemon with --debug may provide some more information in the log to
> figure out what's going on.
>

Nothing alarming in lxd.log, I'll try with --debug, thanks.
Is golang version matters? I rebuild lxd with newest 1.7.5, will see.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20170214/4518e147/attachment.html>