On Fri, Mar 10, 2017 at 03:01:02AM +0900, Tomasz Chmielewski wrote:
> On 2017-03-10 01:52, Stéphane Graber wrote:
>
> > Do you see a flood of events if you run "lxc monitor --type=logging"?
>
> Nope, just this:
>
> # lxc monitor --type=logging
> metadata:
> context: {}
> level: dbug
> message: 'New events listener: 9e429089-289b-4ab8-9965-069054e7371c'
> timestamp: 2017-03-09T18:57:56.311175444+01:00
> type: loggingHmm, then it matches another such report I've seen where some of the threads are reported as using a lot of CPU, yet when trying to trace them you don't actually see anything. Can you try to run "strace -p" on the various threads that are reported as eating all your CPU? The similar report I got of this would just show them stuck on a futex, which wouldn't explain the CPU use. And unfortunately it looked like tracing the threads actually somehow fixed the CPU problem for that user... If you just want the problem gone, "systemctl restart lxd" should fix things without interrupting your containers, but we'd definitely like to figure this one out if we can. -- Stéphane Graber Ubuntu developer http://www.ubuntu.com
signature.asc
Description: PGP signature
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
