Snow Leopard hangs after LDAP login, mouse work...
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Afternoon,
It was suggested that I post my question below in a server forum rather than a client form.
Mike
------------------------------------
Morning,
Earlier I posted a question about 10.5 brightness and 10.6. The user will deal with the brightness issue, so that's moot at the moment. I still have an issue with 10.6 hanging.
I have configured 10.6 to authenticate using OpenLDAP from a Red Hat box. The authentication works fine. I have added /home from the same linux box to the list of NFS mounts (Disk Utility->File->NFS Mounts?, I'm not in front of the mac box at this moment to verify). The /home filesystem does get mounted.
Very quickly after logging into a non-local, LDAP account, the mac box becomes useless in that I cannot start any programs, I can't logout, I can't do anything. If I double click on Terminal (Applications->Utilities->Terminal) I get the brief flash like Terminal is starting, but the application never appears on the desktop.
I can still ssh into the mac box. When I ssh in and run top, to see what's consuming the CPU, the machine is idle. My guess right now is every application is timing out or failing to start. I see nothing hogging the CPU nor the network.
When I log in using a local, non-LDAP account the mac box acts as I expect it to when launching applications, looking at NFS, surfing the web, etc.
Any ideas what's going on, what to check for, and how to fix this?
This is an iMac 27". I may need to contact Apple support on this one.
Mike
------------------------------------
Additionally, the mouse continues to work, the keyboard stops working (wifi both), and the finder starts reporting -10810 on every application open attempt. I can select the Apple->Logout or Restart options, but nothing happens. I must ssh into the iMac and 'shutdown -r now' to get back to a login so I can login as root to make further changes.
Mike
14 replies
Sign in or join Beachball Help to reply.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I was able to grab a crash log if that helps.
Mike
--------------------------------------------
Process: coreservicesd [58]
Path: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/Support/coreservicesd
Identifier: coreservicesd
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [1]Date/Time: 2010-01-29 16:00:10.976 -0600
OS Version: Mac OS X 10.6.2 (10C2234)
Report Version: 6Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x0000000000000000
Crashed Thread: 3Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x0000000100007e3a machmsgtrap + 10
1 libSystem.B.dylib 0x00000001000084ad mach_msg + 59
2 com.apple.CoreFoundation 0x00000001009e87a2 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00000001009e7c2f CFRunLoopRunSpecific + 575
4 com.apple.CoreFoundation 0x00000001009e79b6 CFRunLoopRun + 70
5 ...ple.CoreServices.CarbonCore 0x000000010030c972 _CoreServicesServerMain + 522
6 coreservicesd 0x0000000100000eac 0x100000000 + 3756Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x0000000100020bba kevent + 10
1 libSystem.B.dylib 0x0000000100022a85 dispatch_mgrinvoke + 154
2 libSystem.B.dylib 0x000000010002275c dispatch_queueinvoke + 185
3 libSystem.B.dylib 0x0000000100022286 dispatch_workerthread2 + 244
4 libSystem.B.dylib 0x0000000100021bb8 pthreadwqthread + 353
5 libSystem.B.dylib 0x0000000100021a55 start_wqthread + 13Thread 2:
0 libSystem.B.dylib 0x00000001000219da _workqkernreturn + 10
1 libSystem.B.dylib 0x0000000100021dec pthreadwqthread + 917
2 libSystem.B.dylib 0x0000000100021a55 start_wqthread + 13Thread 3 Crashed:
0 ...ple.CoreServices.CarbonCore 0x00000001002c152e fmodWatchConsumer + 1098
1 libSystem.B.dylib 0x0000000100040f8e pthreadstart + 331
2 libSystem.B.dylib 0x0000000100040e41 thread_start + 13Thread 4:
0 libSystem.B.dylib 0x0000000100012426 read + 10
1 ...ple.CoreServices.CarbonCore 0x00000001002c1f08 fmodWatchProducer + 140
2 libSystem.B.dylib 0x0000000100040f8e pthreadstart + 331
3 libSystem.B.dylib 0x0000000100040e41 thread_start + 13Thread 5:
0 libSystem.B.dylib 0x00000001000219da _workqkernreturn + 10
1 libSystem.B.dylib 0x0000000100021dec pthreadwqthread + 917
2 libSystem.B.dylib 0x0000000100021a55 start_wqthread + 13Thread 3 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000101c835ee rcx: 0x00007fffffe00080 rdx: 0x0000000101ae202c
rdi: 0x0000000000000006 rsi: 0x0000000101c835f4 rbp: 0x0000000101f80f10 rsp: 0x0000000101f80db0
r8: 0x0000000101ae2078 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x000000010028272f
r12: 0x0000000000000000 r13: 0x0000000101c83624 r14: 0x0000000101c83624 r15: 0x0000000000000006
rip: 0x00000001002c152e rfl: 0x0000000000010202 cr2: 0x0000000000000000Binary Images:
0x100000000 - 0x100000fff coreservicesd ??? (???) <6D7763A3-EBAF-99C6-FE9A-F79ABB1D96BC> /System/Library/CoreServices/coreservicesd
0x100004000 - 0x100004ff7 com.apple.CoreServices 44 (44) <210A4C56-BECB-E3E4-B6EE-7EC53E02265D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x100007000 - 0x1001c5ff7 libSystem.B.dylib ??? (???) <3814B353-9EE2-E2D3-2D5D-9FE26D4AF5D6> /usr/lib/libSystem.B.dylib
0x100256000 - 0x10025aff7 libmathCommon.A.dylib ??? (???) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
0x10025d000 - 0x10058ffef com.apple.CoreServices.CarbonCore 861.2 (861.2) <8D3CECD6-0184-C481-14DF-544F6C1BD4D9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x100608000 - 0x1006d4fff com.apple.CFNetwork 454.5 (454.5) <34CC453F-9BFC-F6F6-78FE-304F19A8266F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x100744000 - 0x10078eff7 com.apple.Metadata 10.6.2 (507.4) <89D9A7A8-00D8-6143-31C9-708275853E91> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x1007b8000 - 0x100875ff7 com.apple.CoreServices.OSServices 352 (352) <991CA6C2-78C5-93CC-A7AA-7BF351991BC6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x1008cf000 - 0x10095ffff com.apple.SearchKit 1.3.0 (1.3.0) <3403E658-A54E-A79A-12EB-E090E8743984> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x10099d000 - 0x100b10ff7 com.apple.CoreFoundation 6.6.1 (550.13) <65C48FB9-CE32-68C4-9457-D8392775ED55> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x100c29000 - 0x100c64ff7 com.apple.AE 496.1 (496.1) <9B43962D-4AE5-7CB5-EA81-50C27AF5AD94> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x100c7e000 - 0x100d1efff com.apple.LaunchServices 362 (362) <0420B038-B12E-0976-A069-15894B398314> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x100d64000 - 0x100d8cfff com.apple.DictionaryServices 1.1.1 (1.1.1) <CC593ECB-8FFA-BF81-0B0D-F8C606B31318> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x100da6000 - 0x100e03fef com.apple.framework.IOKit 2.0 (???) <4437494E-1E7F-EE0F-9FCA-AC5BC46DFD57> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x100e25000 - 0x100fe3fff libicucore.A.dylib ??? (???) <7165A473-3A42-A15A-C6B0-75DECF1C3ECF> /usr/lib/libicucore.A.dylib
0x101052000 - 0x101058ff7 com.apple.DiskArbitration 2.3 (2.3) <857F6E43-1EF4-7D53-351B-10DE0A8F992A> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x101061000 - 0x101077fef libbsm.0.dylib ??? (???) <83676D2E-23CD-45CD-BE5C-35FCFFBBBDBB> /usr/lib/libbsm.0.dylib
0x101080000 - 0x10108ffff com.apple.NetFS 3.2.1 (3.2.1) <3C6C2D5E-C1E2-9FF9-97A2-4141A5660EBB> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x101098000 - 0x10114efff libobjc.A.dylib ??? (???) <4B6351E5-A293-D814-36E1-E75E35C25D86> /usr/lib/libobjc.A.dylib
0x101162000 - 0x1011dffef libstdc++.6.dylib ??? (???) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
0x101240000 - 0x101251fef libz.1.dylib ??? (???) <3A7A4C48-A4C8-A78A-8B87-C0DDF6601AC8> /usr/lib/libz.1.dylib
0x101256000 - 0x101264ff7 libkxld.dylib ??? (???) <60D615F8-6AD1-0AFF-8303-6F3627296780> /usr/lib/system/libkxld.dylib
0x101268000 - 0x1012b4fff libauto.dylib ??? (???) <8145CA34-EA03-11D2-5C60-02C1E5750593> /usr/lib/libauto.dylib
0x1012c1000 - 0x101546fe7 com.apple.security 6.1.1 (37594) <E5DA8BFD-4A48-EFD4-E938-3BDFB356A8AF> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x10163c000 - 0x1016f5fff libsqlite3.dylib ??? (???) <5A15E12A-AE8F-1A36-BBC7-564E7D7AD0FB> /usr/lib/libsqlite3.dylib
0x101705000 - 0x101746ff7 com.apple.SystemConfiguration 1.10.1 (1.10.1) <199E5964-B414-05BE-7930-D63309134523> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x101769000 - 0x101794ff7 libxslt.1.dylib ??? (???) <87A0B228-B24A-C426-C3FB-B40D7258DD49> /usr/lib/libxslt.1.dylib
0x10179f000 - 0x1018b6fef libxml2.2.dylib ??? (???) <4355C785-9388-1061-6427-D004E92A3766> /usr/lib/libxml2.2.dylib
0x103294000 - 0x1032b4ff7 com.apple.DirectoryService.Framework 3.6 (621.1) <1B6C18CD-2257-1CEB-00C4-1BD8EB267DDE> /System/Library/Frameworks/DirectoryService.framework/DirectoryService
0x7fff5fc00000 - 0x7fff5fc3bde7 dyld 132.1 (???) <A43F7314-3A8C-4391-3237-46790EE6313A> /usr/lib/dyld
0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <3814B353-9EE2-E2D3-2D5D-9FE26D4AF5D6> /usr/lib/libSystem.B.dylib--------------------------------------------
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have no answers, but I can corroborate the issue. We had dozens of Macs running Snow Leopard - different flavors of Macs 27" iMacs, 21.5" iMacs, 21"iMacs, Quad Core Mac Pros, Dual Core Mac Pros that all had the same symptoms. After LDAP authentication, between 20 minutes and an hour and a half, the Mac would hang. Mouse worked, some keys worked, but new processes would not start. Eventually, all processes would halt, and Internet connectivity would stop. Local logins were fine. We switched our Macs to Active Directory authentication, and the hanging stopped. The same LDAP settings we used for LDAP authentication in Leopard were used for our Snow Leopard installation.
We're waiting to hear from Apple what the issue is.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm also seeing this problem. I've been holding off SL upgrade because of this LDAP problem. I am using CentOS Linux OpenLDAP server. I can log in and the Mac client runs for a few minutes. However, I see the same hang as you described. With Leopard 10.5, it runs fine. I did a search and found this article:
http://www.xlr8yourmac.com/feedback/OSX106_SSL_LDAPproblems.html
The article mentions disabling SSL encryption. I am using SSL encryption so this might fix my problem. I'll try changing my OpenLDAP server to allow non-SSL connection. I really don't want to have to do this though.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks for the links (several people). I'm on an small, internal network and I'm not using SSL (reduce the number of things going on) anywhere for OpenLDAP connections. So it's not the SSL issue. I wonder what's causing the issue?
Mike
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
fyi, I changed OpenLDAP to accept unencrypted LDAP requests and disabled SSL encryption in SL DirectoryService. I've been running for a few hours on the Mac now... Usually, it would hang after an hour or so and I would have to hard reset the Mac using the power button.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I want to make sure my OpenLDAP allows unencrypted connections (I'm sure it does, but I want to be really sure!). Where did you change your OpenLDAP to allow unencrypted connections?
Mike
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
In CentOS and other RedHat based Linux, edit /etc/sysconfig/ldap. Changed the line:
SLAPD_LDAP=yes
Restart OpenLDAP server with:
$ /sbin/service ldap restart
This basically starts "slapd" with the "-h ldap:///" arguments appended to it. Make sure LDAP tcp port 389 is allowed from your firewall.
Start on the Mac /System/Library/CoreServices/Directory Utility.app, make sure SSL is unchecked.
Verify Mac is sending ldap requests on port 389 via tcpdump or wireshark sniffer.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Mike, I looked at your logs closer and they are different than what I'm seeing although both seem to exhibit the same symptoms. When I had SSL enabled, the last thing I would see in system.log before the hang:
Feb 3 06:37:24 astro PubSubAgent[501]: * Could not create /Users/jim/Library : CFURL error 4294967286
Feb 3 06:37:24 astro PubSubAgent[501]: Foundation::NetException "CFURL error 4294967286" caught in int PSAgentFrameworkMain()
Feb 3 06:37:24 astro com.apple.launchd.peruser.1000[85] (com.apple.PubSub.Agent[501]): Exited with exit code: 1Shortly after that, my system hangs and I have to do a hard reset to get out of it. It no longer hangs when I have SSL disabled. I've been running over 18 hours now. With SSL enabled, my Mac Mini would hang less than an hour so it is a step in the right direction.
I did notice one thing different though. Here is what my user info looks like under Leopard (10.5):
jim@muttley[~]$ id jim
uid=1000(jim) gid=1000(eng) groups=1000(eng),103(com.apple.sharepoint.group.3),2001(svn),101(com.apple.shar epoint.group.1),20(staff),2000(cvs),102(com.apple.sharepoint.group.2),1001(devel )
jim@muttley[~]$ groups jim
eng com.apple.sharepoint.group.3 svn com.apple.sharepoint.group.1 staff cvs com.apple.sharepoint.group.2 develLooks good. The groups >= 1000 are my LDAP groups. With Snow Leopard (10.6), my user info is slightly different and it doesn't list my LDAP group ids:
jim@astro[~]$ id jim
uid=1000(jim) gid=1000 groups=1000,62(netaccounts),12(everyone),404(com.apple.sharepoint.group.3),402( com.apple.sharepoint.group.1),403(com.apple.sharepoint.group.2)
jim@astro[~]$ groups jim
1000 netaccounts everyone com.apple.sharepoint.group.3 com.apple.sharepoint.group.1 com.apple.sharepoint.group.2The only group that exist is my base group = 1000. Furthermore, it is unable to translate the uid to its literal form (eng). So, Snow Leopard is unhappy about something and isn't playing nice with the LDAP server. I'm certainly not an LDAP expert so it could be something I'm doing wrong on the server side although I have been running this single sign-on Kerberos/OpenLDAP on CentOS for 3+ years now and it ran fine with OS X Tiger and OS X Leopard. Maybe the OpenDirectory guys are lurking on this list and can point out the problem(s). Let me know if you make progress on your end.
-Jim
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I just found this post while looking into an issue related to the id command. I have a program that relies on _id -Gn_ to determine the groups that different users belong to. As you pointed out, after upgrading to Snow Leopard, suddenly the id command appears to work differently:
In Snow Leopard, the Open Directory groups that I create using Workgroup Manager no longer show up when using the _id -Gn_ command. Under OS X 10.5.8, these groups show up when running _id -G_ or _id -Gn_ commands (but not when using plain id command without parameters).
Using id with 10.6.2, the only way I can determine a user's group information is with _id -G_ - this at least gives me the group id number, now all I have to do is insert the extra step of translating the group id number to the group name.
I've also noticed that Directory.app is gone in 10.6.2 leaving no easy way (that I can tell) to read & configure Open Directory group ownership.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Directory Utility has moved to /System/Library/CoreServices in 10.6
You can also get to it though System Preferences --> Accounts --> Login Options.
Message was edited by: kmrivers
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks, I do still use Directory Utility.app in Snow leopard, but I really miss DIrectory.app, that handy app that lets you create & manage groups in Leopard. It used to be used primarily for managing Wiki & Podcast Producer groups, but it looks like in Snow Leopard all of that has been moved out of Open Directory & given a web interface - still very nice for managing Wiki & PcP groups, but I really liked using Directory.app to manage OD users & groups...
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Just Following up on my earlier post regarding my _id -Gn_ issue...
While looking through some old developer documentation, I found a reference to the groups command which has been "obsoleted" by the id command. I thought I'd give groups a try anyway - and what do you know - it worked! Groups returned exactly what _id -Gn_ should have been returning all this time. Being the sceptic that I am, I also ran the id -Gn command and to my dismay, I found that the _id -Gn_ command was also returning the correct results now....
At this point I decided to log into my test server and run a few more tests. It turns out that just as the groups man page states, groups & _id -Gn_ return the same results... The problem seems to be that after you add a group (with memberships) to Open Directory, there seems to be a delay before the command line utilities (both groups & id ) are able to recognize the group memberships. I'm still not certain how long the delay is, but from my testing, the delay seems to be around 15 minutes . Also, on my test server I was able to force the issue with a restart. That is, after the restart everything worked as expected.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm still working on this issue. I decided to reload the iMac that I'm working on in case I missed something. I setup the LDAP then logged in with a domain account. I use OpenLDAP and not Active Directory. When logging in I received an error about a missing /home filesystem. I forgot to set that up, however, everything worked, I was not locked by things running amok. When I logged out, logged in as root, mounted /home, then logged out and back in with my domain account, things stopped working again.
What I thought was an LDAP issue may actually be an NFS issue.
- 0
Apple Support Community member ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Following up on my post for others to benefit. I solved my LDAP client problem. Snow Leopard is running great as an OpenLDAP client with SSL enabled. The problem was I had LDAP client config misconfigured all this time. With SL, it is more strict about it. I use CAcert for certificates since it is free and I'm on a low budget... The thing is SL LDAP client will silently reject connections to unverified servers. Once I figured out what was going on, I added a TLS_CACERT directive in my /etc/openldap/ldap.conf to point to my CA certificate bundle. Now, SL runs like a dream. I've been running for 3 weeks solid.