LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 10-06-2009, 07:56 AM   #1
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,517

Rep: Reputation: 37
Are kernel panics normal at reboot when servers been running for a long time?


I have a bunch of servers that haven't been restarted in over a year. So far every one I've rebooted has had a kernel panic and just sat there during the reboot process until I manually power down and power back up, then it starts normally.

Is that to be expected when a server hasn't been restarted in a long time? Is there a way to make it restart itself gracefully when it has a kernel panic, rather than me hard powering it down?
 
Old 10-06-2009, 08:20 AM   #2
AlucardZero
Senior Member
 
Registered: May 2006
Location: USA
Distribution: Debian
Posts: 4,642

Rep: Reputation: 523Reputation: 523Reputation: 523Reputation: 523Reputation: 523Reputation: 523
It's not normal.
 
Old 10-06-2009, 08:32 AM   #3
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,201
Blog Entries: 3

Rep: Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426
Hi,

No, it's not normal. You should look at the logs in '/var/log' to see if there's anything that will point to the potential problem.
 
Old 10-06-2009, 08:33 AM   #4
i92guboj
Gentoo support team
 
Registered: May 2008
Location: Lucena, Córdoba (Spain)
Distribution: Gentoo
Posts: 4,040

Rep: Reputation: 373Reputation: 373Reputation: 373Reputation: 373
Things that sometimes work, sometimes don't, are usually a symptom of broken hardware. You could start by checking your ram sticks with memtest86.
 
Old 10-06-2009, 08:44 AM   #5
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728
More than once, I have "fixed" a computer by blowing out all the dust, careful vacuuming, and disconnecting and reconnecting all plugs (including the RAM sticks, but NOT the CPU).

Be sure to use static protection methods and other handling precautions. If you have never worked inside electronics equipment, consider getting some help.
 
Old 10-06-2009, 09:29 AM   #6
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,201
Blog Entries: 3

Rep: Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426
Hi,

I agree that regular 'PMS' (preventative maintenance schedule/services) should be performed. You should see some of the systems that I repair that would remain in service if only a good 'PMS' was followed. Some of these systems (fileservers included) are just placed on the floor for convenience and never get touched unless the cleaning persons bumps it. Not the best place to put a system. Even if you place the boxen on a small platform then the dust or dirt will be less.

Cleaning a system properly requires more than just blowing out or vacuuming. Card edges, cabling or other connectors may need attention. One should always follow safety procedures whenever handling electronic devices.
 
Old 10-06-2009, 09:57 AM   #7
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,517

Original Poster
Rep: Reputation: 37
Thanks guys. The servers are actually clean in the dirty sense, not dusty or anything. But what should I look for in the logs to find out what caused the panic?
 
Old 10-06-2009, 02:37 PM   #8
pixellany
LQ Veteran
 
Registered: Nov 2005
Location: Annapolis, MD
Distribution: Arch/XFCE
Posts: 17,802

Rep: Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728Reputation: 728
Quote:
Originally Posted by rjo98 View Post
Thanks guys. The servers are actually clean in the dirty sense, not dusty or anything. But what should I look for in the logs to find out what caused the panic?
Even if everything appears clean, it is completely plausible that there are some bad connections. If there is--e.g.--a bad connection to RAM stick, i'm not sure that you will find that in the logs....

De-mate, inspect, and re-mate all connecters and the RAM sticks.

Also, how about temperature? If you monitor CPU temperature and it is higher than normal, you may have a bad heat-sink interface. happened to me just a few months ago.

At the age of 10 I discovered that I could repair lawnmowers by disassembly and re-assembly----but I never knew WHY.
Now it's the same with computers, but at least I know why........
 
Old 10-06-2009, 03:18 PM   #9
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,517

Original Poster
Rep: Reputation: 37
OK. I rebooted the box again and it actually restarted fine this time, so maybe everything's connected ok and clean and this was just a one time thing?
 
Old 10-06-2009, 04:00 PM   #10
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,201
Blog Entries: 3

Rep: Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426Reputation: 1426
Hi,

Possibly a one time thing but I would certainly not give up on this. As it may be a prelude for things to come. A 'PMS' entails move than just physical cleaning. Filesystem maintenance falls into that realm along with physical checks on connectors, PSU rails and any head cleaning or lens cleaning should be addressed to name a few.

Most system maintenance should be done on a regular schedule. Within that schedule one should setup diagnostic and physical checks to prevent catastrophic problems.
 
Old 10-06-2009, 04:25 PM   #11
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,517

Original Poster
Rep: Reputation: 37
I am planning on e2fsck'ing the entire server next time I restart it, since I'm sure that hasn't been done in forever, I just need to figure out how to make that happen. Unless I'm still missing something, I don't see anything in the log that says why it did that.
 
Old 10-06-2009, 05:05 PM   #12
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Hello together,

what are you looking for in a log-file? While a kernel-panic there will nothing be logged. In my experience it may happen that while booting a failure in the filesystem is detected which can only be fixed when again rebooting.
To help you out in this special case of a kernel-panic I think it would be necessary to know exactly the message on the screen while the kernel-panic.

Markus
 
Old 10-06-2009, 05:07 PM   #13
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,517

Original Poster
Rep: Reputation: 37
The exact message I do not recall. I thought it would have been written to a log file somewhere like everything else in Linux seems to be. Guess I was wrong.
 
Old 10-06-2009, 05:11 PM   #14
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
I think while a kernel-panic (which is at the very beginning of the boot-process) there may be no disk and as well no file accessible to write a log.

Markus
 
Old 10-06-2009, 05:12 PM   #15
rjo98
Senior Member
 
Registered: Jun 2009
Location: US
Distribution: RHEL, CentOS
Posts: 1,517

Original Poster
Rep: Reputation: 37
OK. well I'll pay more attention next time to the lines above the kernel panic message then.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
running any appli tooks a very long time abd_bela Debian 1 09-30-2009 10:53 PM
Can kernel kill long-running process? registering Linux - Kernel 5 07-20-2007 08:45 AM
System time goes twice as fast as normal on FC4 SMP kernel H_TeXMeX_H Linux - Hardware 6 05-20-2006 09:03 PM
rpmbuild rebuild running for long time littauer99 Linux - Newbie 1 11-28-2004 04:37 PM
Kernel Decompress Taking a long time v2-ncl Linux - Laptop and Netbook 0 11-10-2003 08:47 AM


All times are GMT -5. The time now is 09:20 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration