Hide Forgot
Description of problem: Starting from RHEL7.3, the systemd does not accept numeric value for LimitMEMLOCK and LimitSTACK. It only accepts "infinity" The systemd parsing LimitNOFILE and LimitNPROC without error. Affected versions systemd-219-30.el7 systemd-219-30.el7_3.6 How reproducible: Always Steps to Reproduce: 1. Create custom startup configuration file. Add LimitStack and LimitMEMLOCK in [Service] section. # more my-local.service [Unit] Description=my last service After=default.target Before=shutdown.target [Service] Type=oneshot ExecStart=/usr/local/bin/dummy.sh RemainAfterExit=yes LimitNOFILE=65536 LimitNPROC=16384 LimitSTACK=12345 LimitMEMLOCK=5432100 [Install] WantedBy=default.target 2. Reboot system 3. After bootup, check log. Actual results: systemd[1]: [/etc/systemd/system/my-local.service:12] Failed to parse resource value, ignoring: 12345 systemd[1]: [/etc/systemd/system/my-local.service:13] Failed to parse resource value, ignoring: 5432100 Additional info: Between RHEL7.0 and 7.2, systemd accept LimitSTACK and LimtMEMLOCK. And it didn't produce any parsing errors.
Hi Iida-san, We found that the same issue was already reported at https://bugzilla.redhat.com/show_bug.cgi?id=1396277. Can we close this bugzilla and discuss the issue in bz#1396277? In bz#1396277, there is no description which addresses LimitMEMLOCK. I'll add the comment in bz#1396277. Regards, Keigo
I don't think Masanari will have an issue with that as long as LimitMEMLOCK gets tested and confirmed that it no longer causes an issue either otherwise the other BZ will need to move backwards from post and be reworked. Given that the other BZ says there wasn't a test case for LimitSTACK and LimitMEMLOCK can you confirm that every one of the Limit* settings now has a test case to prevent anything like this happening in the future?
Can the regression keyword please also be added to the other BZ if this is closed as a duplicate?
Hi Shane-san, Thank you for your update. I added Regression keyword in bz#1396277 and asked the engineering team to add test cases for other parameters which uses config_parse_bytes_limit(). I'll update the support case when I get a reply from our engineering. Regards, Keigo
Hi Noha-san, you may close this case as duplicate of bz#1396277. I will follow the bz#1396277 to see the progress. Thanks.
Hi Iida-san, I close this case as duplicate of bz#1396277. And I'll share the progress of the bugzilla and handle requests through the support case. Regards, Keigo *** This bug has been marked as a duplicate of bug 1396277 ***