• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 282
  • Last Modified:

RedHat Enterprise on Proliant ML-370: Kernel Panic Error

Hello,

I am the administrator of some webservers used in a test/develop environment. One of them is causing me many troubles, as it gives me a kernel panic error about once a week.
It is running RedHat enterprise, apache 1.3.29, php 4.3.4, mysql 3.23, on a Compaq Proliant ML-370, Dual Xenon 600, 1024 MB memory, and the os is on a 2x 18 GB scsi raid1.
I don't find anything about the error in the log files, the only thing it shows me is a kernel panic error on the console screen.

Could someone give me some advice, as i am pretty new in the linux world?

If you need more info, just ask.

Regards,
Erik
0
Erikjanssens
Asked:
Erikjanssens
  • 2
  • 2
  • 2
1 Solution
 
paullamhkgCommented:
what's the error messages? if prossible can you post it here.

Also, is it working after reboot?
0
 
ErikjanssensAuthor Commented:
After a hard reboot, everything works fine. I cant give you a detailed error until it happens again. It happened this weekend, but a collegue rebooted it, and didnt noted down error.
0
 
jlevieCommented:
It that copy of RHEL up to with respect to the RedHat errata (as in running up2date and allowing the kernel to be updated)?
0
Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
ErikjanssensAuthor Commented:
Nope, cant connect to the internet with that server.
0
 
jlevieCommented:
Presumably this is a legal copy of RHEL, right?

For RHEL systems that can't connect to the Internet but are legal copies and can be registered with RHN one solution is to use a registered system that is running up2date as a source of the errata. You can tell up2date to save each update that it applies then copy those updates to the "hidden server" and set them up in a yum repository and use yum to do the updates. I have a large collection of RHEL 3.0 workstations and servers in places where the light from the Internet won't reach those systems for 10 thousand years and that's how I keep them up to date. Note that there may be some packages that you'll need on the 'hidden system" that you might not have installed on the exposed system that runs up2date. Those are easily downloaded from your RHN account.

You can read more about Yum and what's involved in setting up a repository at:

http://linux.duke.edu/projects/yum/
--and--
http://www.charlescurley.com/yum.html

My suspicion is that your "weekly panics" may be the result of running the outdated kernel, glibc, etc, that came from the distro CD's. The very first thing to do is to get the errata on the box and see if you still have a problem.
0
 
paullamhkgCommented:
agree with jlevie abt the outdated kernel or the other packages, do an up2date will help. but without the actual error we can only guess. but most likely as jlevie said.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now