I've got a Mac fileserver that isn't acting right (and was acting strangely yesterday as well). I set up an audible ping to it, and
sshed into it and, as root, issued the
reboot command. It did nothing! I
sshed in again and issues another reboot command, and still nothing.
It is bizarre seeing 'reboot' listed as one of the tasks in
Then, as root, I issued a
shutdown -r now
It alerted all users that the system was going down ... and it didn't go down. (I can't establish a new ssh connection, but I did leave myself one open with root access.)
I've never seen anything like this. What could prevent a system from rebooting, and more to the point, without accessing the box physically (I can, it is just at another location), how can I bring the box down?
I notice now that
Processes: 25 total, 2 running, 4 stuck, 19 sleeping... 88 threads
I've never seen stuck processes either. (And one of my friends was just telling me that only on Unix can you have sleeping zombie children.)
From this thread (esp. post #9), I take is that
top will show a 'U' for stuck ("uninterruptible") processes.
bash-3.2# ps ax | grep U 48 ?? Us 0:08.23 /usr/sbin/update 10180 ?? U 0:32.95 /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/build_hd_index 17119 s000 U+ 0:00.07 reboot 17052 s001 U+ 0:00.09 reboot 17261 s002 R+ 0:00.00 grep U
kill -9 [pid] has no effect.