5 Replies Latest reply: Dec 7, 2012 1:45 PM by mecg
Sascha Holesch Level 1 Level 1 (0 points)

Hi! We are using a setup of a 10.7.1 OS X Server and lots of 10.7.1 OS X Clients.

 

Today one of my users called me that he is not able to login anymore. I checked, and when he wants to login the sync is working, then the screen flashes to grey for a short time and throws us back into the login window.

 

I thought it might be an error with the syncing and tried removing the ~./FileSync and ~/Library/FileSync folders on both the client and the server, but this didn't have any effect. The user can access the other services we're running (iChat, AddressBook, Calendar, Wiki).

 

All of my other users can login without problems at all.

 

I'd appreciate it very much if someone could tell me how to resolve this or give some hints.

 

Thank you very much in advance,

 

Sascha Holesch

Eyes, JAPAN Co. Ltd.


Mac OS X (10.7.1)
  • 1. Re: Mobile Home user cannot login
    Stress Test Level 4 Level 4 (1,265 points)

    Have you checked the logs on the Client with a local admin user?

  • 2. Re: Mobile Home user cannot login
    Sascha Holesch Level 1 Level 1 (0 points)

    The content of /var/log/system.log is as followed (I just edited the username), but I can't really get a hint from it:

    Sep 27 10:38:52 exp135 SecurityAgent[414]: User info context values set for myuser

    Sep 27 10:38:52 exp135 SecurityAgent[414]: Login Window login proceeding

    Sep 27 10:38:54 exp135 loginwindow[405]: Login Window - Returned from Security Agent

    Sep 27 10:38:54 exp135 loginwindow[405]: USER_PROCESS: 405 console

    Sep 27 10:38:55 exp135 ReportCrash[442]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.

    Sep 27 10:38:57 exp135 parentalcontrolsd[440]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)

    Sep 27 10:38:57: --- last message repeated 1 time ---

    Sep 27 10:38:57 exp135 com.apple.launchd[1] (com.apple.loginwindow[405]): Job appears to have crashed: Segmentation fault: 11

    Sep 27 10:38:57 exp135 loginwindow[443]: Login Window Application Started

    Sep 27 10:38:57 exp135 parentalcontrolsd[440]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)

    Sep 27 10:38:57 exp135 loginwindow[443]: **DMPROXY** Found `/System/Library/CoreServices/DMProxy'.

    Sep 27 10:38:57 exp135 loginwindow[443]: Login Window Started Security Agent

    Sep 27 10:38:57 exp135 com.apple.launchctl.LoginWindow[447]: com.apple.findmymacmessenger: Already loaded

    Sep 27 10:38:57 exp135 WindowServer[445]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

    Sep 27 10:38:57 exp135 loginwindow[443]: kCGErrorFailure: CGSPackagesGetWorkspaceType: couldn't get workspace type

    Sep 27 10:38:57 exp135 loginwindow[443]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

    Sep 27 10:38:57 exp135 SecurityAgent[452]: Echo enabled

    Sep 27 10:38:57 exp135 ReportCrash[442]: Saved crash report for loginwindow[405] version ??? (???) to /Library/Logs/DiagnosticReports/loginwindow_2011-09-27-103857_localhost.crash

    Sep 27 10:38:58 exp135 ReportCrash[442]: Removing excessive log: /Library/Logs/DiagnosticReports/loginwindow_2011-09-25-122131_localhost.crash

    Sep 27 10:38:58 exp135 SecurityAgent[452]: kCGErrorFailure: CGSPackagesGetWorkspaceType: couldn't get workspace type

    Sep 27 10:38:58 exp135 SecurityAgent[452]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.

    Sep 27 10:38:59 exp135 com.apple.launchd.peruser.92[427]: Background: Bug: launchd_core_logic.c:10063 (24984):0

    Sep 27 10:38:59 exp135 com.apple.launchd.peruser.92[427]: Background: This API can only be used by a process running within an Aqua session.

    Also a crashlog of loginwindow and HomeSync will be created. Both with

     

    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000001c

  • 3. Re: Mobile Home user cannot login
    Sascha Holesch Level 1 Level 1 (0 points)

    After contacting the support line and having a long phone call with them, we tried a variety of steps to fix the issue.

     

    Turns out that, after deleting the home directory (on the client as well as on the server) the user is able to login again. However, the sync does not work. It will break with the error message that "(null)'s home directory can not be found. The home directory has to be created manually in the Workgroup Manager under the "Accounts" tab. Pick the user, select the tab "Home", chose the afp://.... link, push "Create Home Now" on the bottom of the window and Save. This will create the user's home directory and thus will be able to login and sync his home to the server.

     

    This has worked for us so far for every user we encountered.

  • 4. Re: Mobile Home user cannot login
    mecg Level 1 Level 1 (0 points)

    Found the answer I was not looking for, however I am glad I found the fix. Unfortunately backing up a users data wiping it on server/client machine putting it back updating to 10.7.5 was the fix, leaving them at 10.7.4 never fixed it. 10.7.5 did have server support software put in the updates info. Of what it exactly does who knows, apple didn't put any information on that.

    If anybody has any other way of doing this or a quicker fix without having to wipe server/client information would be good to know. I have tried: Machelp mate (sometimes it helped, rarely). Any other information would be helpful. Thanks for the related posts

  • 5. Re: Mobile Home user cannot login
    mecg Level 1 Level 1 (0 points)

    Found the answer I was not looking for, however I am glad I found the fix. Unfortunately backing up a users data wiping it on server/client machine putting it back updating to 10.7.5 was the fix, leaving them at 10.7.4 never fixed it. 10.7.5 did have server support software put in the updates info. Of what it exactly does who knows, apple didn't put any information on that.

    If anybody has any other way of doing this or a quicker fix without having to wipe server/client information would be good to know. I have tried: Machelp mate (sometimes it helped, rarely). Any other information would be helpful. Thanks for the related posts