Hello,

When I opened up WHM today, it said:

You are running an insecure kernel (2.4.20-18.7). You should upgrade to a newer version as soon as possible to avoid your system being compromised.

Could someone please help me figure out how to update it?..

Thanks in Advance,
Justin.

Search the forum. There are numerous kernel update threads, including this one. Keep in mind, however, that this is a touchy matter and you can easily hose your server, requiring a restore if not extremely careful. Consider hiring someone to do it for you if you have no experience.

What ever you do, install it using rpm -ivh and NOT rpm -Uvh, -Uvh will overwrite your working kernel, and if it bombs you may be screwed.. -ivh will install a new kernel and if it doesnt work, RS can reboot the server to the old one..


make sure u update /etc/lilo.conf with the new kernel info and then run lilo -v -v before reboobing the server to make sure there are no errors.

you can find your kernel from here depending on your redhat version and cpu type. http://updates.redhat.com

That's good advice...if you decide to do it yourself. As Foggy says, updating your kernel "is not for the faint of heart".

It's pretty straight forward.

Log in via SSH,

Do...

wget ftp://updates.redhat.com/9/en/os/i686/ker...0-24.9.i686.rpm

then...

rpm -ivh kernel-2.4.20-24.9.i686.rpm

(note the -i and not a -u)

edit your /etc/lilo.conf with pico

You want it to look similar to this...

prompt
timeout=50
default=2.4.20-24.9
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear

image=/boot/vmlinuz-2.4.18-26.7.x
label=linux
root=/dev/hda2
read-only
initrd=/boot/initrd-2.4.18-26.7.x.img

image=/boot/vmlinuz-2.4.20-24.9
label=2.4.20-24.9
root=/dev/hda2
read-only
initrd=/boot/initrd-2.4.20-24.9.img

(Notice that are two kernels listed - label=linux & label=2.4.20-24.9 - so make sure the version you want to boot from, in this case the 2.4.20-24.9 is in default=2.4.20-24.9 - if you want to boot the old kernel, change it to default=linux)

Now in shell do...

/sbin/lilo

then...

reboot

You should be all set now. If so be sure to remember me when I am in need!

I offer 100% money back guarantee, I will refund your full purchase price of $0, but no warranties beyond that.


Added Note: Notice that the wget statement is assuming you have Redhat 9, if not then use the correct url in its place for your version of Linux.

Hello,

When going in shell and using lilo -v -v I get something to this effect on each.....

root@server01 [~]# lilo -v -v
LILO version 21.4-4, Copyright © 1992-1998 Werner Almesberger
'lba32' extensions Copyright © 1999,2000 John Coffman

Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Message: 46 sectors.
Boot image: /boot/vmlinuz-2.4.18-26.7.x
Fatal: open /boot/vmlinuz-2.4.18-26.7.x: No such file or directory
Removed temporary file /boot/map~

Thanks in Advance,
Justin.

In the /etc/lilo.conf replace the x with the old kernel number. Basically it will be the line that was in the config before all of the editing. Look in /boot/ should only be 2 files named vmlinuz, one you already have in the config and the other one.

I followed the above steps and it worked great.

Thanks!

Hello,
Is the !686 the processor type? If yes how do I check for this type on my server? I have Lunix 7.3, could someone post the link for this file.
Thank you.
Carol

ALL servers at EV1 will accept the i686 rpms. The only exception would be the AMD Machines which DO work with the i686 rpm, but the K7 rpm is better for them.

Thank you for the reply!
Carol

I have done the kernel upgrade, but whm still give the following message:
You are running an insecure kernel (2.4.20-18.7). You should upgrade to a newer version as soon as possible to avoid your system being compromised.
I have done a "Graceful Reboot" and a "Forceful Reboot". It still give me the error message.
How do I check for the kernel version in ssh.
Please help
Thank you.
Carol

uname -a

Make sure you've edited /etc/lilo.conf and setup the new kernel as "default" and then run lilo -v -v. Then you can reboot your box.

You guys are Great!
I have upgraded the kernel and everything at this point seems to work very well. It was my mistake that after editting lilo.conf I did not run lilo -v -v.
Thank you LighthousePoint for your prompt reply and hostedzone for his simple How-to.
Have a great Hollyday Everyone!
Carol:)

