On Tue, April 19, 2005 11:36 am, IT Support NZ said: > >I have searched and found no cause for horse to go belly up last week. >> >>Evidence included >> A load average of 15-16 >> A number of processes in state D, including a bunch of >>apt-extracttemplate processes >> Giving a reboot command from remote hung the machine. >> >>I recently configured horse to get packages from an apt-proxy server >> wehich >>entailed allowing port 9999 through the firewall to my own server. I >> doubt >>that caused the problem though. >> >>Any idea? > A load average of 15-16? Shouldn't there be a decimal place in that > somewhere? e.g. Load average of 0.15 to 0.16? > > If memory serves me well and you are using the same load average stats I > do then that figure indicates you have 15 to 16 processes waiting on > average per CPU. No wonder it went belly up. No, not per cpu. In total. And it's the sum of those running and runnable. However, some versions of top do very strange things with this number.
As this is a multi-cpu box (IIRC), then this is extremely high, but not unexpected if there's any java running (: > > What was your top process in terms of cpu usage? Is it apt-getting stuff > and trying to compile? As apt-get doesn't compile without the --source --compile flags. Not ones you often use on an older machine when you don't have to? > > Shane > > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.308 / Virus Database: 266.9.15 - Release Date: 16/04/2005 > > $0.02 Steve -- Windows: Where do you want to go today? MacOS: Where do you want to be tomorrow? Linux: Are you coming or what?
