We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

locked at login screen OSX server

TonyTech7
TonyTech7 asked
on
Medium Priority
457 Views
Last Modified: 2010-04-29
I have an XServe apple server running OSX server
I have logged in and it is sitting at the login screen "working" for about an hour so far
and I can't quit. it is a production file server so I do not what to restart
Is there a way to quit out or force a quit or force quit from anther osx computer remotely  ?

Thanks....
Comment
Watch Question

Commented:
Working? You mean spinning the beachball? Can you enter a name/pass to login?
Tried command-opt-esc?

Author

Commented:
I have a "Candy cane bar" saying that it is logging in and I can't do anything even command-opt-esc
I thought OSX was crash proof ??? This OSX server ..
I am guessing that there is some process that is hung is there a remote way to see what process is running and kill it ?
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Author

Commented:
SSH ?

Commented:
If you can SSH into your server (from Terminal, type "ssh user@serverip"), try using the command "top -u" to see what process is using the most of your CPU and may be causing the hang.  Also, you may want to try scheduling a restart overnight or at some time when the server is not in use, or not as busy (i.e. "shutdown -r +x", where x is the number of minutes until shutdown... for more info, type "man shutdown").
Have you tried holding down the shift key when loading the OS to boot it into safe mode and then restarting after that?
James LooneySr. Programmer/Analyst

Commented:
Hi Tony,
I have 3 XServes and have had this problem on 1 of them.  I first booted into Single User mode (hold down the S key while booting), this gives you a command line where you can run the file system check (something like /usr/sbin/fsck -y).  Let that run. If it comes back with a message saying that the file system was modified, then run fsck again. Run it until you get a message saying the file system appears Ok. Then type 'exit' to continue the reboot. It may take it a while to reboot if it is doing what mine was doing, but eventually I was able to get in.

As the others said, if you can ssh into the server while it is "logging in", then use 'top' to view all the processes. In the left column of 'top' you will see Process IDs, you can use the IDs to kill any processes you see that are out of control.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.