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.

Bug 894470

Summary: runlevel3 console isn't displayed after booting
Product: Red Hat Enterprise Linux 6 Reporter: Jay Rishel <jay>
Component: initscriptsAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED INSUFFICIENT_DATA QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3CC: lnykryn, tgummels
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-14 16:01:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
example kickstart file used none

Description Jay Rishel 2013-01-11 20:24:38 UTC
Created attachment 677083 [details]
example kickstart file used

Description of problem: after new kickstarted install of RHEL6.3, booting to runlevel 3, console is never returned, but completed status bar remains on screen.  turning off rhgb quiet boot options shows system is stuck right after "starting certmonger [OK]"  console back be accessed by switching to another virtual console


Version-Release number of selected component (if applicable):


How reproducible:
everytime.  two differet kickstarts on different systems of RHEL6.3 show this issue.

Steps to Reproduce:
1. kickstart host
2. wait for boot to complete

  
Actual results:
no login prompt, just a complete status bar

Expected results:
login prompt

Additional info:

Comment 1 Jay Rishel 2013-01-11 20:26:05 UTC
had wrong component initially, changed to sysvinit?

Comment 3 Lukáš Nykrýn 2013-01-14 08:53:59 UTC
Can you please past here output of initctl list and content of /etc/rc.d/rc3.d/? Do you have something in /etc/rc.d/rc.local?

Comment 4 Jay Rishel 2013-01-14 16:10:34 UTC
[root@pidco111 ~]# initctl list
rc stop/waiting
tty (/dev/tty3) start/running, process 1828
tty (/dev/tty2) start/running, process 1826
tty (/dev/tty6) start/running, process 1834
tty (/dev/tty5) start/running, process 1832
tty (/dev/tty4) start/running, process 1830
plymouth-shutdown stop/waiting
control-alt-delete stop/waiting
rcS-emergency stop/waiting
readahead-collector stop/waiting
kexec-disable stop/waiting
quit-plymouth stop/waiting
rcS stop/waiting
prefdm start/running, process 1821
init-system-dbus stop/waiting
readahead stop/waiting
splash-manager stop/waiting
start-ttys stop/waiting
readahead-disable-services stop/waiting
rcS-sulogin stop/waiting
serial stop/waiting

[root@pidco111 ~]# cd /etc/rc3.d/
[root@pidco111 rc3.d]# ls
K01smartd        K74ntpd            S11auditd        S50mcelogd
K02oddjobd       K75ntpdate         S11portreserve   S50snmpd
K10cups          K75quota_nld       S12rsyslog       S55sshd
K10psacct        K84NetworkManager  S13cpuspeed      S56xinetd
K10saslauthd     K84wpa_supplicant  S13irqbalance    S82abrt-ccpp
K15svnserve      K85mdmonitor       S13rpcbind       S82abrtd
K30sendmail      K86cgred           S20kdump         S82abrt-oops
K30spamassassin  K87multipathd      S22messagebus    S90crond
K35dovecot       K87restorecond     S24avahi-daemon  S95atd
K35tgtd          K88sssd            S24nfslock       S97rhnsd
K50dnsmasq       K89rdisc           S24rpcgssd       S97rhsmcertd
K50netconsole    K92ip6tables       S24rpcidmapd     S99certmonger
K50snmptrapd     K92iptables        S25netfs         S99firstboot
K60nfs           K95cgconfig        S26acpid         S99libvirt-guests
K69rpcsvcgssd    K99rngd            S26haldaemon     S99local
K73ypbind        S01sysstat         S26udev-post
K74ipsec         S02lvm2-monitor    S27ypbind
K74nscd          S10network         S28autofs

[root@pidco111 rc3.d]# cat /etc/rc.d/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local
[root@pidco111 rc3.d]#

Comment 5 Lukáš Nykrýn 2013-01-14 16:58:37 UTC
I think that there is probably nothing wrong with init. Can you please check that there are no error messages about mingetty / getty / tty in your log files? Or can you try to start getty manually ('/sbin/mingetty /dev/tty1' or 'start tty TTY=/dev/tty1')?

Comment 6 Jay Rishel 2013-01-14 17:25:26 UTC
nothing in /var/log/messages, just a note to register with RHN.

running "/sbin/mingetty /dev/tty1" completes without error.

Comment 7 Lukáš Nykrýn 2013-01-15 11:52:52 UTC
Can you please try to add init=/sbin/init --verbose to your kernel line and then post here content of /var/log/messages.

Comment 8 Lukáš Nykrýn 2013-01-15 12:16:55 UTC
And just to be sure, did you modify /etc/sysconfig/init or /etc/init/start-ttys.conf and /etc/init/tty.conf?

