I have recently upgraded centOS 6.6 to 7. It seemingly boots up, but it can not open the log in page, Actually the systems is frozen here. Does anybody have similar experience? If so, it would be great to help with this.
Had the same problem driving me nuts! It just takes forever to show the login prompt. On my VM it took around 25 minutes! The problem for me was on the audit package installed.
Problem #1 :
yumnot working - could not find
libsasl2.so.2The upgrade process resulted in me having
/usr/lib64/libsasl2.so.3. just create a symlink in
ln -s /usr/lib64/libsasl2.so.3 /usr/lib64/libsasl2.so.2
Problem #2 :
yumwas working again but could not complete most operations. Had to remove
mod-perl-2.0.4-11.el6_5.x65_86. Please note that this may not apply to you.
Problem #3 : Delay during boot. removed
yum erase audit) updated
yum update glibc) and then update the system (
I rebooted and the system was up in less than 20 seconds!
While the symlink will work, I don't believe it's the complete solution. I'm not sure this solution is either. I had similar symptoms as above. Important programs like Python and sshd were linked with
libsasl2.so.2, which is a el6 package.
It seems that in my case some of the post install scripts did not run correctly. I started the rescue system, and as root in the
/root/preupgrade/postupgrade.d/pkgdowngrades, run the
fixpkgdowngrades.sh script. This fixes all the references to
libsasl2.so.2, correcting them to
libsasl2.so.3. I then removed the
I also cd'ed into each of the other directories in
/root/preupgrade/postupgrade.d and ran the scripts therein. The
/root/preupgrade/postupgrade.d/clean_centos6_pkgs/postupgrade_cleanup.sh will need to be fixed near the bottom where it exits if not called with
I would use a Live CD to bypass the login page. Then, I would use an external hard drive to transfer your important data to. Once all of the essentials are backed up, I would reinstall your OS and transfer your data back to your computer.
While you are logged into your computer with a Live CD, I would take the opportunity to review your log files to learn what transpired before this happened so that you learn how to prevent this from happening again.