Apple Support Communities > Servers and Enterprise Software > Mac OS X Server v10.6 Snow Leopard > Discussions
This discussion is archived
3895 Views 8 Replies Latest reply: Nov 21, 2010 6:22 AM by Robert Carneim2
Currently Being ModeratedSep 13, 2010 5:20 AM (in response to Vern Dempster)Do you have time machine on? If so, turn it off.Mac OS X (10.6.2)
Currently Being ModeratedSep 13, 2010 4:09 PM (in response to InterHmai)Time Machine is turned off. I am aware of that. I dont use Server Admin or WGM on the server only remotely. But it just seems during periods of high workload afp dies. I am about to rebuild the server yet again but only take it to 10.6.2 this time. Maybe I will get another 10 days of trouble free fast server to get me through to the holidays!! I have just realised it has been crashing now for 2 terms. of frustration for our teachers and students.xserve, Mac OS X (10.6.4)
Currently Being ModeratedSep 14, 2010 5:20 PM (in response to Vern Dempster)Have you checked the console log for any ideas both on a user's machine and the server?
Energy-Saver/sleep settings on both server and client?
Currently Being ModeratedSep 14, 2010 6:16 PM (in response to Brett Thornsberry1)I have moved mail to my reliable 10.6.2. web server and reinstalled a clean 10.6.2 on our xserve. And hope I get through the next 10 days till holidays- this problem has gone on 2 terms now. It did seem faster when I tested student logins but tomorrow will be the real test.xserve, Mac OS X (10.6.2)
Currently Being ModeratedNov 6, 2010 7:11 PM (in response to Vern Dempster)We have a small, 8 node network of OSX 10.5.8 clients mounting AFP shares from an OSX 10.6.x server. Users report that when another person in the office finishes for the day and shuts their machine down, they lose their connection to the server. This is not an issue of Time Machine or clients falling asleep. The bumped user can simply reconnect but it's a significant annoyance. It seems a bit worse since the server was replaced with the current 10.6.x Mac Mini, but it used to happen, although less, when there was a Mac Pro (G4) server running 10.3.9. The only other recent change (besides the server upgrade), is that the 2 small daisy-chained switches were replaced by a 16 port switch. Same router, same wiring, same service.
At first I thought there was some trick or operator error, but it appears that is not the case.
What could cause other users to be bumped when someone shuts their Mac down? Otherwise, everything works well.
_StumpedMac Mini server, Mac OS X (10.6.3), 4GB RAM, 500GB RAID HD
Currently Being ModeratedNov 7, 2010 3:57 AM (in response to Vern Dempster)Are you sure AFP is actually "dying"?
Are you using Calendar Server, and if so, do people have the same connection errors?
I ask because we have this happen a lot, and we find that if we go to "Server Preferences", and click on "Users", and then click on each user's name, suddenly they can log back in. Can you see if that "fixes" the issue for you?
Currently Being ModeratedNov 8, 2010 3:39 AM (in response to Jamie Curmi)The AFP is not 'dying' as often others are still connected.
What happens is persons A, B, C are connected to 1 AFP share. A shuts down, B is disconnected from the share and C remains connected. B can immediately reconnnect and continues.
We are not using Calendar server. In fact at this point we're only using AFP, SMB, Open Directory services.Mac OS X (10.4.6)
Currently Being ModeratedNov 21, 2010 6:22 AM (in response to Vern Dempster)I've been posting in other threads, trying to track down this issue. I'm having this problem, but I thought it was due to the 10.6.5 update. (I wasn't running a domain configuration on any Snow Leopard systems until the 10.6.5 update.)
So, I have a domain account; I log in with this account from the client and create a mobile account; the share point containing the network home directories is automatically mounted; this share gets unceremoniously disconnected at some random time (usually less than an hour); I can open that connection again from the client with no problem, but the running apps can't handle the interruption (for example, my iTunes Media is on that share, but outside my home directory). Also, my TGT and the ticket for the server are intact.
*Now, if I log in to the client with a local account and then connect to the server share with my domain credentials, the share stays connected just fine.*
I'm going to have to live with this setup for a while I guess (this is what I was doing previously anyway), but I don't like having the separate local home directory that doesn't sync to the server (automatically).