|
|
#1 |
|
Prospect
Join Date: Dec 2003
Location: Santiago, Chile
Posts: 18
|
Beachball when trying to mount a specific Mac
Hello.
I am having trouble with a Mac mini (1.5 Ghz G4) that is on my network. It is connected via DHCP to the network, as all other computers (Macs and PCs). It worked flawlessly until one day it starting with an issue: When trying to mount its shared folder from another Mac, it causes the beachball to hung the computer from where you are trying to connect. This happens from any Mac, Intel or PPC. Also, File Sharing deactivates in the Mac mini when this happens. I have tried resetting the preferences, caches, I have reset the PMU with no success. I finally erase and reinstall Mac OS X and the problem went away. But it has come back again. No other computer can connect to it's shared folder. I have updated to 10.4.7, reinstalled the combo updater, and no success. I don't want to backup, erase and reinstall again. Any idea how can I fix this? Thank you!
__________________
Hugo 2 Ghz MacBook 2 Gb of RAM Mac OS X 10.4.x "Tiger" |
|
|
|
|
|
#2 |
|
League Commissioner
Join Date: Sep 2003
Location: Old Europe
Posts: 5,146
|
Please copy any interesting system.log entries here.
|
|
|
|
|
|
#3 |
|
Site Admin
Join Date: Jan 2002
Location: Montreal
Posts: 32,473
|
The beachball is due to the Mac Mini not responding to the sharing request.
Ignore that for the moment as it seems the real problem is on the Mac Mini. You should look in the Mac Mini's logs for relevant messages. Launch the "Console" application (under /Applications/Utilities) on the Mac Mini and look for relevant error messages. Note that messages are labeled with the date & time so you can use that to locate the part of the log to look at. Copy & paste the relevant messages back here so we can see them. Be sure to look at system.log as well as console.log (Use the "Logs" button (top-left) to see the various logs available - note that you will probably need to be an "admin" user to see the system.log) Note that there should be a separate log for AFP as well.
__________________
hayne.net/macosx.html |
|
|
|
|
|
#4 |
|
Prospect
Join Date: Dec 2003
Location: Santiago, Chile
Posts: 18
|
Hayne, thank you very much.
I opened Console and recreated the situation. Something crashes: Aug 4 10:55:49 Hugo /System/Library/PrivateFrameworks/Admin.framework/Resources/writeconfig: AFPDefines Start AFP Server request\n Aug 4 10:56:45 Hugo crashdump[495]: AppleFileServer crashed Aug 4 10:56:46 Hugo crashdump[495]: crash report written to: /Library/Logs/CrashReporter/AppleFileServer.crash.log Aug 4 10:58:12 Hugo crashdump[504]: smbd crashed Aug 4 10:58:12 Hugo crashdump[504]: crash report written to: /Library/Logs/CrashReporter/smbd.crash.log Aug 4 11:00:13 Hugo crashdump[523]: smbd crashed Aug 4 11:00:13 Hugo crashdump[523]: crash report written to: /Library/Logs/CrashReporter/smbd.crash.log And the log is this: Host Name: Hugo Date/Time: 2006-08-04 10:56:45.186 -0400 OS Version: 10.4.7 (Build 8J135) Report Version: 4 Command: AppleFileServer Path: /usr/sbin/AppleFileServer Parent: launchd [1] Version: ??? (???) PID: 489 Thread: 5 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000008 Thread 0: 0 libSystem.B.dylib 0x9001f7ac select + 12 1 AppleFileServer 0x00053514 0x1000 + 337172 2 AppleFileServer 0x0009a838 0x1000 + 628792 3 AppleFileServer 0x00037634 0x1000 + 222772 4 AppleFileServer 0x0004c8f4 0x1000 + 309492 5 AppleFileServer 0x0004c9e4 0x1000 + 309732 6 AppleFileServer 0x00049ecc 0x1000 + 298700 7 AppleFileServer 0x00002388 0x1000 + 5000 8 AppleFileServer 0x00002230 0x1000 + 4656 Thread 1: 0 libSystem.B.dylib 0x9000b268 mach_msg_trap + 8 1 libSystem.B.dylib 0x9000b1bc mach_msg + 60 2 com.apple.CoreFoundation 0x907dbb78 __CFRunLoopRun + 832 3 com.apple.CoreFoundation 0x907db47c CFRunLoopRunSpecific + 268 4 com.apple.CoreFoundation 0x907ea8dc CFRunLoopRun + 52 5 AppleFileServer 0x0003c760 0x1000 + 243552 6 AppleFileServer 0x0004c8f4 0x1000 + 309492 7 AppleFileServer 0x0004c9e4 0x1000 + 309732 8 libSystem.B.dylib 0x9002bc28 _pthread_body + 96 Thread 2: 0 libSystem.B.dylib 0x9002c2e8 semaphore_wait_signal_trap + 8 1 libSystem.B.dylib 0x90001b30 pthread_mutex_lock + 472 2 AppleFileServer 0x0004d514 0x1000 + 312596 3 AppleFileServer 0x0004de20 0x1000 + 314912 4 AppleFileServer 0x0004c8f4 0x1000 + 309492 5 AppleFileServer 0x0004c9e4 0x1000 + 309732 6 libSystem.B.dylib 0x9002bc28 _pthread_body + 96 Thread 3: 0 libSystem.B.dylib 0x9002c2e8 semaphore_wait_signal_trap + 8 1 libSystem.B.dylib 0x90001b30 pthread_mutex_lock + 472 2 AppleFileServer 0x0004d514 0x1000 + 312596 3 AppleFileServer 0x0004de20 0x1000 + 314912 4 AppleFileServer 0x0004c8f4 0x1000 + 309492 5 AppleFileServer 0x0004c9e4 0x1000 + 309732 6 libSystem.B.dylib 0x9002bc28 _pthread_body + 96 Thread 4: 0 libSystem.B.dylib 0x9002c2e8 semaphore_wait_signal_trap + 8 1 libSystem.B.dylib 0x90001b30 pthread_mutex_lock + 472 2 AppleFileServer 0x0004d514 0x1000 + 312596 3 AppleFileServer 0x0004de20 0x1000 + 314912 4 AppleFileServer 0x0004c8f4 0x1000 + 309492 5 AppleFileServer 0x0004c9e4 0x1000 + 309732 6 libSystem.B.dylib 0x9002bc28 _pthread_body + 96 Thread 5 Crashed: 0 com.apple.ByteRangeLocking 0x962285dc DBMutex::Grab() + 36 1 com.apple.ByteRangeLocking 0x962257cc NLMDB::FindFileRecord(NLMDBID const&, unsigned*) + 56 2 com.apple.ByteRangeLocking 0x96225904 NLMDB::FindElseCreateFileRecord(NLMDBID const&, unsigned*) + 52 3 com.apple.ByteRangeLocking 0x962235ec BRLMCarbonOpen + 396 4 AppleFileServer 0x0006a5cc 0x1000 + 431564 5 AppleFileServer 0x000686f0 0x1000 + 423664 6 AppleFileServer 0x00069e3c 0x1000 + 429628 7 AppleFileServer 0x00069c48 0x1000 + 429128 8 AppleFileServer 0x000595d4 0x1000 + 361940 9 AppleFileServer 0x0006e578 0x1000 + 447864 10 AppleFileServer 0x0008ea34 0x1000 + 580148 11 AppleFileServer 0x0007bc58 0x1000 + 502872 12 AppleFileServer 0x0007b634 0x1000 + 501300 13 AppleFileServer 0x0009e95c 0x1000 + 645468 14 AppleFileServer 0x000a662c 0x1000 + 677420 15 AppleFileServer 0x0004df54 0x1000 + 315220 16 AppleFileServer 0x0004c8f4 0x1000 + 309492 17 AppleFileServer 0x0004c9e4 0x1000 + 309732 18 libSystem.B.dylib 0x9002bc28 _pthread_body + 96 Thread 6: 0 libSystem.B.dylib 0x9000610c syscall + 12 1 AppleFileServer 0x0004deac 0x1000 + 315052 2 AppleFileServer 0x0004c8f4 0x1000 + 309492 3 AppleFileServer 0x0004c9e4 0x1000 + 309732 4 libSystem.B.dylib 0x9002bc28 _pthread_body + 96 Thread 5 crashed with PPC Thread State 64: srr0: 0x00000000962285dc srr1: 0x000000000000f030 vrsave: 0x0000000000000000 cr: 0x24004022 xer: 0x0000000000000004 lr: 0x00000000962285c0 ctr: 0x0000000090b94338 r0: 0x00000000962257cc r1: 0x00000000f0283fc0 r2: 0x00000000a6222008 r3: 0x0000000000000004 r4: 0x00000000f02843f0 r5: 0x0000000000000000 r6: 0x00000000f0284350 r7: 0x0000000020617262 r8: 0x000000006f6c2063 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000022004028 r12: 0x0000000090b94338 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000003 r20: 0x0000000000410154 r21: 0x0000000001824d3c r22: 0x00000000f02843f0 r23: 0x0000000000000002 r24: 0x00000000a622346c r25: 0x0000000000000000 r26: 0x0000000000076fad r27: 0x00000000f02843f0 r28: 0x0000000000406830 r29: 0x00000000a62285c0 r30: 0x0000000000000004 r31: 0x00000000962285c0 It continues but I trimmed it... Apple File server is the problem. Is there anything I can install or update to fix this situation? Thank you very much.
__________________
Hugo 2 Ghz MacBook 2 Gb of RAM Mac OS X 10.4.x "Tiger" |
|
|
|
|
|
#5 | |||||||||||||||||||||||
|
Site Admin
Join Date: Jan 2002
Location: Montreal
Posts: 32,473
|
Please attach the whole of that crash log as a plain text file, using the "Manage Attachments" button at the bottom when you reply. The part at the bottom is often the most important part. Anything unusual about your Mac Mini's configuration? Partitions? Filesystem format?
__________________
hayne.net/macosx.html |
|||||||||||||||||||||||
|
|
|
|
|
#6 |
|
Prospect
Join Date: Dec 2003
Location: Santiago, Chile
Posts: 18
|
Here is the complete log... Thank you very much for your interest.
I have two partitions, but before I had only one. The same problem happened with both situations. Filesystem is Journaled HFS+
__________________
Hugo 2 Ghz MacBook 2 Gb of RAM Mac OS X 10.4.x "Tiger" Last edited by hugotron; 08-04-2006 at 03:36 PM. |
|
|
|
|
|
#7 | |||||||||||||||||||||||
|
Site Admin
Join Date: Jan 2002
Location: Montreal
Posts: 32,473
|
I guess you didn't understand what was meant by "plain text". MS Word docs are not plain text. I attach below the log in plain text. Nothing jumps out at me from the log as a clue. I can only advise you to look closely at that machine to figure out what might be peculiar about it. What 3rd-party software do you have installed that might affect this? You said that the problem went away after an "erase & install". maybe you should do that again, but don't install anything else on that machine except data files. No other software. And don't make any changes to the configuration until it is shown as stable. Then make one change at a time and test.
__________________
hayne.net/macosx.html Last edited by hayne; 08-04-2006 at 04:01 PM. |
|||||||||||||||||||||||
|
|
|
|
|
#8 |
|
Prospect
Join Date: Dec 2003
Location: Santiago, Chile
Posts: 18
|
Hayne, thank you.
I know what plain text is... I apologize because of the Word document... This phrase is the one that appears all the time in my Console log: Aug 4 11:00:13 Hugo crashdump[523]: smbd crashed Aug 4 11:00:13 Hugo crashdump[523]: crash report written to: /Library/Logs/CrashReporter/smbd.crash.log What is smbd?
__________________
Hugo 2 Ghz MacBook 2 Gb of RAM Mac OS X 10.4.x "Tiger" |
|
|
|
|
|
#9 |
|
Site Admin
Join Date: Jan 2002
Location: Montreal
Posts: 32,473
|
smbd is the server program for SMB sharing (i.e. "Windows sharing").
You usually only enable this (in Sharing prefs) if you want to share your Macs files to Windows machines.
__________________
hayne.net/macosx.html |
|
|
|
|
|
#10 |
|
Prospect
Join Date: Dec 2003
Location: Santiago, Chile
Posts: 18
|
Hayne, look this:
http://discussions.apple.com/thread....68015� I will try it right now. I'm burning a DVD and when finished, I will restart and post back again.
__________________
Hugo 2 Ghz MacBook 2 Gb of RAM Mac OS X 10.4.x "Tiger" |
|
|
|
|
|
#11 |
|
League Commissioner
Join Date: Sep 2003
Location: Old Europe
Posts: 5,146
|
First of all, the very fact that this problem can even occur, shows that whoever managed that project/wrote that code should probably jump off a cliff so some Real Programmers can fix it.
When a service starts, then notices that it lacks a critical plist, it should probably create one with reasonable default values, rather than to crash in silent despair. Everybody who has wasted time with this problem should really file a bug report at radar.apple.com. If you go to the WWDC, try to attract the bozo responsible for this blunder near an open elevator shaft... Anyway, searching here instead would have brought up this thread: http://forums.macosxhints.com/showthread.php?t=51785 Where Apple support recommends the same workaround. In case anybody wondered, a sane version of /Library/Preferences/com.apple.ByteRangeLocking.plist on a 10.4.7 system looks like this: Code:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>DB_HASH_TABLE_MAX</key> <integer>4096</integer> <key>DB_INIT_SIZE</key> <integer>2097152</integer> <key>DB_Location</key> <string>/var/db/BRLM.db</string> <key>DB_PROC_TABLE_MAX</key> <integer>1000</integer> </dict> </plist> Last edited by voldenuit; 08-04-2006 at 06:06 PM. |
|
|
|
![]() |
|
|