After running the rpm I get:

Preparing... ########################################### [100%]
1:kernel ########################################### [100%]
stdin: is not a tty
stdin: is not a tty
stdin: is not a tty

It looks like the initrd and the vmlinuz are there for the new version. Just didn't know if this meant there was an error. Can someone put me at ease before I reboot?

Hello,

Here's all the files I have listed in boot for my kernels:


vmlinuz-2.4.20-24.7 1072329 01 Dec 2003 13:42 «1070304144
vmlinuz-2.4.20-18.7 1073013 29 May 2003 08:56 «1054213005
vmlinuz-2.4.18-3 1030147 18 Apr 2002 07:44 «1019130306
vmlinuz 1072329 01 Dec 2003 13:42 «1070304144
vmlinux-2.4.20-24.7 2989435 01 Dec 2003 13:42 «1070304144
vmlinux-2.4.20-18.7 2993373 29 May 2003 08:56 «1054213005
vmlinux-2.4.18-3

Could you please help me figure out how my lilo.conf file should look like based on that?..

Thanks in Advance,
Justin.

That "error" means nothing and you are fine to reboot, make sure you did the lilo -v -v and checked the config.




Justin:
Your lilo.conf will have the version numbers
2.4.20-24.7
but i am running 2.4.20-24.9, its late and I am about off to bed but make sure that 24.9 is not available for your release of redhat. If it is just make another section with the "2.4.20-24.7" set of numbers vs the old one making sure to keep the old with a different label in case of errors.

it worked perfectly!

sucks... no emotion today!

btw... is 2.4.20-24.7 a "recommended" kernel for rh 7.3?

-- Dave

Worked excellent! Thank you for this info.

2.4.20-24.7 = RH 7.x
2.4.20-24.8 = RH 8.x
2.4.20-24.9 = RH 9.x

2.4.20 = release, -24 = build, .9 = Red Hat Linux Number

i did every thing,

still no update


there is no patch file that i can run to do every thing???

Hello,

I am not trying to be rude here, but I tried everything too and it worked just fine.

I think we'll need both a rundown of exactly what you did and what system you are on in order for anyone to really lend a hand.

Some information here for us to go on at least.

Thanks.

Hello,

Is there any possible way that I can make sure that my server will boot from the old kernel until I get this fixed, cause my server really needs a reboot .. been up for 33 days 17 hours 12 minutes 8 seconds...

Thanks in Advance,
Justin.

Hello,

Nevermind.. I just edited the default in lilo.conf to do that

Justin.

Hello,

To make sure im doing this right.. im runing an Intel P4, cpanel, Redhat 7.3.. which version do I get from Redhat?.. like i686 or what?..

Thanks in Advance,
Justin.

Hi there,

I used this kernel version for my P4 / 7.3 server and it worked just fine.

wget http://updates.redhat.com/7.3/en/os/i686/k...0-24.7.i686.rpm

- Ricoche

That direct link to an rpm that I posted above will work fine for you, for that matter all of the configs should look the same(as far as the new parts) because it will be the exact same. Remember to run lilo -v -v and that will double check everything before you reboot.

Hello,

Everything has worked fine in the update til i get to run lilo -v -v and i get :

"Boot image: /boot/vmlinuz-2.4.18-26.7.3
Fatal: open /boot/vmlinuz-2.4.18-26.7.3: No such file or directory"

When I edit /etc/lilo.conf what do I put for that boot part if im updating using the above wget url?

Thanks in Advance,
Justin.

image=/boot/vmlinuz-2.4.20-24.9
label=2.4.20-24.9
initrd=/boot/initrd-2.4.20-24.9.img
read-only
root=/dev/hda2


the only problem would be with the root=/dev/hdaX, make sure its the same as the other entries

Hello,

Sorry bout this, but it dont make any sense to me, cause im running 7.3 not v9

Justin.

Search the RH site for
2.4.20-24.7
get that kernel version and just change it to


image=/boot/vmlinuz-2.4.20-24.7
label=2.4.20-24.7
initrd=/boot/initrd-2.4.20-24.7.img
read-only
root=/dev/hda2

Hello,

From my knowledge everything went well and I changed it all like yall have said to do, and it still says:

