Re: How do I find the cause when OSX locks up?
Re: How do I find the cause when OSX locks up?
- Subject: Re: How do I find the cause when OSX locks up?
- From: Anton Kuzmin <email@hidden>
- Date: Fri, 04 Mar 2005 13:13:51 +0000
It does not seem to be a problem with lookupd (or at least it's not just
lookupd on it's own).
Normally, when lookupd locks up, the UI remains responsive, but in this
case the whole UI (except the mouse cursor) locks up as well - as if the
window server hung up. But seems to be somewhere deeper in the system,
as it looks that every other process hangs up too. But not the kernel
itself - as I can ping this computer and establish tcp connections.
Anton
have you tried disabling crashreporter? /etc/hostconfig
sounds like you're running into the lookupd lock-up problem. Google
for more info. :)
I'm experiencing a very strange problem on 10.3.8 with one of our own
proxies (smtp/pop3 proxy) - from time to time (once or twice a day),
the whole system locks up - I can move the mouse cursor, but
everything else becomes completely unresponsive, all
applications(even daemons) freeze, but I can ping this computer while
it's locked up, and if I try to connect to any standard service (like
ftp or ssh) - the tcp connection can be established instantly but no
data is ever received by the client (i.e. ftp server prompt). I've
tried to run a simple script on this computer that logs top and
zprint output every second into a file, and the data from the script
shows no apparent anomalies in memory usage just before the computer
locks up. Sometimes it unlocks itself after a random amount of time
(can be from 20 seconds to a few hours) in which case the top output
shows crazy cpu usage percentages for different processes, which
total at up to 700-1000% (which could be just a problem with top
getting confused by the lock up).
Are there any other monitoring utilities except top and zprint that I
can use to figure out what's going on?
I tried the same configuration on another computer and it's the same
problem again, which, I think, rules out possible hardware problems.
Any insight on what other resources(or lack thereof) can cause this
behavior and how to monitor them would be very helpful.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden