Sun, Solaris , 8, Console hangs for a long time. All else seems to work

Solaris system went down.  Brought system back up and was able to fsck the system.  

If you try to access the system by console the system just hangs.   Other than that the system works fine.  This is a system we have limited access to and I can not give great details on the system.  I just need a "to do" list of things to check.  

I do not belive we can  ever get to the console, I just hangs for hours.  
Who is Participating?
When you say "Other than that the system works fine." I wonder what you mean?

What does this server do?  Webserver, database?

Can you telnet or ssh into it?

My first guess is that there is a missing file system that is included in the path of whoever is logging into the console.  This is common, when a system is brought back after a crash.  It is likely that the fsck wasn't complete and a file system wasn't mounted.

That is why I was concerned about the working fine comment.  It may only seem to be working fine, and is not preforming some function that it normally does, or is preforming it improperly.

Also, the reason for the crash is important.  

From your description, it is likely that it crashed because a disk partition filled up.  Suns do not like that if it is root, and they will crash.  

df -lk

this will show all the mounted partitions and their space usage.  If any are close to 100% then that could be your problem.  

It is also likely that /var filled up because a crash does a core dump and most people have an inadequate /var space.  

itguy411Author Commented:
Good reply.   I will check

We can telnet and ssh into it.  

It is a system that runs a very large java app.  

Thank you. !!
Hanno P.S.IT Consultant and Infrastructure ArchitectCommented:
When you access the console, do you see anything?
What happens, when you press "Enter" (or "Return")? Does the cursor go down to the next line?
Get your problem seen by more experts

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

itguy411Author Commented:
Now the system crashes.  I found the same problem on the web except they did not give the solution:  

Our place is a little touchy about information so I will send you the URL to the other guy's issuse, exact same as mine.   FSCK did not resolve this issue and the system crashes often:

I'd guess that some electrical connection like SCSI or RAM got loose inside server.
This sounds like exactly what I mentioned, something is wrong with your /var file system. Here is how to check it.

First, make sure that you have done what I suggested before, running df -lk to see if any of the file systems are full

Boot the system in single user mode, by typing boot -s at the ok prompt.  (This will also work if the system is stuck in single user mode.)

once you are in, you should examine the entries in /etc/vfstab compare those entries to the df -lk that you did.  If there is a file system missing from the df -lk , such as /var then there is the problem.

The fix could be as easy as fsck /var or as tough as a bad disk that has to be replaced.  If you don't know how to read those, you can post them here and we can give you advice.  (The layout of you file system is not something that could lead to a security breech.)

I'd suggest checking cable connections because of sporadic crashes.
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.

All Courses

From novice to tech pro — start learning today.