This bug was fixed in the package systemd - 239-7ubuntu15
---------------
systemd (239-7ubuntu15) disco; urgency=medium
* core: set /run size to 10%, like initramfs-tools does.
Currently there is a difference between initrd and initrd-less boots,
w.r.t. size= mount option of /run. This yields different runtime journald
caps
(1% vs 10%), and on dense deployments of containers may result in OOM kills.
(LP: #1799251)
File:
debian/patches/debian/UBUNTU-core-set-run-size-to-10-like-initramfs-tools-does.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1fac2568fe716dc1a41bada78293dc6327a6df0d
* resolved: Increase size of TCP stub replies.
DNS_PACKET_PAYLOAD_SIZE_MAX is limiting the size of the stub replies to
512 with EDNS off or 4096 with EDNS on, without checking the protocol
used. This makes TCP replies for clients without EDNS support to be
limited to 512, making the truncate flag useless if the query result is
bigger than 512 bytes.
This commit increases the size of TCP replies to DNS_PACKET_SIZE_MAX
Fixes: #10816
(cherry picked from commit e6eed9445956cfa496e1db933bfd3530db23bfce)
(LP: #1804487)
Author: Victor Tapia
File: debian/patches/resolved-Increase-size-of-TCP-stub-replies.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=702a4566174c4d2bd84b70805107cfc1a7c128cc
-- Dimitri John Ledkov <x...@ubuntu.com> Mon, 03 Dec 2018 13:49:24
+0000
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1799251
Title:
mount options for /run should be the same as initramfs tools
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
New
Status in systemd source package in Bionic:
New
Status in systemd source package in Cosmic:
Fix Committed
Bug description:
mount options for /run should be the same as initramfs tools
[Impact]
* /run is mounted with different options on initrd boots, and initrd-
less boots. For consistency it should be the same
* In particular, this causes overuse of RAM on hosts with dense
deployment of containers. Specifically, runtime journald takes up at
most 10% or /run, which is capped at 10% of ram, thus 1% of total RAM.
However, on initrd-less boots (like lxd launch ubuntu-daily:foo), /run
takes up all of RAM, and thus run-time journal is now capped at 10% of
RAM. Which is really bad when one deploys more than 10 containers...
[Test Case]
* Check total RAM on the host with `free -h`
* lxd launch ubuntu-daily:release
* In that container check the size of /run with `df -h | grep '/run$'`
* /run should roughly be 1/10th of the total RAM.
[Regression Potential]
* /run is meant to be small, and it is small on systems booted with
initrd and everything works fine there. Reducing the default size of
/run in the containers should not have averse impacts. The most
notable change is that runtime journald is now capped 10x smaller in
the containers, to the same size as on the hosts. If that is not
enough, one should $ sudo mkdir /var/log/journal to have a larger
persistent journal.
[Other Info]
* This issue got escalated as affecting production deployments in the
Canonical datacentre.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799251/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
