[Touch-packages] [Bug 1578080] Re: percona cluster hits resource limits in HA Openstack cloud with xenial
Great to hear. This bug will be fixed then I guess: https://youtrack.jetbrains.com/issue/UP-6943 Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1578080 Title: percona cluster hits resource limits in HA Openstack cloud with xenial Status in percona-xtradb-cluster-5.6 package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in percona-cluster package in Juju Charms Collection: Won't Fix Status in systemd package in Debian: Fix Released Bug description: I'm trying to deploy Mitaka Openstack using the 16.04 charms on Xenial using Juju 1.25.5 and MAAS 1.9.2, with as many components of Openstack being HA as possible. When deployed, after running for a while mysql (which is a 3 node cluster) starts refusing connections, and erroring: 2016-05-03 01:25:28 13795 [ERROR] Error log throttle: 50 'Can't create thread to handle new connection' error(s) suppressed When I look at systemd-cgtop, I can see it maxing out at 512 connections. To get it going again I do a: $ sudo systemctl edit mysql and set: TasksMax=infinity Sometimes I even need to edit /etc/systemd/system.conf and bump DefaultTasksMax to 1024 or higher, depending on long its been left running. I've noticed that dropping worker-multiplier setting on nova-cloud- controller, neutron-api etc all help to reduce the load, but I still need to bump it up. Please let me know if you need any more information. SRU INFORMATION --- Impact: Introducing a default #thread limit of 512 broke an unknown set of services which regularly run many threads. Fix: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=fe4d9d3ba0 (essentially, revert the upstream commit that enabled it) Regression potential: Very low -- this just restores the pre-228 behaviour and does not impose any new restriction. Test case: - Pick some unit like cron.service or mysql.service that does not specify an explicit TaskMax= limit. - Check its TaskMax: systemctl show -p TasksMax cron.service - In current xenial this is "512", after the update it should be a very big number (maxint minus 1, which means "infinity") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1578080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578080] Re: percona cluster hits resource limits in HA Openstack cloud with xenial
Will my systemd scripts with TasksMax setting keep working? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1578080 Title: percona cluster hits resource limits in HA Openstack cloud with xenial Status in percona-xtradb-cluster-5.6 package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in percona-cluster package in Juju Charms Collection: Won't Fix Status in systemd package in Debian: Fix Released Bug description: I'm trying to deploy Mitaka Openstack using the 16.04 charms on Xenial using Juju 1.25.5 and MAAS 1.9.2, with as many components of Openstack being HA as possible. When deployed, after running for a while mysql (which is a 3 node cluster) starts refusing connections, and erroring: 2016-05-03 01:25:28 13795 [ERROR] Error log throttle: 50 'Can't create thread to handle new connection' error(s) suppressed When I look at systemd-cgtop, I can see it maxing out at 512 connections. To get it going again I do a: $ sudo systemctl edit mysql and set: TasksMax=infinity Sometimes I even need to edit /etc/systemd/system.conf and bump DefaultTasksMax to 1024 or higher, depending on long its been left running. I've noticed that dropping worker-multiplier setting on nova-cloud- controller, neutron-api etc all help to reduce the load, but I still need to bump it up. Please let me know if you need any more information. SRU INFORMATION --- Impact: Introducing a default #thread limit of 512 broke an unknown set of services which regularly run many threads. Fix: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=fe4d9d3ba0 (essentially, revert the upstream commit that enabled it) Regression potential: Very low -- this just restores the pre-228 behaviour and does not impose any new restriction. Test case: - Pick some unit like cron.service or mysql.service that does not specify an explicit TaskMax= limit. - Check its TaskMax: systemctl show -p TasksMax cron.service - In current xenial this is "512", after the update it should be a very big number (maxint minus 1, which means "infinity") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1578080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583232] Re: Wowza Streaming Engine out of memory on Ubuntu 16.04
*** This bug is a duplicate of bug 1578080 *** https://bugs.launchpad.net/bugs/1578080 Installing upstart didn't work well on Xenial, so I looked into this some more. Turns out you have to set TasksMax=infinity since a recent version of systemd, which is also mentioned in the duplicate bug link. Just set [Service] TasksMax=infinity and you're good to go. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1583232 Title: Wowza Streaming Engine out of memory on Ubuntu 16.04 Status in systemd package in Ubuntu: New Bug description: Wowza Streaming Engine using systemd runs out of memory within a few minutes on Ubuntu 16.04. Specific Java error is: Failed to get the session[java.lang.OutOfMemoryError: unable to create new native thread This appears to be related to systemd, and specific to 16.04, since the software functions properly in previous versions of Ubuntu (verified with 15.04 and 15.10) and also works in 16.04 when the system is reverted to upstart init. I have also verified that a working 15.10 installation (systemd) fails after upgrading to 16.04. Currently, we are recommending that users don't upgrade to 16.04. Thanks you for your assistance and I can provide additional information as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1583232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583232] Re: Wowza Streaming Engine out of memory on Ubuntu 16.04
*** This bug is a duplicate of bug 1578080 *** https://bugs.launchpad.net/bugs/1578080 Well it looks like I have the same problem with JetBrains Upsource. When starting from systemd it never manages to start up, the Java VM runs out of memory before finishing the startup every single time. (Same java error as OP.) If running the startup script normally by console it finishes the startup without error every single time. Now, after setting up all the scripts I needed for systemd, it seems I will have to set up upstart. This is really upsetting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1583232 Title: Wowza Streaming Engine out of memory on Ubuntu 16.04 Status in systemd package in Ubuntu: New Bug description: Wowza Streaming Engine using systemd runs out of memory within a few minutes on Ubuntu 16.04. Specific Java error is: Failed to get the session[java.lang.OutOfMemoryError: unable to create new native thread This appears to be related to systemd, and specific to 16.04, since the software functions properly in previous versions of Ubuntu (verified with 15.04 and 15.10) and also works in 16.04 when the system is reverted to upstart init. I have also verified that a working 15.10 installation (systemd) fails after upgrading to 16.04. Currently, we are recommending that users don't upgrade to 16.04. Thanks you for your assistance and I can provide additional information as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1583232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
