Re: [lxc-users] How to recover from ERROR state

2019-01-14 Thread Kees Bakker
On 11-09-18 15:13, Kees Bakker wrote: > Hey, > > Every now and then we have one or more containers in state ERROR. > Is there a clever method to recover from that, other than > rebooting the LXD server? > > Killing the monitor and the forkstart does help. And also a kworker > process

Re: [lxc-users] How to recover from ERROR state

2018-09-24 Thread Christian Brauner
On Mon, Sep 24, 2018 at 02:11:38PM +0200, Christian Brauner wrote: > On Mon, Sep 24, 2018, 14:03 Kees Bakker wrote: > > > Same question again: what is the best approach to recover > > from a container in an ERROR state? So another thing I would like to see is the current stack of the hung

Re: [lxc-users] How to recover from ERROR state

2018-09-24 Thread Christian Brauner
On Mon, Sep 24, 2018, 14:03 Kees Bakker wrote: > Same question again: what is the best approach to recover > from a container in an ERROR state? > Please show me the dmesg output. If it is a kernel bug you're hitting there's nothing that LXD can do to help you. > This time it happened with

Re: [lxc-users] How to recover from ERROR state

2018-09-24 Thread Kees Bakker
Same question again: what is the best approach to recover from a container in an ERROR state? This time it happened with Ubuntu 18.04 and LVM storage. The steps leading to this were as follows. It's just an FYI, I don't think it really matters, except for the stop and start.   lvextend -L 20G

Re: [lxc-users] How to recover from ERROR state

2018-09-12 Thread Fajar A. Nugraha
On Wed, Sep 12, 2018 at 4:08 PM, Kees Bakker wrote: > On 12-09-18 10:51, Fajar A. Nugraha wrote: > > On Wed, Sep 12, 2018 at 3:14 PM, Kees Bakker wrote: > >> On 11-09-18 21:56, Andrey Repin wrote: >> > Greetings, Kees Bakker! >> > >> >> ii lxc-common 2.0.8-0ubuntu1~16.04.2 amd64

Re: [lxc-users] How to recover from ERROR state

2018-09-12 Thread Kees Bakker
On 12-09-18 10:51, Fajar A. Nugraha wrote: > On Wed, Sep 12, 2018 at 3:14 PM, Kees Bakker > wrote: > > On 11-09-18 21:56, Andrey Repin wrote: > > Greetings, Kees Bakker! > > > >> ii  lxc-common 2.0.8-0ubuntu1~16.04.2  amd64    Linux > Containers

Re: [lxc-users] How to recover from ERROR state

2018-09-12 Thread Fajar A. Nugraha
On Wed, Sep 12, 2018 at 3:14 PM, Kees Bakker wrote: > On 11-09-18 21:56, Andrey Repin wrote: > > Greetings, Kees Bakker! > > > >> ii lxc-common 2.0.8-0ubuntu1~16.04.2 amd64Linux > Containers userspace tools (common tools) > >> ii lxcfs 2.0.8-0ubuntu1~16.04.2 amd64

Re: [lxc-users] How to recover from ERROR state

2018-09-12 Thread Kees Bakker
On 11-09-18 21:56, Andrey Repin wrote: > Greetings, Kees Bakker! > >> ii  lxc-common 2.0.8-0ubuntu1~16.04.2  amd64    Linux Containers >> userspace tools (common tools) >> ii  lxcfs  2.0.8-0ubuntu1~16.04.2  amd64    FUSE based >> filesystem for LXC >> ii  lxd   

Re: [lxc-users] How to recover from ERROR state

2018-09-11 Thread Andrey Repin
Greetings, Kees Bakker! > ii  lxc-common 2.0.8-0ubuntu1~16.04.2  amd64    Linux Containers > userspace tools (common tools) > ii  lxcfs  2.0.8-0ubuntu1~16.04.2  amd64    FUSE based filesystem > for LXC > ii  lxd    2.0.11-0ubuntu1~16.04.4 amd64    Container

Re: [lxc-users] How to recover from ERROR state

2018-09-11 Thread Kees Bakker
On 11-09-18 16:11, Christian Brauner wrote: >> Kees Bakker hat am 11. September 2018 um 15:54 geschrieben: >> >> >> On 11-09-18 15:40, Christian Brauner wrote: Kees Bakker hat am 11. September 2018 um 15:13 geschrieben: Hey, Every now and then we have one or more

Re: [lxc-users] How to recover from ERROR state

2018-09-11 Thread Kees Bakker
On 11-09-18 15:40, Christian Brauner wrote: >> Kees Bakker hat am 11. September 2018 um 15:13 geschrieben: >> >> >> Hey, >> >> Every now and then we have one or more containers in state ERROR. >> Is there a clever method to recover from that, other than >> rebooting the LXD server? >> >> Killing

Re: [lxc-users] How to recover from ERROR state

2018-09-11 Thread Christian Brauner
> Kees Bakker hat am 11. September 2018 um 15:13 geschrieben: > > > Hey, > > Every now and then we have one or more containers in state ERROR. > Is there a clever method to recover from that, other than > rebooting the LXD server? > > Killing the monitor and the forkstart does help. And also