Home › Forums › OS X Server and Client Discussion › File Serving › 10.4.7 Craziness with File sharing…
- This topic has 1 reply, 2 voices, and was last updated 18 years, 7 months ago by
slaw1020.
-
AuthorPosts
-
August 24, 2006 at 11:04 pm #366907
Zeheeba
ParticipantHello all,
i have a new problem that I have been experiencing on a couple different XServe G5’s running server 10.4.7 and XSan 1.3. The Xsan mounts volumes that are reshared via AFP. All servers are bound to our AD for users and groups.
The server always behaves for a while after reboot, but at some point will start to act strangly.
Stage 1: SMB starts making multiple connections per user. As in having 3 connections from “danielc” orignating from the same IP. Soon 10 people logging into the server turns into 100 connections. Soon SMB stops responding to people. Stopping the service doesnt solve the problem. Only a reboot will bring the service back to normal.
Stage 2: Once SMB is stopped, the CPU load from the AFP server goes through the roof. I’m talking 145% cpu used. At this point the load starts climbing.
Stage 3: Now server admin wont work correctly. Using the serveradmin utility doesn’t work. Even serveradmin list will just sit there hanging.
A full reboot is the only solution to these problems.
What I have done…
Following the tuning afp article, I have increaesd the max threads of the afp server to 600.
Enabled AFP debugging. I’m hoping its not a corrupt .DS_Store issue as it would get ugly around here quick if I had to delete them all.Any other ideas people may have would be appreciated.
Regards,
ZSeptember 4, 2006 at 2:24 pm #366986slaw1020
ParticipantGood Morning,
We ran into the same thing this week. Two 10.4.7 servers: one an OD Master with the other server bound to the OD master through Directory Access. The second server was our network homes for both Mac and PC student accounts and this was the server that overloaded. Both servers were also bound through Kerberos for single sign-on. The OD Master was set as a PDC and the second server was a “Domain Member”. SMB went nuts on the member server just as yours did. Talked to Apple directly and also talked to an Apple engineer in another district. Here is what we found:
1. The number of automount home folders on our second server was more than three. We needed to consolidate to less than three. We consolidated to one.
2. Since the servers were bound together via Kerberos, we didn’t need the second server to be a “Domain Member” in Server Admin>Windows. Once we demoted it to a standalone server in ServerAdmin>Windows, everything quieted down and the server load was minimal. The number of instances of smbd running on the second server was small and the processor load was great.We started up three labs of computers (Mac and PC) and had 80+ computers connected to the second server simultaneousy. Left them running for a while. Had no ill effects.
I don’t know if this will help you solve your issue but it is working for us right now. I hope that maybe there is something here that you can use.
Best Regards,
Steve
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed