top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Server dies after cenos kernel upgrade

0 votes

I am running a server with CentOS release 6.4 (Final) and the kernel version of 2.6.32-279.19.1.el6.x86_64 and everything looks ok, but when I do a yum update on the kernel to update it to a newer version "2.6.32-358.11.1.el6".

It will not restart after the required reboot. It will start to load until the task bar at the bottom gets to the end than it stops loading I have been patient with it unless it requires more time to start but after 10min it was still just sitting at the task bar.

This is a VM machine so I just revert to a previous snapshot, but what should I be looking for that would cause this, and how should I fix it?

posted Jul 4, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

I recall this happening to me in the past.
Hit esc when the loading bar starts to run across the screen and see what it stops on. Go into single user mode and see if you can look at the logs.
Can you select the older kernel when the grub pops up? You may have to use chkconfig to disable services from starting after you see whats in the way.

answer Jul 4, 2013 by anonymous
Similar Questions
+1 vote

Is there a way to redirect ports 80 and 443 to 8443. I have a non root user but I cannot use CentOS firewalld nor iptables. I have tried these things. But it still fails.

+1 vote

I want to use fail2ban on CentOS 6 to monitor Apache with the standard default logfile format ("combined"). Has anyone here succeeded in doing so?

The format has the IP at the start of the line, followed by two dashes (if no authentication) and THEN the timestamp. What I've read on the fail2ban wiki seems to say that the timestamp must ALWAYS be at the start of the line, followed by other stuff. I'm amazed if it isn't configurable...

I'm using fail2ban 0.8.8 from EPEL.

0 votes

I have svn server running on Windows XP as service (using svnserve.exe). Everything was working fine until I switched server from 1.7 to 1.8. From that moment, every few days, SVN server would freeze eating up all cpu it can (50% on dual core system). Note that I upgraded repository after upgrading svn software.

0 votes

I am using Ubuntu 14.04 and facing problem with ubuntu? On my machine Skype starts, asks to log in and then presents its list of connections. However after a couple of moments the list of connections gets
"inactive" (greys out) and finally disappears.

In the crash window that then pops up I see that something with seems to be amiss.

Any idea what I can do to fix the problem and where do I find the info that is in the "crash report window" so I
could add it to this email if needed?