"lxc delete containername --force" is sometimes freezing and does not
return.
ii lxd 2.20-0ubuntu4~16.04.1
amd64 Container hypervisor based on LXC - daemon
ii lxd-client 2.20-0ubuntu4~16.04.1
amd64 Container hypervisor based on LXC - client
ii liblxc1 2.1.1-0ubuntu1~ubuntu16.04.1~ppa1
amd64 Linux Containers userspace tools (library)
ii lxc-common 2.1.1-0ubuntu1~ubuntu16.04.1~ppa1
amd64 Linux Containers userspace tools (common tools)
ii lxcfs 2.0.8-1ubuntu2~ubuntu16.04.1~ppa1
amd64 FUSE based filesystem for LXC
Server is hosted on AWS and is running linux-image-4.4.0-1043-aws kernel
(Ubuntu 16.04).
Container's /var/log/lxd/containername/lxc.log comtains:
lxc 20171217104137.857 WARN lxc_monitor -
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send
message: No such file or directory.
lxc 20171217104137.857 WARN lxc_monitor -
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send
message: No such file or directory.
lxc 20171217104137.978 WARN lxc_monitor -
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send
message: No such file or directory.
lxc 20171217104137.978 WARN lxc_monitor -
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send
message: No such file or directory.
lxc 20171219063617.834 WARN lxc_monitor -
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send
message: No such file or directory.
lxc 20171221100816.533 WARN lxc_monitor -
monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send
message: No such file or directory.
Not sure how to debug this.
It kills our server deployment / automation.
Tomasz Chmielewski
https://lxadm.com
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
