Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Shutting down hung server

Status
Not open for further replies.

dandan123

Technical User
Sep 9, 2005
505
US
I have a server that's hung, I can telnet to the console, but that's dead too. I did a "send break" to the console but that doesn't do anything.

At this point it looks like someone has to actually power cycle it. It's an old E3500, do I have any other options ?
 
Also will I get a crash dump if I power cycle it without doing a sync ?
 
dandan123;

Your are in a tough spot as far as capturing a crash dump.

There are a couple options here.

1) If there is a sun keyboard attached you can have the person try a stop A then type sync enter. The problem with this is the crash dump will basically point to someone doing a stop A. Hangs usually point to a memory leek which may be caused by some program being run or actually bad memory. Someone may be able to analyze the crash dump and give you some pointers. Also Sun has SCAT (Sun crash analysis tool which is a free download from there download site. With this you can see what processes were running and try to figure out things from there.

2) If no keyboard attached have someone plug in a keyboard and it should drop to ok prompt then type sync.

Also hard hangs the stop-A will not work so if it does work then you were not actually hard hung and more investigation is necessary. I can't remember if plugging in the keyboard will drop the system if hard hung. Both the stop-A and unplugging and plugging in are more preferable then just powering off and on as you would still be able to run sync.

Thanks

CA
 
Are you using one of those old school Annex Terminal things? You can power cycle that on and off without effecting the server. It usually hangsup the console connection for that server when you logout improperly.
 
I ended up having someone powercycle it. The terminal server is a Cisco unit. The problem turned out to be on the Cisco side and our networking guys have fixed it so now I have to wait for the next crash.

Thanks for your help coffeesym.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top