I have CentOs, as mentioned, and now i want to upgrade kernel.

I went in SSH and did this:

# yum update kernel

and got this:

Setting up Update Process
Setting up repositories
update 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
addons 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
Excluding Packages in global exclude list
Finished
Could not find update match for kernel
No Packages marked for Update/Obsoletion

as far as i can see it says that he couldn't update it. is that so?
i am going to restart server now, just in case, but if that is not updated, what am i to do to make it updated?

note that i am a newbie

It probably already is updated, if you are running an old kernel check the /etc/grub.conf, the default= may be set to the old kernel. It also may be you simply have not rebooted to have it take affect.

Greetings:

For yum, also check /etc/yum.conf to make sure you do not have an exclude line that includes kernel or kernel*

Thank you.

well, as Jeff instructed i sshed and typed: uname -a. this result:

"Linux new.server-ns1.com 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 26 14:30:58 EDT 2007 i686 i686 i386 GNU/Linux"

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg. console=tty0 console=ttyS0,9600n8
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda7 console=tty0 console=ttyS0,9600n8
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
serial --unit=0 --speed=9600 -word=8 --parity=no --stop=1
terminal --timeout=2 serial console
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS-4 i386 (2.6.9-34.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.ELsmp ro root=LABEL=/ console=tty0 console=ttyS0,9600n8
initrd /initrd-2.6.9-34.ELsmp.img
title CentOS-4 i386-up (2.6.9-34.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.EL ro root=LABEL=/ console=tty0 console=ttyS0,9600n8
initrd /initrd-2.6.9-34.EL.img

theres another copy in /boot/grub/grub.conf

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda7
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.9-55.0.6.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.6.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-55.0.6.ELsmp.img
title CentOS (2.6.9-55.0.6.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.6.EL ro root=LABEL=/
initrd /initrd-2.6.9-55.0.6.EL.img
title CentOS (2.6.9-55.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.2.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-55.0.2.ELsmp.img
title CentOS (2.6.9-55.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.2.EL ro root=LABEL=/
initrd /initrd-2.6.9-55.0.2.EL.img
title CentOS (2.6.9-55.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.EL ro root=LABEL=/
initrd /initrd-2.6.9-55.EL.img
title CentOS (2.6.9-55.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-55.ELsmp.img
title CentOS (2.6.9-42.0.10.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.10.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-42.0.10.ELsmp.img
title CentOS (2.6.9-42.0.10.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.10.EL ro root=LABEL=/
initrd /initrd-2.6.9-42.0.10.EL.img
title CentOS (2.6.9-42.0.8.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.8.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-42.0.8.ELsmp.img
title CentOS (2.6.9-42.0.8.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.8.EL ro root=LABEL=/
initrd /initrd-2.6.9-42.0.8.EL.img
title CentOS (2.6.9-42.0.3.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-42.0.3.ELsmp.img
title CentOS (2.6.9-42.0.3.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.EL ro root=LABEL=/
initrd /initrd-2.6.9-42.0.3.EL.img
title CentOS (2.6.9-34.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.0.2.EL ro root=LABEL=/
initrd /initrd-2.6.9-34.0.2.EL.img
title CentOS (2.6.9-34.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.0.2.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-34.0.2.ELsmp.img
title CentOS-4 i386 (2.6.9-34.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.ELsmp ro root=LABEL=/
initrd /initrd-2.6.9-34.ELsmp.img
title CentOS-4 i386-up (2.6.9-34.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-34.EL ro root=LABEL=/
initrd /initrd-2.6.9-34.EL.img

You have the latest kernel installed, simply reboot and you will boot to it.

i agree with eth0

ok
thx

still i have some overload issue on server.
i suspect on one forum that is very busy and almost always is using the most.
this is my configuration:
Server P4 2.8GHz ValueLine
RAM 512 MB RAM

and this is usage:
%CPU %MEM MySQL Processes
11.76 31.19 1.2

it is the first, and this is on the good day.
i suspect mysql going into overload becouse forums don't work, while some simple pages do.
and it always goes into overload at the busiest hours almost every day.

also, i saw somewhere that one of HDD partions shouldn't be over 80%. Now, i cannot find that topic.
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 1012M 744M 217M 78% /
/dev/sda1 99M 50M 45M 53% /boot
none 244M 0 244M 0% / dev/shm
/dev/sda5 54G 4.8G 47G 10% /home
/dev/sda6 1012M 34M 927M 4% /tmp
/dev/sda2 9.9G 3.1G 6.4G 33% /usr
/dev/sda3 6.9G 749M 5.9G 12% /var
/tmp 1012M 34M 927M 4% /var/tmp

any tips?

Upgrading the kernel was not going to help much with performance issues.

Paste the output of top (the very top part and a few processes) as well as free -m here, that will help see what the limit is.

i'll try to do it tonight when it will probably go into overload, but problem is that everything is slow then. even ssh...

i have attached data becouse in post it isn't clear.. this is from midday...

Next time post the uppermost part of "top" as well. It is best to post it when it is overloaded.

now the server wont go into overload!!! ARGH!

not that i complain but still i think that problem is out there... as soon as i catch it in overload i'll post here.

well it started again and here is "top" in attachment...

after reboot i got this email from statscheck] Stats/Server Overload on new.server-ns1.com:
IMPORTANT: Do not ignore this email.
This is cPanel stats runner on new.server-ns1.com!
While processing the log files for user ivofan, the cpu has been maxed out for more than a 6 hour period. The current load/uptime line on the server at the time of this email is
21:36:05 up 8 days, 25 min, 0 users, load average: 60.03, 47.21, 34.79
You should check the server to see why the load is so high and take steps to lower the load. If you want stats to continue to run even with a high load; Edit /var/cpanel/cpanel.config and change extracpus to a number larger then 0 (run /usr/local/cpanel/startup afterwards to pickup the changes).

I did as it said: i changed "extracpus" from 0 to 2. and then i ran /usr/local/cpanel/startup.

also, i have just checked my settings:
"the load average above the number of cpus at which logs file processing should be suspended (default 0):" is at default. should i change that, and into what?

recently i have enabled logwatch and every day, and sometimes few times a day, i receive this:
--------------------- Kernel Begin ------------------------


Logged 2 packets on interface eth0
From 59.176.43.188 - 1 packet
To 74.52.77.170 - 1 packet
Service: 50055 (tcp/50055) (** RABHIT **,eth0,none) - 1 packet
From 82.50.216.122 - 1 packet
To 74.52.77.170 - 1 packet
Service: 50109 (tcp/50109) (** RABHIT **,eth0,none) - 1 packet

87 Time(s): [<c011ae6d>] do_page_fault+0x0/0x5c6
95 Time(s): [<c012052d>] autoremove_wake_function+0x0/0x2d
96 Time(s): [<c0126934>] current_fs_time+0x44/0x4c
96 Time(s): [<c0142517>] generic_file_buffered_write+0x41f/0x501
96 Time(s): [<c0142982>] __generic_file_aio_write_nolock+0x389/0x3b7
96 Time(s): [<c01429e9>] generic_file_aio_write_nolock+0x39/0x7f
95 Time(s): [<c0142bd3>] generic_file_aio_write+0x72/0xc6
1 Time(s): [<c0142bd3>] generic_file_aio_write+0xb/0x1a7
96 Time(s): [<c014524f>] balance_dirty_pages+0x7c/0x11c
95 Time(s): [<c015b5b8>] do_sync_write+0x9e/0xcb
96 Time(s): [<c016942b>] sys_rmdir+0xaa/0xf4
95 Time(s): [<c016fc97>] dput+0x17b/0x1a7
95 Time(s): [<c0172440>] generic_delete_inode+0xa2/0x104
95 Time(s): [<c0172623>] iput+0x5f/0x61
80 Time(s): [<c0177df8>] __mark_inode_dirty+0x28/0x176
10 Time(s): [<c0177eb2>] __mark_inode_dirty+0xe2/0x176
96 Time(s): [<c0177f76>] write_inode+0x30/0x37
96 Time(s): [<c0177fed>] __sync_single_inode+0x70/0x1bb
96 Time(s): [<c0178399>] sync_sb_inodes+0x1a7/0x274
96 Time(s): [<c01784f7>] writeback_inodes+0x91/0xde
95 Time(s): [<c0183077>] dquot_commit+0xa2/0xf4
95 Time(s): [<c0183642>] dqput+0xdd/0x159
95 Time(s): [<c0184086>] dquot_drop+0x4c/0x80
95 Time(s): [<c0186103>] v2_write_dquot+0xe8/0x128
2 Time(s): [<c0226d69>] __make_request+0x421/0x46c
2 Time(s): [<c0226d9a>] __make_request+0x452/0x46c
92 Time(s): [<c02d007b>] unix_dgram_sendmsg+0x23c/0x45d
96 Time(s): [<c02d64db>] syscall_call+0x7/0xb
95 Time(s): [<df834cdb>] do_get_write_access+0x516/0x532 [jbd]
95 Time(s): [<df926d9e>] ext3_file_write+0x19/0x8b [ext3]
95 Time(s): [<df927003>] ext3_free_inode+0xf4/0x31b [ext3]
95 Time(s): [<df927f35>] ext3_delete_inode+0x0/0xaa [ext3]
95 Time(s): [<df927fc8>] ext3_delete_inode+0x93/0xaa [ext3]
96 Time(s): [<df928f7d>] ext3_ordered_commit_write+0xb6/0xc5 [ext3]
96 Time(s): [<df92ac72>] ext3_write_inode+0x22/0x3f [ext3]
95 Time(s): [<df92aedc>] ext3_mark_iloc_dirty+0x10/0x18 [ext3]
95 Time(s): [<df92af9f>] ext3_mark_inode_dirty+0x3a/0x41 [ext3]
90 Time(s): [<df92e832>] __ext3_journal_stop+0x19/0x34 [ext3]
95 Time(s): [<df930d9a>] ext3_dquot_drop+0x25/0x3b [ext3]
95 Time(s): [<df930de9>] ext3_write_dquot+0x39/0x4f [ext3]

---------------------- Kernel End -------------------------

what is that i should be keeping an eye at this watchlog reports?