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.
Previously, remote "tuned" service starts could have led to a service unresponsiveness under certain circumstances. With this update, the handling of stdin, stdout, or stderr during the service creation has been fixed to resolve this problem.
Description of problem:
We have a network based test configuration which requires tuned profile tuning to be initiated via a remote command (ssh). Remotely requesting tuned-adm to set a specific profile causes the command to hang
# ssh root@bigi tuned-adm profile default
Stopping tuned: [ OK ]
Switching to profile 'default'
Applying ktune sysctl settings:
/etc/ktune.d/tunedadm.conf: [ OK ]
Applying sysctl settings from /etc/sysctl.conf
Starting tuned: [ OK ]
<HANG>
This didn't happen with beta for 6.1 nor 6.0. There are no issues running the command when remotely logged in.
The command:
# ssh bigi tuned-adm profile default >& /dev/null &
Gets stopped almost instantly with
[1]+ Stopped ssh bigi tuned-adm profile default >&/dev/null
Is this a job control issue ?
Version-Release number of selected component (if applicable):
RHEL6.1-20110406.0 2.6.32-130.el6.x86_64
How reproducible:
every time
Steps to Reproduce:
1. see above
2.
3.
Actual results:
Expected results:
Additional info:
Comment 2RHEL Program Management
2011-04-12 06:01:43 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Found a fix for the problem, was due to incorrect handling of stdin/stdout/stderr during daemon creation.
Patch send to review, proposing for RHEL-6.2 to get this fixed.
Thanks & regards, Phil
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously, remote "tuned" service starts could have led to a service unresponsiveness under certain circumstances. With this update, the handling of stdin, stdout, or stderr during the service creation has been fixed to resolve this problem.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-1176.html
Description of problem: We have a network based test configuration which requires tuned profile tuning to be initiated via a remote command (ssh). Remotely requesting tuned-adm to set a specific profile causes the command to hang # ssh root@bigi tuned-adm profile default Stopping tuned: [ OK ] Switching to profile 'default' Applying ktune sysctl settings: /etc/ktune.d/tunedadm.conf: [ OK ] Applying sysctl settings from /etc/sysctl.conf Starting tuned: [ OK ] <HANG> This didn't happen with beta for 6.1 nor 6.0. There are no issues running the command when remotely logged in. The command: # ssh bigi tuned-adm profile default >& /dev/null & Gets stopped almost instantly with [1]+ Stopped ssh bigi tuned-adm profile default >&/dev/null Is this a job control issue ? Version-Release number of selected component (if applicable): RHEL6.1-20110406.0 2.6.32-130.el6.x86_64 How reproducible: every time Steps to Reproduce: 1. see above 2. 3. Actual results: Expected results: Additional info: