AFP548 Changing the world one server at a time.

Network accounts no longer available after server reboot

Home › Forums › OS X Server and Client Discussion › Questions and Answers › Network accounts no longer available after server reboot

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #369918
    mgilchrist
    Participant

    Mac OS Server 10.4.10
    Open Directory Master running DNS. DNS is working properly and the system had been up and running for about 4 months without any problems and it had been restarted periodically for software updates, etc. I restarted the server the other day just to do so, and when it came back up, none of my network accounts were able to log into the server. The “Other” option at the login screen is actually missing from the client. I am able to log in locally to the client machines and access network shares with OD accounts, so the usernames and passwords are still functioning as they should, I just can’t use them to log onto the client computers. I have the following errors in my ldap log when I start up a client machine:

    Sep 8 11:40:19 macserver slapd[55]: SASL [conn=20] Failure: GSSAPI Error: Miscellaneous failure (No principal in keytab matches desired name)\n
    Sep 8 11:40:19 macserver slapd[55]: SASL [conn=20] Failure: no user in database\n
    Sep 8 11:40:29 macserver slapd[55]: SASL [conn=24] Failure: GSSAPI Error: Miscellaneous failure (No principal in keytab matches desired name)\n
    Sep 8 11:40:29 macserver slapd[55]: SASL [conn=24] Failure: no user in database\n
    Sep 8 11:40:30 macserver slapd[55]: SASL [conn=28] Failure: GSSAPI Error: Miscellaneous failure (No principal in keytab matches desired name)\n
    Sep 8 11:40:30 macserver slapd[55]: SASL [conn=28] Failure: no user in database\n

    The fix for this is to restore my OD database from the archive backup that I make every other day, but I shouldn’t have to be doing that every time I may need to reboot my server. I did not make any configuration changes to the server before this started happening, so I can’t point to any one thing that would lead to this type of behavior. Any help would be greatly appreciated.

    Thanks

    #369925
    mgilchrist
    Participant

    I plan to further troubleshoot this on Friday when nobody will be accessing the server. I’ll try your suggestion and let you know how it works out.

    #369926
    mgilchrist
    Participant

    Also, isn’t my problem with the record of the client computer itself? I don’t even get the option to try to log into a network account as the “Other” option at the login window is missing. The LDAP errors I detailed occur without me even trying to log into a machine with network credentials.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.