toggle

AAPL Stock: 423 ( 0 )

http://www.macnn.com/articles/09/01/13/afp.server.problems/

AFP rendering Mac servers unusable

updated 04:05 pm EST, Tue January 13, 2009

 

AFP server problems


Problems with Mac OS X Server are causing some corporate networks to come to a crawl, complaints from network administrators indicate. The problem is believed to stem specifically from Apple File Protocol, as used by Mac OS X Leopard Server; whereas Leopard typically consumes only a portion of the CPU power on an Xserve, some administrators have noticed quad- and eight-core Xserves becoming non-functional due to AFP activity. CPU burden can become as bad as 800 percent, according to one complaint.

The exact reason for the AFP overloads is unknown, and their appears to be no permanent solution to the problem, whether from Apple or an independent source. Killing processes and/or restarting a server is necessary for recovery; some administrators say they have managed to reduce server load by adjusting the afp_wan_quantum and afp_wan_threshold variables on a server, and killing unnecessary processes or tasks.


by MacNN Staff

Post tools:

TAGS :

 troubleshooting, enterprise, Xserve, Leopard Server, Mac OS X Server

Related Articles

Recent Articles

toggle

Comments

  1. Zanziboy

    Forum Regular

    Joined: Aug 2008

    +1
    01/13, 04:52pm | report spam | Reply |

    Poor old AFP!

    Apple needs to investigate this issue promptly. These kinds of problems could be hard to diagnose without the help of Apple and a good analysis of the network traffic. However, part of the cause could be related to an inappropriate network architecture.

  1. rtbarry

    Fresh-Faced Recruit

    Joined: Aug 2001

    -5
    01/13, 05:05pm | report spam | Reply |

    "and their appears"

    the awesome writing/editing continues. yay.

  1. Creator1326

    Fresh-Faced Recruit

    Joined: Jan 2009

    +6
    01/13, 05:21pm | report spam | (1 reply) Reply |

    Traced it to Safari 3.2.1

    I traced my problem of this nature to the use of Safari 3.2.1 by network accounts. Once I switched everybody to Firefox and disallowed the use of that version of Safari the problem hasn't resurfaced. I have six Xserves serving home folders and running 10.5.5 Server and 450 clients on 10.4.11 and 32 of those on 10.5.6.

  1. malax

    Fresh-Faced Recruit

    Joined: Aug 2006

    +3
    01/13, 09:53pm | report spam | Reply |

    Minor error

    Actually it's "Apple Filing Protocol" not Apple File Protocol. Ain't trvia fun?

  1. jpellino

    Fresh-Faced Recruit

    Joined: Oct 1999

    +2
    01/13, 11:03pm | report spam | Reply |

    Would it kill them...

    ...to finally implement rw FTP in the Finder? They even embedded Panic's FTP in iWeb. This is eternally puzzling.

  1. themacjedicali

    Fresh-Faced Recruit

    Joined: Nov 2007

    -1
    01/14, 02:42am | report spam | Reply |

    What can we expect?

    What can we really expect forma company that still has a finder that hangs just because network store isn't responding? Or a CD that wont eject for mysterious reasons? They should also be able to tell the user EXACTLY what program is halting media ejections, as the generic messages rarely help when they say "start closing programs" WHAT?. They should be able to cancel a network store mounting WHEN I CLICK CANCEL and not halt the finder. Most beginning users know nothing of the terminal and how to recover from this when the relaunch finder command fails. There are serious issues that need to be fixed and if Microsoft was a pompous as apple was, they would make commercials saying how crappy certain fundamental parts of OS X STILL work nowhere near properly. As mac lovers we need to get on Apple to get this tuff fixed! 99% of everything else of course works like a charm which is why Apple rocks!

  1. Guest

    Fresh-Faced Recruit

    Joined: Nov 1999

    +3
    01/14, 03:39am | report spam | Reply |

    Just the usual...

    We've been using Apple servers for eons now, AFP problems are nothing new. We had issues with stability (caused by AFP) as far back as 10.2.

    Apple's line is a consistent "try this patch", and we've never got one that works. So far, what does seem to work is to reduce the number of users on each server (50 seems to be the maximum for a quad-core and 100-or-so for an 8-core), and set the servers to restart every night when no-ones using them.

    Personally, I think it's a memory leak somewhere in the AFP implementation, simply because the issue is cumulative. Starting with a fresh reboot, everything works well, then as time progresses, it gets worst and worst, until the AFP thread takes over all the processing power and brings the servers to a halt.

    OsX does have its of problems, but it has its advantages as well. Don't bash a system just because of one "glitch" (persistent as it may be).

    M. (ACSA)

Login Here

Not a member of the MacNN forums? Register now for free.

 
close
Photo
toggle

Network Headlines

toggle

Most Popular

MacNN Sponsor

Recent Reviews

Logitech FabricSkin Keyboard Folio for iPad

Since the fourth-generation iPad didn't evolve much over its predecessor, the market for iPad accessories has remained somewhat static ...

Huawei Ascend Mate

The Huawei Ascend Mate is a phone that fits the screen-size gap between the 4 to 5-inch smartphone and the seven-inch or more tablet, ...

MaxUpgrades MaxConnect for 2006-2008 Mac Pro

Nobody outside of Cupertino's privileged bunch knows the future of the Mac Pro line for sure. Despite Apple's reluctance to tell us wh ...

toggle

Most Commented

 

Popular News