Hide Forgot
Description of problem: We have upgraded initscripts from 9.03.23-1.el6 to 9.03.38-1.el6_4.2 to fix Unable to continue with Ctrl+D or login after a failed file system check. Server is hanging after starting crond service , we are unable to login screen. The issue has been fixed after downgrade from the newer version. Version-Release number of selected component (if applicable): initscripts.x86_64 0:9.03.38-1.el6_4.2 How reproducible: Upgrade initscripts rpm to 9.03.38-1.el6_4.2 version and bounce. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
There is a lot of changes between those two versions, so I can't say what to suspect. Can you please attach /var/log/messages and list of files in /etc/rc3.d and /etc/rc5.d? Also can you get a getty on the other ttys?
Thanks for your comments. Please find the plymouth path in the version "9.03.23". $ rpm -qa|grep -i initscripts initscripts-9.03.23-1.el6.x86_64 $ cat /etc/rc.d/rc.sysinit |grep -i plymouth PLYMOUTH= [ -x /usr/bin/plymouth ] && PLYMOUTH=yes [ -n "$PLYMOUTH" ] && plymouth --hide-splash [ -n "$PLYMOUTH" ] && plymouth --hide-splash [ -n "$PLYMOUTH" ] && plymouth --show-splash [ -n "$PLYMOUTH" ] && plymouth --hide-splash [ "$PROMPT" != no ] && plymouth watch-keystroke --command "touch /var/run/confirm" --keys=Ii & [ "$PROMPT" != no ] && plymouth --ignore-keystroke=Ii [ananradh@plexrportap001 ~]$ After we upgrade initscripts it becomes "/bin/plymouth". # rpm -qa|grep -i initscripts initscripts-9.03.38-1.el6_4.2.x86_64 # cat /etc/rc.d/rc.sysinit |grep -i plymouth PLYMOUTH= [ -x /bin/plymouth ] && PLYMOUTH=yes [ -n "$PLYMOUTH" ] && plymouth --hide-splash [ -n "$PLYMOUTH" ] && plymouth --hide-splash [ -n "$PLYMOUTH" ] && plymouth --show-splash [ -n "$PLYMOUTH" ] && plymouth --hide-splash if [ -x /bin/plymouth ]; then /bin/plymouth quit [ "$PROMPT" != no ] && plymouth watch-keystroke --command "touch /var/run/confirm" --keys=Ii & [ "$PROMPT" != no ] && plymouth --ignore-keystroke=Ii if [ -x /bin/plymouth ]; then /bin/plymouth --sysinit
Yes this was the fix for the issue.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Still needing requested information from comment 2.