Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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?
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 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 ***