« Return to Thread: AFP eating up CPU

Re: AFP eating up CPU

by Anders Pihl :: Rate this Message:

Reply to Author | View in Thread

I had this problem and in my case it was the clients time settings  
that was the problem.
In a lot of clients the clock was wrong. I changed the time settings  
so all computers had the  same time as the server and now the CPU is  
normal again.

Anders
23 okt 2008 kl. 19.54 skrev Jeremy Wellner:

> I'll second that notion.
>
> We've been having some problems with our core home directory servers  
> and high AFP CPU and I was finally able to bring them offline last  
> night for a bit of maintenance.
>
> Of the 4 I worked on, I believe all of them (it was getting late and  
> cold medicine is awesome...) had volume header block, incorrect  
> #ACLs and to add icing an incorrect # of extent attributes.
>
> They took FOREVER to run disk utility, however 3 of the 4 are quite  
> happy today.  The fourth one took so long running DU that I just let  
> it run overnight and had it up the next morning.
>
> Also part of the maintenance I have a script I churn thru to clean  
> out .DS_Store files, user home caches and a few other things.  
> (Didn't have time to run the script and let it finish hence some of  
> the issues still).
>
> Not to ask a silly question... but how do you peek into the process  
> with dtrace and sc_usage?
>
> Jeremy Wellner
> Technology Group
> Stanwood-Camano School District
> jwellner@...
>
> Internal: x3505
> External: 360-629-1205
> Cell: 425-418-4972
>
> "Time travel?...The evidence is all around us. I'm talking about how  
> every time we make an insurance claim we discover that somehow  
> mysteriously the exact thing we're claiming for is now precisely  
> excluded from our policy."
> - Salmon of Doubt, Douglas Adams (1952-2001)
>
>
>
>
> On Oct 23, 2008, at 9:52 AM, Dan Shoop wrote:
>
>>
>> On Oct 14, 2008, at 11:47 AM, Dan Rader wrote:
>>
>>
>>
>> I was experiencing this problem as well.  I found a DNS error and  
>> fixed it
>> and then restarted the server.  This has taken care of my CPU  
>> maxing out
>> problem until yesterday.
>>
>> I got a call around noon that weird things were happening to my  
>> logged in
>> users.  There docs were disappearing and wallpaper pictures were  
>> gone, etc.
>> The secretary in that building told everybody to shut down their
>> computers until further notice.  Since I didn't actually see this
>> weirdness I told a couple of users to turn their computers back on  
>> and log
>> in.  It appears as though they had lost there doc prefs, sidebar  
>> prefs,
>> and background prefs.  These were the things that were immediately
>> noticeable.  I found out later that most of them have Firefox profile
>> issues as well.
>>
>> This morning I noticed that my CPU % has been over 50% overnight
>> when nobody is supposed to be here and shouldn't have anything  
>> going on
>> and this morning it has been averaging around 75% and looks like it  
>> is
>> slowly creeping up.
>>
>> I don't want to have to restart the server again.  My users are  
>> getting
>> frustrated.  Has anyone found any solutions?
>>
>>
>>
>>
>> You presume that there's a single cause to this. Unfortunately it's  
>> not
>> that simple. Your problem is likely different from others.
>>
>>
>> Given dtrace and sc_usage you can look deeper.
>>
>>
>> Remember though that %CPU is not a metric, and if a process is  
>> consuming
>> most all the CPU that this implies there's no other processes that  
>> are
>> competing for CPU significantly.
>>
>>
>> What normally you find is that when processes are using "excessive"  
>> cpu
>> that they're spending a large amount of system time, which indicates
>> something fundamental wrong, like latency issues, bad DNS,
>> misconfiguration etc. It's spending time there b/c it's made system  
>> calls
>> that aren't getting serviced. Find out why and you solve your  
>> mystery.
>> Other issues occur when you've got waits that never return. That
>> indicates, again, something fundamental that's out of line or  
>> problematic.
>>
>>
>> Guess my overall suggestion is that the issue isn't really with AFP  
>> but
>> something in the system that's not right.
>>
>> -d
>>
>>
>> ------------------------------------------------------------------------
>> Dan Shoop
>> Computer Scientist
>> iWiring / U.S. Technical Services
>>
>>
>> [ mailto:shoop@... ]shoop@...
>> AOL IM .................... iWiring
>> Nextel .................... 1-714-363-1174
>> Operations TOC (24/7) ..... 1-866-901-USTS
>> USTS Offices .............. 1-714-374-6300
>>
>>
>> For immediate response for urgent matters please speak to the Duty  
>> Officer
>> at the USTS Tactical Operations Center (above) who can reach me by  
>> radio.
>>
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Macos-x-server mailing list      (Macos-x-server@...)
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/macos-x-server/jwellner%40stanwood.wednet.edu
>>
>> This email sent to jwellner@...
>>
>> <Attach0.html>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Macos-x-server mailing list      (Macos-x-server@...)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/macos-x-server/agp%40rudebecks.se
>
> This email sent to agp@...
>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      (Macos-x-server@...)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/lists%40nabble.com

This email sent to lists@...

 « Return to Thread: AFP eating up CPU