Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 443
  • Last Modified:

Red Hat 6.1 Linux Hangs (full details below)

This is a new install
Red Hat 6.1
I have installed red hat 6.1, if for example the computer is turned off, then i go and turn it on, it will boot into the OS, with No problems, I can go and ping it from a client workstation, Netscape server, and ftp deamon and connect
to it from any other client workstation, and I can telnet into just fine. Everything works fine. Ok now if i go away for 10 hours and dont touch the server, When i come back, the screen on the monitor goes black, but the light on the monitor is green not yellow. the power light on the computer is green, you can here the fans inside the computer, power seems to be going through, but if i go to the servers keyboard and press any button. That action produces no effects, the screen still stays black, and nothing happens.
If i go to a client workstation and try to ping the server i get request times out, i am pinging it by the ip address and by the host name, If i go try to connect via ftp or telnet i get the same results, that i cannot connect to the server. Now if i go and hit the reset button on the server, and wait until it reboots, It comes up and says that the file systems where not unmounted properly and forces a check, The system boots fine after the check, i can go and use it do what ever i need to do everything is fine, then the whole process repeats itself, if i do not touch the computer physically for a couple of hours. I dont know what is causing this, but i assumed that it was going into some power saving mode and just not waking up from it, i checked one of the utilities in KDE for power management , and it doesnt seem to be set up for power management. Is there anything that i can check or do to prevent it from going into this hung state?

Thanks in advance
0
klute
Asked:
klute
  • 5
  • 4
1 Solution
 
jlevieCommented:
Have you disabled power management in the bios?
0
 
mjn020200Commented:
It seems to be that you are having problem with your bios APM and the daemon. May we know what kind of hardware we are using?? notebook or desktop.
0
 
kluteAuthor Commented:
there is no power management feature for this mother board, the comp is a generic server, with an intel server board, the bios is phoenix bios.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
jlevieCommented:
Oh well, APM would have been the easiest to diagnose & fix and if the bios has that feature & it's enabled it can cause a lock up.

Look in /var/log messages and see if anything is being logged prior the the lock up.
0
 
kluteAuthor Commented:
this is where i currently stand with this issue, The last time it locked up i came to the keyboard started pressing the num lock or cap lock (to see if the light would light up) the green light did not light up. then i tried pressing ctrl + alt + f1 f2 etc, i tried ctrl + alt + backspace, none of these actions produced any results, i hit the reset button and walked away, at the time there was a dos disk and just booted into dos, when i came back several hours later the screen was not black and i could type things on the keyboard, So i guess that goes to show that the Power managenemt is not turned on in the bios, its probebly some power setting within linux, in all honesty i really dont jknow what else to check or even where to start looking,
thanks in advance
0
 
jlevieCommented:
Having DOS stay running isn't relevant as it doesn't support APM and won't go in to powersaving mode regardless of what the bios does.

Power management in Linux is controlled by apmd, but I've only ever seen it set up to run by default except on laptops. If you want to see if it's running, do "ps -ef | fgrep apm | fgrep -v fgrep".

If apmd isn't running, then the kernel isn't responding to APM signals from the bios. Which leads to the next most likey problem... Something is hosing up and locking or crashing the Kernel. Done in the right (or wrong depending on you viewpoint) way there may not be anything visible on the console, especially if it had "blanked" from inactivity. Have you looked in the logs (/var/log/messages) for any errors just before the reboot messages?

To help find the problem, don't log in to KDE. If the system is set up for graphical login, use the ctrl-alt-F1 hotkey to get to a console and log in there. You might then see a panic message from the kernel or some other error as it locks up.
0
 
kluteAuthor Commented:
Thanks,
After much trial and error, i finally figured out what the problem was,
It turned out to be hardware issue,
there was tape drive that was not terminted properly, I guess it was locking up and it was doing it every time it tries to initilaize the tape drive. At anyrate i removed the tape drive and it doesnt lock up anymore..


Thanks for all the help

0
 
jlevieCommented:
Well, I should have thought to ask, as an improperly terminated SCSI bus can cause some of the most mysterious problems. Most of the time, there are lots of other clues that point to a SCSI bus problem. System crashes when the I/O load is high, like when booting or starting X, come readily to mind.

The bus must have been at least partially terminated or you'd have known about it before. Ahh well, at least you found it. What do you want to do with the question?
0
 
kluteAuthor Commented:
As far as the question, i dont know what to do, i will just give you the points i guess, you gave me a lot of ideas that pointed me in the right direction.

Thanks
0
 
jlevieCommented:
Okay, that works for me.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

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