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:
it is not a new problem: https://bugzilla.redhat.com/show_bug.cgi?id=1201952
and there suggested workaround works,
$ echo 10000 > /sys/fs/cgroup/cpu/system.slice/cpu.rt_runtime_us
but it'd great to have it fixed within the package.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 2Andreas Schneider
2017-02-15 15:55:01 UTC
Did you try to setting
LimitRTPRIO=infinity
LimitRTTIME=100000
in the ctdb.service file?
I do: system edit ctdb
there:
[Service]
ExecStartPre=/bin/sh -c "echo 10000 > /sys/fs/cgroup/cpu/system.slice/cpu.rt_runtime_us"
#LimitRTPRIO=infinity
#LimitRTTIME=100000
TimeoutStartSec=300
Restart=on-failure
RestartSec=20
But Limit options don't work for me.
(In reply to lejeczek from comment #6)
> Does not seem like start even honours this option. I put it in
> /etc/sysconfig/ctdb. Still fails the same.
The configuration parameter 'CTDB_NOSETSCHED' is only valid from ctdb version >=4.5. IIRC, RHEL 7.3 does not ship ctdb >=v4.5. In that case you may have to manually modify the ctdbd_wrapper script to disable real-time scheduling during start-up. Make changes to /usr/sbin/ctdbd_wrapper script along the following lines:
@@ -22,6 +22,8 @@ fi
. "${CTDB_BASE}/functions"
loadconfig "ctdb"
+CTDB_NOSETSCHED=yes
+
[ -n "$CTDB_SOCKET" ] && export CTDB_SOCKET
ctdbd="${CTDBD:-/usr/local/sbin/ctdbd}"
@@ -163,6 +165,7 @@ build_ctdb_options ()
maybe_set "--start-as-stopped " "$CTDB_START_AS_STOPPED" "yes"
maybe_set "--no-recmaster" "$CTDB_CAPABILITY_RECMASTER" "no"
maybe_set "--no-lmaster" "$CTDB_CAPABILITY_LMASTER" "no"
+ maybe_set "--nosetsched" "$CTDB_NOSETSCHED" "yes"
maybe_set "--lvs --single-public-ip" "$CTDB_LVS_PUBLIC_IP"
maybe_set "--script-log-level" "$CTDB_SCRIPT_LOG_LEVEL"
maybe_set "--max-persistent-check-errors" "$CTDB_MAX_PERSISTENT_CHECK_ERRORS"
See the extra lines(starting with the plus '+' symbol) to be added to ctdbd_wrapper script which is invoked by ctdb service file.
Comment 8Andreas Schneider
2018-04-18 09:15:31 UTC
This has been addressed in the meantime, see comment #7. Closing.