Re: [opensuse-factory] WARNING - Tumbleweed snapshot 20160605 - POSSIBLE FIX
On Wed, 2016-06-08 at 10:34 +0200, René Krell wrote:
* user.slice not being used - hence the user is limited to system.scope and that's 512 children (not sufficient for a normal session, resulting in forking issues)
So that's this weird problem with running out of threads while using Chromium, IntelliJ and bash happening already several months...
I worked around by increasing the limit in /etc/systemd/system.conf: DefaultTasksMax=2048
It's just that - a workaround, which might hide other things (you lack logind integration). I suggest to either 'force re-install systemd' (zypper in -f systemd) which will get the config pack in place or the pam-config call mentioned earlier... and revert the workaround. This would ensure your entire logind integration is back in place Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
2016-06-08 10:41 GMT+02:00 Dominique Leuenberger / DimStar
On Wed, 2016-06-08 at 10:34 +0200, René Krell wrote:
* user.slice not being used - hence the user is limited to system.scope and that's 512 children (not sufficient for a normal session, resulting in forking issues)
So that's this weird problem with running out of threads while using Chromium, IntelliJ and bash happening already several months...
I worked around by increasing the limit in /etc/systemd/system.conf: DefaultTasksMax=2048
It's just that - a workaround, which might hide other things (you lack logind integration).
I suggest to either 'force re-install systemd' (zypper in -f systemd) which will get the config pack in place or the pam-config call mentioned earlier... and revert the workaround.
This would ensure your entire logind integration is back in place
Dominique
OK, I did all of them: - Clean up /etc/pam.d to get clean files installed - Restored /etc/systemd/system.conf like originally installed - zypper in -f systemd - zypper in -f pam-config - rpm -q --verify systemd pam-config - pam-config --add --systemd This worked and my TW 20160605 system is up and running fine (also Chromium with dozens of open tabs doesn't run out of fork limits). Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, June 8, 2016 10:41:55 AM WIB Dominique Leuenberger / DimStar wrote:
On Wed, 2016-06-08 at 10:34 +0200, René Krell wrote:
* user.slice not being used - hence the user is limited to system.scope and that's 512 children (not sufficient for a normal session, resulting in forking issues)
So that's this weird problem with running out of threads while using Chromium, IntelliJ and bash happening already several months...
I worked around by increasing the limit in /etc/systemd/system.conf: DefaultTasksMax=2048
It's just that - a workaround, which might hide other things (you lack logind integration).
I suggest to either 'force re-install systemd' (zypper in -f systemd) which will get the config pack in place or the pam-config call mentioned earlier... and revert the workaround.
This would ensure your entire logind integration is back in place
Thanks Dominique, Followed your suggestion and as far as I could see everyhing worked as expected. Sound has come back, kmail behaves as before and the connection to the internet is back. Constant -- Linux User 183145 using Tumbleweed on a Pentium IV System : Linux 4.6.0-1-default Distro : openSUSE 20160605 (x86_64) Desktop: KDE Frameworks: 5.22.0 and Plasma 5.6.4 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
C. Brouerius van Nidek -
Dominique Leuenberger / DimStar -
René Krell