Memory: 479488k/491456k available (1706k kernel code, 9408k reserved, 328k data, 304k init, 0k highmem)
Linux xxxx.xxxxhosting.com 2.4.24-ow5 #2 SMP Fri Feb 20 02:06:39 EST 2004 i686 athlon i386 GNU/Linux
hda: WDC WD800BB-00FRA0, ATA DISK drive
hdc: WDC WD800BB-00FRA0, ATA DISK drive
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=9729/255/63
Sat. I upgraded my OS and Kernel following these instructions.
The first step is to register the system with redhat and sign-up for the update. This needs to be done only once for one server.
Login as root and give the command:
This will ask you a couple of questions, which you need to answer. At a point, you need to enter a username, password and an email-address. Just think of a unique username, password and enter your email address, and continue with the rest of the questions. At the final state, it will send the profile to Redhat Network.
The second step is to configure the command to update the system. After that, you just need to run this command and update your system to the latest.
Let us first configure the options.
as root, enter the command:
select number for "removeSkipList" ENTER
select number for "pkgSkipList" ENTER
What the above command does is it will remove "kernel" from the skip package list, and hence, everything, including the kernel can now be upgraded automatically. Unless you are using raid or dual cpu's or a custom-made kernel, upgrading the kernel via up2date is the recommended method.
Ever since my server has been crippled by one thing or another. First Perl was corrupted, killing exim stats. Perl had to be re-installed. Then cpanel was jacked up. When Perl was re-installed it fixed these problems. Then the CGI counter scripts quit working, The images were gone.
I was getting this eror from within ssh:
/usr/sbin/httpd restart: httpd not running, trying to start
Syntax error on line 499 of /usr/local/apache/conf/httpd.conf:
Can't locate Digest/MD5.pm in @INC (@INC contains: /usr/lib/perl5/5.8.1/i686-linux /usr/lib/perl5/5.8.1 /usr/lib/perl5/site_perl/5.8.1/i686-linux /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl . /usr/local/apache/ /usr/local/apache/lib/perl) at /usr/lib/perl5/site_perl/5.8.1/Apache/ASP.pm line 13.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.8.1/Apache/ASP.pm line 13.
Compilation failed in require at (eval 3) line 3.
/usr/sbin/httpd restart: httpd could not be started
Finally the DC admin decided it was a perl module in the httpd_config file that was causing the problem. I told him what I had done and asked him to check everything out. He said the Kernel was fine.
How ever I got this in my logwatch this morning:
--------------------- Kernel Begin ------------------------
WARNING: Kernel Errors Present
Error: only one proces...: 2Time(s)
Dropped 28 packets on interface eth0
From 126.96.36.199 - 16 packets
To 188.8.131.52 - 16 packets
Service: 8002 (tcp/8002) (** IN_TCP DROP **,eth0,none) - 9 packets
Service: 8003 (tcp/8003) (** IN_TCP DROP **,eth0,none) - 7 packets
From 184.108.40.206 - 12 packets
To 220.127.116.11 - 12 packets
Service: 8002 (tcp/8002) (** IN_TCP DROP **,eth0,none) - 12 packets
They could be an indicator of one of two things that I know of. Some WH HDDs go to "sleep" after x amount of time of inactivity. There's a firmware upgrade for it, I cannot find the actual URL. Contact me if you'd like a copy of the patch. Anyway, the drive goes to sleep after some inactivity is reached, and the system tries to queue the device but it seems as if it doesn't exist. I've only known this to happen on WD 120G drives. This is NOT the same "sleep mode" as one would set in the BIOS.
Second reason is an indicator of a failing drive. Does this activity go away after some time? Does it clear after you unplug the computer for 2+ minutes, and turn it back on? A quick test for this is to do a soft reset of the computer, and see if the drive shows up upon reboot, in the POST screen. By doing this, you do not reset the drive itself, so it will remain in a "sleep mode". Hope that helps.