Unresponsive Mac - "Stuck Process" the cu…
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
The last few weeks I've had a string of wierd system freezes (about five or six), where I'll be working on something, and then out of the blue everything goes completely unresponsive, the mouse still moves, but everything else is frozen solid and I can't click anything no matter how long I wait.
As a throwback to the old days, the clock even stops entirely. Very reminsicant of Mac OS 9 when you would always hold your breath any time the clock stopped ticking (I thought I was free from the clock watching paranoia).
Twice I was listening to iTunes when this occured and iTunes keeps playing the music, until it got to the end of the song.
I can hear the processors involved in some activity but at a higher pitch than what I'm used to hearing under normal load, and even heavy load, conditions. All the while the fans are rampimp up and down accordingly.
Sometimes the SBOD will emerge....but generally I'm just left with a cursor and forced to do a hard reset. The most frustrating thing is that I have no idea what's causing it.
I decided to try remotely logging in the next time it happens, and run top. Well, I was surprised when I actually could log in, more surprised when I ran top and found that there was no process that was out of control:
http://www.markjenkinson.com/stuckProcess.jpg
If you look at the top, it says that there is "1 stuck" process. Is this what is causing this system hang? Can anyone suggest some help here? Can anyone make heads or tails of this TOP report?
I've noticed that the last three times that this has occured I was manipulating files in the Finder (twice when I was renaming a file, once when I was moving a folder from one location to another)
If there are any others out there who are experiencing the same problem...and have any suggestions...it would be most appreciated.
Thanks in advance.
14 replies
Sign in or join Beachball Help to reply.
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi, Mark
A few thoughts to share:
(1) I'm assuming from your description that although you've suffered intermittent system unresponsiveness you
are able to (force-?) shut down and then startup normally. Correct? If not, please carefully describe any deviant startup behavior.(2) Have you experienced application(s)
quitting unexpectedly or
kernel panics or "only" the system unresponsiveness you've described?(3) I'm relatively new to OS X and can thus only be of help (I hope) in getting you started. As far as I can discern, your
top output simply provides "snapshot" statistics [sorted in default PID order] comparable to what you could see dynamically if you kept Activity Monitor open on your desktop except you don't get the
(not responding) message that helps to determine what process is "hanging." Unless there's a smoking gun you haven't mentioned, you'll need more info to diagnose the gremlins.
(4) As a first step, I think it would be helpful to go to /Applications/Utilites/ and move the Console icon to the Dock, so it's handy. (Same with Activity Monitor, if you haven't already.) Then open Console, click on the "Logs" icon in the top-left-hand corner, open the gray "disclosure triangles" as appropriate, and look through your logs to correlate entries vs. the times when you've experienced these problems. Look first to see if any panic.logs or <application name>.crash.logs have been generated in ~/Library/Logs or /Library/Logs. If not, look in console.log, system.log, and (last ditch) asl.log. (Note that asl.log time is UTC; all others should sync to your local settings.)
ADC documents TN2063:Understanding and Debugging Kernel Panics and TN2123: CrashReporter though pretty technical may provide you with enough of a handle on things to determine what logs/excerpts apply. Also, the Console and Crash Logs chapter in the X Lab's Troubleshooting Mac® OS X has some very useful examples about how to do this.
You may want to post any relevant logs/excerpts here and hopefully, one of the more UNIX-perienced participants can help you to decipher it.
I hope this is a little help...
Good luck!
Dean - 0
Mark Jenkinson ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi Dean,
Thanks for your help. Here's a rundown of my situation in relation to your comments:
1.) You are correct in assuming that startup is normal.
2.) I haven't had any kernel panics or applications unexpectidly quitting
4.) The only thing in Console that happened around the time of the unresponsiveness was an apparent crash of the Dock...which is odd and possibly the culprit. Maybe next time this happens I will try to log in remotely through the terminal and try to kill the Dock process and see if that brings my system back.Thanks for your help, I'll keep you posted.
Mark
- 0
woodsy ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Mark,
The stuck process is not the culprit. The top and ps commands have little time to scan the process table and determine state of processes. Stuck is probably just reporting an indeterminate process state.
From the ps man page:
Since ps cannot run faster than the system and is run as any other scheduled process, the information it displays can never be exact.
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi again, Mark (
et tu, rebar!) See? You've attracted the attention of
rebar: far my superior in all things UNIX. But ya gotta provide grist for the mill. . .
(A) (1), (2) good news; (buckle-my-shoe) I'm a little confused:
]"<small>The only thing in Console that happened around the time of the unresponsiveness was an apparent crash of the Dock...which is odd and possibly the culprit. Maybe next time this happens I will try to log in remotely through the terminal and try to kill the Dock process and see if that brings my system back.</small>"
Apparent ? Usually if there's in fact been a "crash," console.log &/or system.log would say quite clearly something like: "<small>crash report written to: /Library/Logs/CrashReporter/Dock.crash.log</small>," and a crash.log would be available there. And normally, in the event of the Dock quitting its parent (loginwindow) should automatically relaunch the Dock. [Aside: If you follow the link, please see the final ¶ under "Configuring User Sessions."] All this would (presumably) be logged. See my confusion?
And because loginwindow should relaunch the Dock automatically in the event it unexpectedly quits (as should launchd relaunch loginwindow, if needed) is the issue really limited to the Dock? Do you, perchance, have any system-altering 3rd-party software in the Dock or menu extras that might be behaving mischievously or otherwise incompatibly?
(B) If I may channel Wilson Pickett for a moment: perhaps "the Midnight Hour" seduced me into myopia or tunnel vision. Sorry. Stepping back to gain some perspective have you completed "standard troubleshooting stuff" to isolate and confirm that this is definitely software-related? Have you tried to recreate the "hang" behavior using a test user account?
Though these steps may seem rudimentary, the slow-and-steady approach is usually best in troubleshooting no matter what intuition may suggest. . .
Looking forward to hearing back from you.
Good luck!
Dean - 0
Mark Jenkinson ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi rebar,
Thanks for your input. I guess this raises the question that if the "stuck process" is nothing to worry about, then what's causing this complete system unresponsiveness? What a baffling situation. Even more baffling is the fact that the problem only rears it's ugly head every so often and hasn't happened since my last report.
More often or not it occurs when I'm pushing the machine to it's limits. Sure it's got 2.5 GB of RAM but that is quickly exhausted when I'm running Photoshop, Illustrator, InDesign, Entourage, Word etc... I wonder if this is a clue as to what the problem is?
I find it odd that it's not a kernel panic, and that I can SSH into the unresponsive mac and run top with the appearance of no problems and everything running as normal, and yet there's nothing normal about the apparent frozen state that the computer is in.
Thanks for your help, I'll keep you posted.
Mark
- 0
Mark Jenkinson ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi Dean,
Sorry for the confusion. I termed the crash of the Dock as an "apparent" because as I was looking through my Console logs I noticed that there was a recorded crash of the Dock around the time (roughly) of the system freeze up. This was the only indicator that the Dock crashed though (hence the "apparent") as the screen was frozen (except for the cursor) and I never actually witnessed the Dock crashing and re-spawning...as it normally does when it crashes.
I've got no third part dock hacks, or any system hacks at all for that matter.
Interestingly enough, the last time this system freeze-up occurred, I had just created a "test" user account and was just about to switch users to play around and see if the problem persisted in the test user account. Since that freeze-up, the problem has not resurfaced, under the main user account or the test user account. Really bizarre,
In regards to "standard troubleshooting" stuff, I've run Disk Utility, I've run DiskWarrior, TechToolPro, repaired permissions, cleaned caches, rebooted safe-mode, etc...
Thanks for your willingness to help,
Mark
- 0
Kevin Taggart ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I am having the exact same problem: the UI freezes, but the mouse is still active, with intermittent spinner and pointer activity.
Connecting via ssh from another box and running top does show a consistent stuck thread. Alternatly, if I just run top on the local system (or ssh into the problem child and run top), I see intermittent/infrequent stuck thread msgs, but when the UI freezes, the stuck thread msg becomes constant.
The only option is to hard reboot.
I have run every diag I have, and I can find no problems with the hardware.
In fact, I reinstalled the OS and applied all the patches and I still get the freezes.
The really intersting thing about this error, is that prior to last week, it had never happened before. I did not make any changes to my system during that period.
I am running 10.4.2 w/no 3rd party hacks at all - this is a production system.
The crash logs really give no clue as to what the issue is.
After reinstalling the OS/patches, the system ran for approximately 24hrs before it started freezing again. Once the freeze occurs, the system becomes unusually unstable during subsequent attempts at restarting, often times freezing within a few seconds of startup.
It gets worse from there. The last time I got to a desktop, the system froze half way through rendering the dock (literally, the dock was half drawn on the screen when the sys froze).
Now, the system only boots to a blue screen, no mouse pointer.
I can boot into single user mode, and poke around/view the logs, but after a short time, the text on the screen starts doing "the Matrix" where the screen becomes full of text fragments as the screen is not refreshing properly.
I can boot from the Mac OS X install disc and run the various tools all day long w/o any issues, and can also boot from techtool and disk warrior w/o issue - no freezes while an tool/diag is running.
As soon as I reboot into the OS, system freeze and/or blue screen.
My next effort is to reinstall the OS and upgrade it to 10.4.1 and see what happens.
We have five Mac's in the house, all of which are running 10.4.2 - two of these systems are experience serious reliability problems (the other, also a G4, is getting numerous kp's and I/O errors, freezes, etc.) All the G3 systems are running without issue - it's just the G4's that are bombing.
-k
- 0
Mark Jenkinson ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi Kevin,
I wish I could help you. My crashing problem has mysteriously disappeared, and I don't really know what fixed it. My last crash occurred, just before my last post in this thread, (Oct 12). The only thing I did around that time was uninstal TechTool Pro. I've read on numerous sites that TTP4 causes slow downs and hiccups on some systems and thought uninstalling it was worth a shot. But I can't really say whether or not this was what fixed things, but that's the only thing that I did that was of any significance, aside from the normal repairing permissions, Disk Utility, DiskWarrior etc....
Let us know if you have any success,
Mark
- 0
Kevin Taggart ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Well, I do have TTP installed, maybe that needs to go?
I just started my PM up after being powered off since yesterday, and it came right up. As it sat yesterday, I could not even get to the desktop.
I have also been looking into the various lookupd issues being discussed throughout the board.
While I never visit fox news web sit, there may be some other issues with lookupd that are causing the freezes.
Thanks for the reply!
-k
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi, Kevin and Mark
Mark: do you think this is evidence that
"it's better to be lucky than good?"Kevin: I've just spied your posts and haven't had much chance to think about them yet. More later.
For now a couple of thoughts.
(1) I'm not sure what you mean by "
The crash logs really give no clue as to what the issue is." There's no panic.log? It certainly sounds as if one or more of your Macs is experiencing kernel panics so there should be panic.logs to provide a means to trace exceptions.
I profess to no particular expertise in this regard, but from what I think you're saying, I'd suggest that you:
(a) Initiate a new thread about this. (And, if you do, please include a link back here, for those of us who've "subscribed to" this thread.)
(b) Post representative, recent excerpts from your panic.log.
It'd probably be best to stick with one Mac at a time for diagnostics unless you can isolate and describe something ~unusual that correlates strongly among your Macs.
(2) What's your reason for the hypopthesis that lookupd may be involved? Have you noticed it "hanging" chronically in Activity Monitor or in your system.log, console.log, etc.?
If you're correct in thinking that the "lookupd phenomenon" is involved, there may be a lookupd.crash.log but in /Library/Logs/CrashReporter rather than in ~/Library/Logs/ where you'd usually look. Unfortunately, when lookupd "hangs," crashdump is also affected sometimes resulting in nothing meaningful being logged.
Since you mention you've been "looking into" the lookupd process issues, have you read through this thread: <small> David Campbell5, "Update on lookupd" #5, Sep 30, 2005</small> <big></big>?
(3) I've noticed a couple of other processes that folks have identified as "hanging" their systems since OS X 10.4 Tiger was first released:
] mdimport related to Spotlight indexing
] update "helps protect the integrity of disk volumes by flushing volatile cached filesystem data to disk at thirty second intervals," and can sometimes get "stuck" doing so. Look for repeating log entries like "<small>hotfiles_evict: err 28 relocating file yyyyy</small>" as a way to identify the latter.
Might either of these be involved?
That's all for now. . .
Good luck!
Dean - 0
Kevin Taggart ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks for the response.
The reason I stated the logs don't tell me much is because on the main system in question, the system never crashes (no kp's on this particular system) per se, the finder/entire UI freezes.
The reason I suspect lookupd is precisely because I have read the thread (and other similar threads) that you referenced.
The console logs and crashreporter logs show no common culprits.
I will read the mdimport and update threads as well, as I noticed mdimport as being noted in the console logs.
Thanks,
-k
- 0
Dean Pahl ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi again, Kevin
Understood.
In re: mdimport, we can discuss this further if you'd like I tried to ~keep track of the topic during the last 6 months. Although I haven't looked recently, I'm sure there are still plenty of threads (here in Using Mac OS X 10.4 Tiger and in the
Spotlight forum, etc.) about
"slow-downs" due to indexing whether mdimport is specifically identified or not...Fwiw >
Based on referral from MacFixIt, I've just read that
Tiger Cache Cleaner has been updated to version 3.0.5 for (among other things) OS X 10.4.3 compatibility. According to
versiontracker:"
What's new in this version:
This release of Tiger Cache Cleaner adds the ability to optimize some settings of the lookupd daemon.
It adds the ability to flush the lookupd cache.
It adds the ability to restart the lookupd daemon.
It adds the ability to check the SMART status of connected drives.
This release adds the ability to check and report the status of laptop batteries.
This release adds a System Information tab to the application which reports some relevant system statistics."Since I own and sometimes use TCC, I downloaded the updated version. From p. 21 of the TCC 3.0.5 user's manual, the "lookupd optimization" involves:
"<small>niutil -create . /locations/lookupd/hosts
niutil -createprop . /locations/lookupd MaxThreads 256
niutil -createprop . /locations/lookupd/hosts TimeToLive 300
niutil -createprop . /locations/lookupd/hosts ValidateCache NO
niutil -createprop . /locations/lookupd/hosts LookupOrder
CacheAgent FFAgent DNSAgent NIAgent DSAgent NILAgent
niutil -create . /locations/lookupd/agents/NILAgent
niutil -createprop . /locations/lookupd/agents/NILAgent
TimeToLive 60 </small>"I can't say, of course whether this is relevant or may be helpful just letting you know since we're on the topic.
Regards,
Dean - 0
Kevin Taggart ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Well, I am clueless.
After starting up my system this morning (it had been off overnight as it wouldn't even boot to desktop), it had been working all day.
System locked up (UI only), I ssh'd in and killall'd lookupd to no avail.
Rebooted (hard reset), ran fsck, booted to the desktop, and within a few seconds another freeze.
Rebooted.
Froze immediately after loading the dock.
Rebooted.
Blue screen, no mouse pointer.
Powered off.
This machine has been working well for the longest time, and now I cannot even use it to get any work done at all.
-k
- 0
Carlos Perla ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I am having the same problem. I believe that it is a product of a bad update. I might have skipped verifying it. i was updating from 10.3.5 to 10.3.9 and now i'm stuck! Is there any way to boot from an update?
Thanx