Home › Forums › OS X Server and Client Discussion › Open Directory › KERBEROS-LOGIN-CHECK failure
- This topic has 0 replies, 1 voice, and was last updated 17 years ago by
mosx86.
-
AuthorPosts
-
April 8, 2008 at 10:43 pm #372120
mosx86
ParticipantSo I’m starting to see this more and more often in my Password Service Server Log.
In some cases they will fail for a while and then start to succeed. I’ve seen it with both 10.4 and 10.5 clients (ODmaster and replica are 10.4.11). In the case below, I had to unbind the host and rebind to resolve. The principle for the host exists in the kdc (verified using kadmin– getprinc host$).
ODmaster
Apr 8 2008 14:08:21 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 14:08:21 USER: {slotID, host$} is the current user.
Apr 8 2008 14:08:21 AUTH2: {slotID, host$} CRAM-MD5 authentication succeeded.
Apr 8 2008 14:08:21 QUIT: {slotID, host$} disconnected.
Apr 8 2008 14:20:22 USER: {slotID, host$} is the current user.
Apr 8 2008 14:20:22 AUTH2: {slotID, host$} CRAM-MD5 authentication succeeded.
Apr 8 2008 14:20:22 QUIT: {slotID, host$} disconnected.
Apr 8 2008 14:20:45 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 14:25:37 USER: {slotID, host$} is the current user.
Apr 8 2008 14:25:37 AUTH2: {slotID, host$} CRAM-MD5 authentication succeeded.
Apr 8 2008 14:25:37 QUIT: {slotID, host$} disconnected.
Apr 8 2008 14:25:45 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 14:37:25 USER: {slotID, host$} is the current user.
Apr 8 2008 14:37:25 AUTH2: {slotID, host$} CRAM-MD5 authentication succeeded.
Apr 8 2008 14:37:25 QUIT: {slotID, host$} disconnected.
Apr 8 2008 14:37:33 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.ODreplica
Apr 8 2008 13:00:27 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 13:21:15 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 13:39:34 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 13:45:50 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 14:20:22 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 14:25:36 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 14:37:24 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.
Apr 8 2008 14:43:30 KERBEROS-LOGIN-CHECK: user {slotID, host$} authentication failed.In the Kerberos Admin Log I have the two following rolling errors:
Apr 8 03:15:02 odMaster 700.daily.server.cyrus: Error: /etc/MailServicesOther.plist postfix does not contain a dictionary with key log_rolling_days.
Apr 08 13:27:40 odMaster kadmin.local[29014](info): No dictionary file specified, continuing without one.The Kerberos Server log is empty.
The hosts are bound to the od master with an account we use specifically for directory bindings. What I’m curious about is why would they simply begin failing and succeeding apparently at random. Could this be some kind of corruption on the client machines?
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed