Comment 13 for bug 2022982

Thanks for those.

So to summarise so far:

1. After a while container loses its IP.
2. `lxc restart` doesn't work because container's init system is not responding (or not finishing) the shutdown request that LXD sends.
3. `lxc exec` still works?
4. `lxc restart -f` works - showing that LXD itself is still functioning correctly and can control the container from outside.

Looking at your ps output, does it strike you as odd that there are many many `/usr/sbin/CRON -f -P` processes running inside that problem `juju-acf4dc-1` container?

The next time it happens, if `lxc exec` is working, please can you run `lxc exec <instance> -- ps auxf` so we can see things from the container's perspective.

Also, it should be good to get the output of `lxc exec <instance> -- systemctl` to see what is the state of the systemd units.

Finally, it would be good to see the output of the last few hundred lines of the container's journalctl entries, so something like:

```
lxc exec <instance> -- journalctl -b -r -n 200
```