Comment 9 Jay Rishel 2013-01-16 21:10:15 UTC
no changes to /etc/sysconifg/init, start-ttys.conf or tty.conf

below is end of /var/log/messages with init set to verbose:
Jan 16 10:57:01 pidco11 xinetd[1673]: xinetd Version 2.3.14 started with libwrap loadavg l
abeled-networking options compiled in.
Jan 16 10:57:01 pidco11 xinetd[1673]: Started working: 0 available services
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling started event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling starting event
Jan 16 10:57:01 pidco11 abrtd: Init complete, entering main loop
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling started event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling starting event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling started event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling starting event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling started event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling starting event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling started event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling starting event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling started event
Jan 16 10:57:01 pidco11 init: Connection from private client
Jan 16 10:57:01 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: rc main process (1085) exited normally
Jan 16 10:57:02 pidco11 init: rc goal changed from start to stop
Jan 16 10:57:02 pidco11 init: rc state changed from running to stopping
Jan 16 10:57:02 pidco11 init: Handling stopping event
Jan 16 10:57:02 pidco11 init: rc state changed from stopping to killed
Jan 16 10:57:02 pidco11 init: rc state changed from killed to post-stop
Jan 16 10:57:02 pidco11 init: rc state changed from post-stop to waiting
Jan 16 10:57:02 pidco11 init: Handling stopped event
Jan 16 10:57:02 pidco11 init: prefdm goal changed from stop to start
Jan 16 10:57:02 pidco11 init: prefdm state changed from waiting to starting
Jan 16 10:57:02 pidco11 init: start-ttys goal changed from stop to start
Jan 16 10:57:02 pidco11 init: start-ttys state changed from waiting to starting
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: prefdm state changed from starting to pre-start
Jan 16 10:57:02 pidco11 init: prefdm state changed from pre-start to spawned
Jan 16 10:57:02 pidco11 init: prefdm main process (1761)
Jan 16 10:57:02 pidco11 init: prefdm state changed from spawned to post-start
Jan 16 10:57:02 pidco11 init: prefdm state changed from post-start to running
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: start-ttys state changed from starting to pre-start
Jan 16 10:57:02 pidco11 init: start-ttys state changed from pre-start to spawned
Jan 16 10:57:02 pidco11 init: start-ttys main process (1762)
Jan 16 10:57:02 pidco11 init: start-ttys state changed from spawned to post-start
Jan 16 10:57:02 pidco11 init: start-ttys state changed from post-start to running
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: readahead-collector goal changed from start to stop
Jan 16 10:57:02 pidco11 init: readahead-collector state changed from running to pre-stop
Jan 16 10:57:02 pidco11 init: readahead-collector pre-stop process (1763)
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: tty (/dev/tty2) goal changed from stop to start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty2) state changed from waiting to starting
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: tty (/dev/tty2) state changed from starting to pre-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty2) state changed from pre-start to spawned
Jan 16 10:57:02 pidco11 init: tty (/dev/tty2) main process (1768)
Jan 16 10:57:02 pidco11 init: tty (/dev/tty2) state changed from spawned to post-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty2) state changed from post-start to running
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: tty (/dev/tty3) goal changed from stop to start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty3) state changed from waiting to starting
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: tty (/dev/tty3) state changed from starting to pre-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty3) state changed from pre-start to spawned
Jan 16 10:57:02 pidco11 init: tty (/dev/tty3) main process (1770)
Jan 16 10:57:02 pidco11 init: tty (/dev/tty3) state changed from spawned to post-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty3) state changed from post-start to running
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: tty (/dev/tty4) goal changed from stop to start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty4) state changed from waiting to starting
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: tty (/dev/tty4) state changed from starting to pre-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty4) state changed from pre-start to spawned
Jan 16 10:57:02 pidco11 init: tty (/dev/tty4) main process (1772)
Jan 16 10:57:02 pidco11 init: tty (/dev/tty4) state changed from spawned to post-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty4) state changed from post-start to running
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: tty (/dev/tty5) goal changed from stop to start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty5) state changed from waiting to starting
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: tty (/dev/tty5) state changed from starting to pre-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty5) state changed from pre-start to spawned
Jan 16 10:57:02 pidco11 init: tty (/dev/tty5) main process (1774)
Jan 16 10:57:02 pidco11 init: tty (/dev/tty5) state changed from spawned to post-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty5) state changed from post-start to running
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: Connection from private client
Jan 16 10:57:02 pidco11 init: tty (/dev/tty6) goal changed from stop to start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty6) state changed from waiting to starting
Jan 16 10:57:02 pidco11 init: Handling starting event
Jan 16 10:57:02 pidco11 init: tty (/dev/tty6) state changed from starting to pre-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty6) state changed from pre-start to spawned
Jan 16 10:57:02 pidco11 init: tty (/dev/tty6) main process (1778)
Jan 16 10:57:02 pidco11 init: tty (/dev/tty6) state changed from spawned to post-start
Jan 16 10:57:02 pidco11 init: tty (/dev/tty6) state changed from post-start to running
Jan 16 10:57:02 pidco11 init: Handling started event
Jan 16 10:57:02 pidco11 init: start-ttys main process (1762) exited normally
Jan 16 10:57:02 pidco11 init: start-ttys goal changed from start to stop
Jan 16 10:57:02 pidco11 init: start-ttys state changed from running to stopping
Jan 16 10:57:02 pidco11 init: Handling stopping event
Jan 16 10:57:02 pidco11 init: start-ttys state changed from stopping to killed
Jan 16 10:57:02 pidco11 init: start-ttys state changed from killed to post-stop
Jan 16 10:57:02 pidco11 init: start-ttys state changed from post-stop to waiting
Jan 16 10:57:02 pidco11 init: Handling stopped event
Jan 16 10:57:03 pidco11 gdm-binary[1761]: WARNING: GdmDisplay: display lasted 0.417577 seconds
Jan 16 10:57:03 pidco11 gdm-binary[1761]: WARNING: GdmDisplay: display lasted 0.069902 seconds
Jan 16 10:57:03 pidco11 gdm-binary[1761]: WARNING: GdmDisplay: display lasted 0.069507 seconds
Jan 16 10:57:03 pidco11 gdm-binary[1761]: WARNING: GdmDisplay: display lasted 0.068925 seconds
Jan 16 10:57:03 pidco11 gdm-binary[1761]: WARNING: GdmDisplay: display lasted 0.070193 seconds
Jan 16 10:57:03 pidco11 gdm-binary[1761]: WARNING: GdmDisplay: display lasted 0.069658 seconds
Jan 16 10:57:03 pidco11 gdm-binary[1761]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Jan 16 10:57:12 pidco11 init: readahead-collector pre-stop process (1763) exited normally
Jan 16 10:57:12 pidco11 init: readahead-collector state changed from pre-stop to stopping
Jan 16 10:57:12 pidco11 init: Handling stopping event
Jan 16 10:57:12 pidco11 init: readahead-collector state changed from stopping to killed
Jan 16 10:57:12 pidco11 init: Sending TERM signal to readahead-collector main process (504)

