[lxc-users] How to recover from ERROR state

[Kees Bakker]

On 11-09-18 16:11, Christian Brauner wrote:
>> Kees Bakker <keesb at ghs.com> hat am 11. September 2018 um 15:54 geschrieben:
>>
>>
>> On 11-09-18 15:40, Christian Brauner wrote:
>>>> Kees Bakker <keesb at ghs.com> 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 a kworker
>>>> process (kworker/u16:0) is eating up one of the CPUs with 100% load.
>>>> lxc info gives "error: Monitor is hung"
>>> If I'm not mistaken this is usually caused by a hanging lxc-monitord
>>> process which older LXC versions still use and which is removed in 
>>> newer LXC versions.
>>> Can you check whether you see a lxc-monitord process when such a hang
>>> happens. If so, kill it. Afterwards things should work fine again.
>> Killing lxc-monitord did not help.
>> I had to kill a "[lxc monitor]" process as well. Then the container
>> got back to state "STOPPED".
> But you still have a lxc-monitord process. That's usually the culprit
> for all that mess.

No, that process was killed. Didn't help.

>  If you can update liblxc and feel confident doing so
> you should do it.
>

Update liblxc to what version?
-- 
Kees Bakker