elleryjh

Well-Known Member
Apr 12, 2003
479
0
166
I am running RHEL 3 with kernel linux-2.6.14.6-grsec. I have been trying to upgrade (or go to the 2.4 branch) with no luck.
I tried the latest 2.4 RPM from RH, 2.4.21-47. I used the lilo -R switch so it could be restarted if the kernel failed. The server never came back and had to be rebooted into the previous kernel.
I tried compiling a generic 2.6 kernel following the guide at eth0.us - http://www.eth0.us/generic-2.6.10 - of course using the latest stable version (2.6.17.7), not 2.6.10. It compiled fine, installed fine, lilo accepted it. Again used lilo -R to set the bootup image. But it didn't come back up on a reboot, same as the 2.4 I tried.


There's nothing but a big time gap in /var/log/messages, and I can't find any logs that report anything.

Am I missing something here? Any ideas?

How would I go about troubleshooting this?
 

DigiCrime

Well-Known Member
Nov 27, 2002
399
0
166
grsecurity is specific to the kernel you apply it to and the latest one is 2.6.17.7 which probably wouldnt work on the one your applying to... check with their support forum and see http://forums.grsecurity.net/ eth0 guide I think will work for anything 2.6.13 and under but 2.6.14 has a udev differences or something along that line I forgot now
 

elleryjh

Well-Known Member
Apr 12, 2003
479
0
166
I previously had grsecurity and I was just trying to replace it with a standard kernel without the grsecurity patch.

I've applied the latest grsecurity patch 2.6.17.7, but that had the same problem - the server never came back up after the reboot!

Any other ideas?
 

DigiCrime

Well-Known Member
Nov 27, 2002
399
0
166
Nope, without knowing the error or panic I dont think anyone would know. Ask your noc to reboot it into that kernel and see what the error is, most of them will tell you.