"You are running an insecure kernel (2.4.20-18.7). You should upgrade to a newer version as soon as possible to avoid your system being compromised."

And I check lilo -v -v and it worked fine, and it restarted fine too..

Do you know what could be wrong?...

Thanks in Advance,
Justin.

In the lilo.conf check the
default=
line and make sure it is set to the same label as the new kernel so it will boot by default.

Hello,

I checked it and it was just fine, but when i did lilo -v -v and did get this:

"Fatal: Duplicate label "2.4.20-24.7"

So, once I figure out how to fix that, it should work..

Thanks in Advance,
Justin.

I followed your directions and everything went well. Thanks for the how to!

There are two entries for the 2.4.20-24.7 kernel, or you have the label= the same in the lilo.conf. If its just a duplicate delete it, or renamed it if the name is wrong.

guys

guys

guys

i found the solution

find a proff gut 2 do it 4 u and thats it



bleave me

But where is the adventure in just paying somebody else? I mean don't you enjoy messing up your system and then having to get a restore? haha yea some stuff it is just better to pay somebody, then it helps people like me out

Cpanel is pretty much automated with updates once setup properly but the kernel is something that cannot really be setup to be done automated safely.

for this find a friend to do it

no need to pay

another thing, i like to plaay with my system, not the system that i have business

it will kill me and cost me alot

so,

be away, i will love u more

I am lost, this is my first dedicated server. I did all the shell commands, everything has gone fine. I am unsure as to what to click onto or go to in order to get to the lilo/config option. I have cpanel and it seems that everything I press in webhost manager does not get me to that config option.

great howto, worked more than well. thanks!

I tried everything and it's still telling me You are running an insecure kernel (2.4.20-19.7). You should upgrade to a newer version as soon as possible to avoid your system being compromised.
Could someone please help me...

Thank you,
Nick.

I seem to have finally gotten it, although I made it very hard for myself by doing it through vi.

might want to try using pico next time if you have trouble with VI




Nick - what does your /etc/lilo.conf look like, is the default set to the new kernel and did you run lilo -v -v ?

Thanks for this breakdown!

I just updated to the newest kernel (kernel-2.4.20-28.9) and this tutorial worked perfectly.

Ok I follow directions and finally make changes in lilo... then lilo -v -v give me this error

Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 11 sectors.
Mapping message file /boot/message
Fatal: open /boot/message: No such file or directory
Removed temporary file /boot/map~


I made reboot but still old kernel is comin how can I cope with it?

Thanks... My lilo.conf is


prompt
timeout=50
default=linuxnew
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32

image=/boot/vmlinuz-2.4.20-28.9
label=linuxnew
append="root=/dev/hda2"
read-only
initrd=/boot/initrd-2.4.20-28.9.img

image=/boot/vmlinuz-2.4.20-8
label=linux.bak
initrd=/boot/initrd-2.4.20-8.img
read-only
append="root=LABEL=/"

image=/boot/vmlinuz-2.4.20-20.9
label=linux
append="root=LABEL=/"
read-only
initrd=/boot/initrd-2.4.20-20.9.img


Still running

2.4.20-20.9

Hello Ansolon,
The problem is that you are still using the "default=linuxnew". Replace with: default=vmlinuz-2.4.20-20.9 and this should work.
Ok!

I already use 2.4.20-20.9
But I want to use

2.4.20-28.9

Change to this:

prompt
timeout=50
default=2.4.20-28.9
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
lba32

image=/boot/vmlinuz-2.4.20-28.9
label=linuxnew
append="root=/dev/hda2"
read-only
initrd=/boot/initrd-2.4.20-28.9.img

image=/boot/vmlinuz-2.4.20-8
label=linux.bak
initrd=/boot/initrd-2.4.20-8.img
read-only
append="root=LABEL=/"

image=/boot/vmlinuz-2.4.20-20.9
label=linux
append="root=LABEL=/"
read-only
initrd=/boot/initrd-2.4.20-20.9.img

image=/boot/vmlinuz-2.4.20-28.9
label=linux
append="root=LABEL=/"
read-only
initrd=/boot/initrd-2.4.20-28.9.img

ok what about lilo.conf_ -v -v gives me and error