The systemd mechanism here was proposed in November 2015.
Lennart Poettering acknowledged that it &quot;had the potential to break some daemons&quot;.<p>* <a href="https:&#x2F;&#x2F;lists.freedesktop.org&#x2F;archives&#x2F;systemd-devel&#x2F;2015-November&#x2F;035006.html" rel="nofollow">https:&#x2F;&#x2F;lists.freedesktop.org&#x2F;archives&#x2F;systemd-devel&#x2F;2015-No...</a><p>In conversation with Lennart Poettering, systemd developer Zbigniew Jędrzejewski-Szmek&#x27;s position was to turn the mechanism on and gather statistics about who and what it broke.
Lennart Poettering did this about 20 hours later.
Within a week, this was in the released version of systemd.<p>* <a href="https:&#x2F;&#x2F;lists.freedesktop.org&#x2F;archives&#x2F;systemd-devel&#x2F;2015-November&#x2F;035011.html" rel="nofollow">https:&#x2F;&#x2F;lists.freedesktop.org&#x2F;archives&#x2F;systemd-devel&#x2F;2015-No...</a><p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;commit&#x2F;0af20ea2ee2af2bcf2258e7a8e1a13181a6a75d6" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;commit&#x2F;0af20ea2ee2af2bcf2...</a><p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;commit&#x2F;9ded9cd14cc03c67291b10a5c42ce5094ba0912f" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;commit&#x2F;9ded9cd14cc03c6729...</a><p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;blob&#x2F;ccddd104fc95e0e769142af6e1fe1edec5be70a6&#x2F;NEWS#L373-393" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;blob&#x2F;ccddd104fc95e0e76914...</a><p>Their position has been since that the correct thing to do if one hits this is <i>not</i> to revert Lennart Poettering&#x27;s change to the DefaultTasksMax and DefaulTasksAccounting settings, but to tweak the service unit files of any and all affected daemons.<p>The systemd bug report paints this as an Ubuntu problem, in part because the systemd developer who submitted it is also the Ubuntu maintainer for systemd, but there are actually quite a lot of bug reports <i>across several distributions</i> that relate to this.
Several people have simply placed TasksMax=infinity in their service unit files; but a few have indeed reverted the DefaultTasksMax setting, as the Ubuntu maintainer also asked for.<p>The maximum applies to kernel &quot;tasks&quot;, not to processes.
So whilst one can hit it by forking a lot of processes, one can also hit it with only a few processes that happen to use a lot of threads per process.
This is of particular concern to MySQL, MariaDB, Percona, and their ilk, which use a thread per client connection.
As Brad Mashall discovered, the effect is that the SQL servers start refusing client connections.<p>* <a href="https:&#x2F;&#x2F;bugs.launchpad.net&#x2F;charms&#x2F;+source&#x2F;percona-cluster&#x2F;+bug&#x2F;1578080" rel="nofollow">https:&#x2F;&#x2F;bugs.launchpad.net&#x2F;charms&#x2F;+source&#x2F;percona-cluster&#x2F;+b...</a><p>Someone hit this with a multi-threaded Java program and reported it to Arch.<p>* <a href="https:&#x2F;&#x2F;bugs.archlinux.org&#x2F;task&#x2F;47787" rel="nofollow">https:&#x2F;&#x2F;bugs.archlinux.org&#x2F;task&#x2F;47787</a><p>The issue was clouded by two things:
First, it was obscured by <i>another</i> systemd issue that imposes a task limit on every user service spawned by a user&#x27;s per-user instance of systemd.
Second, it was obscured by the complication that GNOME Terminal does not spawn terminal instances directly but rather uses Desktop Bus to spawn them remotely via &quot;DBUS activation&quot;, resulting in terminals and the processes in their associated login sessions having the <i>non</i>-login-session task maxima applied.<p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;1955" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;1955</a><p>Others have reproduced this with lots of processes.
Dominique Leuenberger reported to OpenSUSE that this affects a lot of xyr builds because of parallel make.
Gustavo Romero created a short makefile to use with parallel make (make -j500) that exhibited the problem.<p>* <a href="https:&#x2F;&#x2F;bugzilla.opensuse.org&#x2F;show_bug.cgi?id=965564" rel="nofollow">https:&#x2F;&#x2F;bugzilla.opensuse.org&#x2F;show_bug.cgi?id=965564</a><p>* <a href="https:&#x2F;&#x2F;bugs.launchpad.net&#x2F;ubuntu&#x2F;+source&#x2F;ubuntu-meta&#x2F;+bug&#x2F;1561658&#x2F;comments&#x2F;1" rel="nofollow">https:&#x2F;&#x2F;bugs.launchpad.net&#x2F;ubuntu&#x2F;+source&#x2F;ubuntu-meta&#x2F;+bug&#x2F;1...</a><p>Marko Mihovilic reported to Arch a similar problem on build machines.<p>* <a href="https:&#x2F;&#x2F;bugs.archlinux.org&#x2F;task&#x2F;47662#comment142757" rel="nofollow">https:&#x2F;&#x2F;bugs.archlinux.org&#x2F;task&#x2F;47662#comment142757</a><p>Jakub Sztandera reported to Arch that LXC encounters this limit.
Other people observed there that it has affected Java services such as Freenet.
Lennart Poettering reiterated that people should not revert his changes but instead change their individual TasksMax settings.<p>* <a href="https:&#x2F;&#x2F;bugs.archlinux.org&#x2F;task&#x2F;47303" rel="nofollow">https:&#x2F;&#x2F;bugs.archlinux.org&#x2F;task&#x2F;47303</a><p>* <a href="https:&#x2F;&#x2F;bbs.archlinux.org&#x2F;viewtopic.php?id=207255" rel="nofollow">https:&#x2F;&#x2F;bbs.archlinux.org&#x2F;viewtopic.php?id=207255</a><p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;2388" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;2388</a><p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;2388#issuecomment-173320246" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;systemd&#x2F;systemd&#x2F;issues&#x2F;2388#issuecomment-...</a><p>It affected Docker, and this was reported to RedHat.
The Docker people then noticed that all of the people who had CentOS 7, Debian 8, and the like were seeing a message about an unknown systemd service unit directive.
Others (including Nathan Cutler, who reported the systemd problem to Ceph) had seen this, and after discussion considered it cosmetic, as it did not in fact prevent services from running on older versions of systemd.
The Docker people, however, promptly reverted their fix.
The Docker position is now that &quot;people on newer kernels&quot; have to maintain their own specially tweaked versions of systemd service unit files.<p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;9868" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;9868</a><p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;pull&#x2F;19391" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;pull&#x2F;19391</a><p>* <a href="https:&#x2F;&#x2F;bugzilla.redhat.com&#x2F;show_bug.cgi?id=1311750" rel="nofollow">https:&#x2F;&#x2F;bugzilla.redhat.com&#x2F;show_bug.cgi?id=1311750</a><p>* <a href="http:&#x2F;&#x2F;tracker.ceph.com&#x2F;issues&#x2F;15583" rel="nofollow">http:&#x2F;&#x2F;tracker.ceph.com&#x2F;issues&#x2F;15583</a><p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;20036" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker&#x2F;issues&#x2F;20036</a><p>It hit Azk, too.<p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;azukiapp&#x2F;azk&#x2F;issues&#x2F;634" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;azukiapp&#x2F;azk&#x2F;issues&#x2F;634</a><p>Sebastian Schmidt hit this with Chrome, where the entire session spawned by xdm was limited to 512 threads in total, and reported it to Debian.<p>* <a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=602002" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=602002</a><p>* <a href="https:&#x2F;&#x2F;bugs.debian.org&#x2F;cgi-bin&#x2F;bugreport.cgi?bug=823530" rel="nofollow">https:&#x2F;&#x2F;bugs.debian.org&#x2F;cgi-bin&#x2F;bugreport.cgi?bug=823530</a><p>Breno Leitão hit this on Ubuntu, with the SSH server under one set of control groups on one system and under a different set on another, the result of a dependency chain involving PAM and PolicyKit.<p>* <a href="https:&#x2F;&#x2F;bugs.launchpad.net&#x2F;ubuntu&#x2F;+source&#x2F;ubuntu-meta&#x2F;+bug&#x2F;1561658" rel="nofollow">https:&#x2F;&#x2F;bugs.launchpad.net&#x2F;ubuntu&#x2F;+source&#x2F;ubuntu-meta&#x2F;+bug&#x2F;1...</a>