Apps are really slow to open on bound machines

[jiamei]

Hi Guys,

i have a problem that’s quite a head-scratcher. I’m assisting a departmental tech at the school I work for with a funny OD problem. There are three problems, and I am not sure if they are related:

1) Initially the problem was that new users that were created were unable to log in, yet users that were already in OD were able to log in fine. We found a workaround by switching the affected accounts’ password types from OD to crypt, then back from crypt to OD.

2) Users can not access file shares in AFP if the auth type is set to kerberos, yet standard works fine. I tried rebuilding the kerberos DB, but the issue still persists.

3) Now the problem is that any machines that were bound to OD take a really long time logging in and opening apps. the login window will hang at the first letter of input before continuing with the rest after 30 seconds or so. After the user logs in, apps take 20 bounces or so before they open (e.g. System Prefs or Safari). the accounts are portable homes. the apps are local to the machine.

All the machines are 2008 imacs running 10.5.7 and the server is 10.5.7 on a Xserve Xeon.

Does anyone know where I can get started to resolve these issues? Thanks!

[arekdreyer]

For authentication problems, I’d take a look on the server at the following logs

/Library/Logs/PasswordService/ApplePasswordServer.Server.log

/var/log/krb5kdc/kdc.log

An easy way to look at those logs is with Server Admin.
Select Open Directory in the left list of servers and services, click Logs in the toolbar, then use the pop-up menu of logs at the bottom of the window.

If you see a message like “KERBEROS-LOGIN-CHECK: no principal ([email protected])” then the kerberos principal didn’t get created.

Check your /Library/Preferences/com.apple.AppleFileServer.plist to see that the value of the kerberosPrincipal is. It should not refer to the LKDC.

For the long login problem, I’d open an SSH connection to the computer as an admin user, use “tail -f /var/log/system.log” to see if there is interesting logged. Then I’d move on to DirectoryService debugging. See http://www.mactech.com/articles/mactech/Vol.23/23.06/TroubleshootingDirectoryServices/index.html

[Author]

Posts