Jan 16 10:57:13 pidco11 init: readahead-collector main process (504) exited normally
Jan 16 10:57:13 pidco11 init: readahead-collector state changed from killed to post-stop
Jan 16 10:57:13 pidco11 init: readahead-collector post-stop process (1828)
Jan 16 10:57:13 pidco11 kernel: readahead-collector: starting delayed service auditd
Jan 16 10:57:13 pidco11 auditd[1845]: Started dispatcher: /sbin/audispd pid: 1847
Jan 16 10:57:13 pidco11 audispd: No plugins found, exiting
Jan 16 10:57:13 pidco11 auditd[1845]: Init complete, auditd 2.2 listening for events (startup state enable)
Jan 16 10:57:13 pidco11 kernel: readahead-collector: sorting
Jan 16 10:57:13 pidco11 kernel: readahead-collector: finished
Jan 16 10:57:13 pidco11 init: readahead-collector post-stop process (1828) exited normally
Jan 16 10:57:13 pidco11 init: readahead-collector state changed from post-stop to waiting
Jan 16 10:57:13 pidco11 init: Handling stopped event

Comment 10 Lukáš Nykrýn 2013-01-17 08:08:56 UTC
Can you please try this modified /etc/init/start-ttys.conf and post here content of /tmp/tty.log?

start on stopped rc RUNLEVEL=[2345]

env ACTIVE_CONSOLES=/dev/tty[1-6]
env X_TTY=/dev/tty1
task
script
	exec > /tmp/tty.log 2>&1
	set -x
	. /etc/sysconfig/init
	for tty in $(echo $ACTIVE_CONSOLES) ; do
		[ "$RUNLEVEL" = "5" -a "$tty" = "$X_TTY" ] && continue
		initctl start tty TTY=$tty
	done
end script

Comment 11 Lukáš Nykrýn 2013-04-02 11:51:25 UTC
Is there any update on this one?

Comment 12 Lukáš Nykrýn 2013-04-02 11:58:01 UTC
And this is not the right component, if there is a bug it is probably in upstart, getty or initscripts.

Comment 13 Lukáš Nykrýn 2013-05-14 16:01:09 UTC
Due to lack of response, closing as INSUFFICIENT_DATA. Feel free to reopen this bug, if there is any new information.