| Summary: | systemd cgroup limit management is unreliable | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Strauss <david> | ||||||||
| Component: | systemd | Assignee: | systemd-maint | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | johannbg, lpoetter, metherid, mschmidt, notting, plautrba, systemd-maint | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | systemd-37-11.fc16 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-01-30 20:58:51 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
David Strauss
2011-10-27 22:26:47 UTC
Created attachment 530584 [details]
Console log
(In reply to comment #0) > Steps to Reproduce: > 1. Configure a service unit with cgroups limits. > 2. systemctl --system daemon-reload > 3. systemctl restart NAME.service > 4. Check the cgroup limits for the server. They should currently be correct. > 5. systemctl restart NAME.service > 6. systemctl restart NAME.service # A third restart usually isn't necessary to > reproduce the problem, but I did see *once* where it was. > 7. Check the cgroup limits for the server. They should currently be correct. > > It usually only takes one more restart to lose the ability to write the limits. Whoops, that's wrong. Here's what I meant to write: Steps to Reproduce: 1. Configure a service unit with cgroups limits. 2. systemctl --system daemon-reload 3. systemctl restart NAME.service 4. Check the cgroup limits for the server. They should currently be correct. 5. systemctl restart NAME.service 6. systemctl restart NAME.service # A third restart usually isn't necessary to reproduce the problem, but I did see *once* where it was. 7. Check the cgroup limits for the server. They should currently be *incorrect*. It usually only takes *two restarts* after the systemd reload to lose the ability to write the limits. Just verified on a fresh installation of F16. See the attached screenshots with the relevant info using a *very* simple service (a simple unit running a Python script that simply sleeps 600 seconds). Created attachment 530587 [details]
F16 verification
Created attachment 530588 [details]
tail of messages on F16
Fixed now upstream in git. I can vouch for this fix working. systemd-37-6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/systemd-37-6.fc16 Package systemd-37-6.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-6.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-6.fc16 then log in and leave karma (feedback). Package systemd-37-7.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-7.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-7.fc16 then log in and leave karma (feedback). Package systemd-37-8.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-8.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-8.fc16 then log in and leave karma (feedback). Package systemd-37-10.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-10.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-10.fc16 then log in and leave karma (feedback). Package systemd-37-11.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-11.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-11.fc16 then log in and leave karma (feedback). systemd-37-11.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |