2014-03-29 22:39:33 UTC
when running multiple lxc actions in row using the command line tools, I
sometimes observe the following state:
- lxc-monitord is not running anymore
- /run/lxc/var/lib/lxc/monitor-fifo still exists, but is "refusing
In the logs, I then see the following:
lxc-start 1395671045.703 ERROR lxc_monitor - connect : backing off 10
lxc-start 1395671045.713 ERROR lxc_monitor - connect : backing off 50
lxc-start 1395671045.763 ERROR lxc_monitor - connect : backing off 100
lxc-start 1395671045.864 ERROR lxc_monitor - connect : Connection refused
... and the command fails.
A possible workaround would be checking for non-running lxc-monitord
process but existing monitor-fifo file then removing the fifo if it
exists before running the next lxc command, but thats ugly ;-)
Is this behaviour known? Is there some missing "cleanup code" in
lxc(_monitord) or why is it failing like this?