With Juju in the loop, I run into whatever limit a bit faster. I was successful at doing:
juju bootstrap test-lxd lxd juju deploy ubuntu juju add-unit -n 5 ubuntu # wait for status to say everything is running juju add-unit -n 5 ubuntu # wait for status to be happy but then after doing one more juju add-unit -n 5 ubuntu Firefox crashed shortly thereafter, and so did the Juju Controller, 'juju status' stopped responding. 'lxc list' shows that containers 0-10, 12 and 13 are running, but 11,14,15 are stopped. lsof | wc -l reports 84854 file handles open, but that's still lower than cat /proc/sys/fs/file-max 1635148 Kernel memory is currently at 1409M I get some random errors like "unable to acquire lock, no space left on device" even though /dev/sda1 has 10GB free. This is all under a Trusty HWE kernel (4.4.0-38), though the images are Xenial ones that we are running. It appears that Mongo was killed when things started to go south and systemd decided that it would stop trying to restart 'juju-db' With the error message "Start request repeated too quickly". It didn't try again for at least 10 minutes before I went in and started it manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
