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.
DescriptionChristopher J Suleski
2011-11-22 15:32:39 UTC
Description of problem:
When switching to runlevel 1 from runlevel 3, control of the serial console is passed directly to sushell or sulogin (configured in /etc/sysconfig/init). The serial console loses its terminal settings during the runlevel change, making it impossible to login via sulogin. Entering any key immediately kicks back an incorrect password response. sushell has similar problems but executing "reset" can fix that condition.
Version-Release number of selected component (if applicable):
initscripts-9.03.23-1.el6
How reproducible:
Always
Steps to Reproduce:
1. Configure a serial console in RHEL6, set SINGLE=/sbin/sulogin in /etc/sysconfig/init
2. Boot into runlevel 3, then switch to runlevel 1
3. Try entering the root password
Actual results:
Password input is not taken, sulogin immediately rejects any input. If sushell is specified instead, newlines do not work for output.
Expected results:
Should be able to enter password to sulogin. For sushell, the terminal should properly print newlines.
Additional info:
This does not occur when booting directly into a single mode serial console, only when switching from a higher runlevel.
Executing "stty sane" before "exec $SINGLE" in /etc/init/rcS-sulogin.conf works around this problem by setting certain terminal defaults.
I had considered filing a bug against sysvinit-tools because sulogin is not resetting the terminal, but this issue also affects sushell which simply passes control to the default shell. The easiest fix may be addressing this in initscripts.
we are HP guys , we can access this bug 756045 , but we can't access 746801. Anyone can update the latest news about this bug? thanks.
this bug can also be reproduced on a DL980 with RHEL 6.4s2,the same issue.
we are testing RHEL6.4s4 ,if we still have this bug, we will re-file a new bugzilla to report this bug again.
We have agreed that this should be probably fixed in upstart and patch is quite short. But upstart was not planned no be updated in RHEL6.4.
--- a/init/system.c
+++ a/init/system.c
@@ -111,6 +111,7 @@ system_setup_console (ConsoleType type,
if (type == CONSOLE_OWNER)
ioctl (fd, TIOCSCTTY, 1);
+ reset = 1;
break;
case CONSOLE_NONE:
/* No console really means /dev/null */