One user generating strange kerberos messages, ...
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have a single user who has a network home folder, and is experiencing daily corruption of his files. He is able to login to the server, but I noticed that his ID is also generating complaints periodically in the logs. I'm wondering if these two things are related, and ideas how to fix them.
Server is 10.6.2; client is 10.5.8
Kerberos logs only complain for this user ("problemuser"):
Feb 04 13:00:35 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:35 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:35 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:00:35 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:00:36 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Feb 04 13:00:36 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): preauth (timestamp) verify failure: Decrypt integrity check failed
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): preauth (timestamp) verify failure: Decrypt integrity check failed
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: PREAUTH_FAILED: [email protected] for krbtgt/[email protected], Decrypt integrity check failed
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: PREAUTH_FAILED: [email protected] for krbtgt/[email protected], Decrypt integrity check failed
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:00:37 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:00:40 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Feb 04 13:00:40 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Feb 04 13:00:40 server4.mycompany.org krb5kdc[80](info): preauth (timestamp) verify failure: Decrypt integrity check failed
Feb 04 13:00:40 server4.mycompany.org krb5kdc[80](info): preauth (timestamp) verify failure: Decrypt integrity check failed
Feb 04 13:00:40 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: PREAUTH_FAILED: [email protected] for krbtgt/[email protected], Decrypt integrity check failed
Feb 04 13:00:40 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.6: PREAUTH_FAILED: [email protected] for krbtgt/[email protected], Decrypt integrity check failed
Feb 04 13:00:41 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:00:41 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:00:41 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:41 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:41 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:00:41 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:00:49 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:00:49 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:00:49 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:49 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:00:49 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:00:49 server4.mycompany.org krb5kdc[80](debug): routing msg not interesting
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.100: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.100: NEEDED_PREAUTH: [email protected] for krbtgt/[email protected], Additional pre-authentication required
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](debug): handling authdata
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](debug): handling authdata
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](debug): .. .. ok
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](debug): .. .. ok
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.100: ISSUE: authtime 1265306463, etypes {rep=18 tkt=16 ses=18}, [email protected] for krbtgt/[email protected]
Feb 04 13:01:03 server4.mycompany.org krb5kdc[80](info): AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.2.100: ISSUE: authtime 1265306463, etypes {rep=18 tkt=16 ses=18}, [email protected] for krbtgt/[email protected]
Feb 04 13:01:05 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:01:05 server4.mycompany.org krb5kdc[80](info): routing socket readable
Feb 04 13:01:05 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
Feb 04 13:01:05 server4.mycompany.org krb5kdc[80](info): got routing msg type 5(RTM_LOSING) v5
applepasswordserver log only complain for this user (problemuser) too:
Feb 4 2010 10:48:46 RSAVALIDATE: success.
Feb 4 2010 10:48:46 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 10:48:46 RSAVALIDATE: success.
Feb 4 2010 10:48:46 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DHX authentication succeeded.
Feb 4 2010 10:48:46 KERBEROS-LOGIN-CHECK: user {0x4b39ec242b8dab1a0000000c0000000c, problemuser} authentication failed.
Feb 4 2010 10:48:47 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 10:48:49 RSAVALIDATE: success.
Feb 4 2010 10:48:49 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DHX authentication succeeded.
Feb 4 2010 10:48:49 KERBEROS-LOGIN-CHECK: user {0x4b39ec242b8dab1a0000000c0000000c, problemuser} authentication failed.
Feb 4 2010 10:48:49 RSAVALIDATE: success.
Feb 4 2010 10:48:49 USER: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} is the current user.
Feb 4 2010 10:48:49 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} CRAM-MD5 authentication succeeded.
Feb 4 2010 10:48:52 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 10:49:11 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 10:54:14 AUTH2: {0x4b2da5de741630530000000800000008, otheruser1} WEBDAV-DIGEST authentication succeeded.
Feb 4 2010 10:54:15 AUTH2: {0x4b2da5de741630530000000800000008, otheruser1} WEBDAV-DIGEST authentication succeeded.
Feb 4 2010 10:54:16 AUTH2: {0x4b2da5de741630530000000800000008, otheruser1} WEBDAV-DIGEST authentication succeeded.
Feb 4 2010 10:54:19 AUTH2: {0x4b2da5de741630530000000800000008, otheruser1} WEBDAV-DIGEST authentication succeeded.
Feb 4 2010 10:54:21 AUTH2: {0x4b2da5de741630530000000800000008, otheruser1} WEBDAV-DIGEST authentication succeeded.
Feb 4 2010 11:01:03 KERBEROS-LOGIN-CHECK: user {0x4b18381b6b8b45670000000300000003, server4.mycompany.org$} is in good standing.
Feb 4 2010 11:01:03 KERBEROS-LOGIN-CHECK: user {0x4b18381b6b8b45670000000300000003, server4.mycompany.org$} authentication succeeded.
Feb 4 2010 11:32:21 AUTH2: {0x4b39ec5b0dcb8c080000000d0000000d, sconnor} DIGEST-MD5 authentication succeeded.
Feb 4 2010 12:54:17 AUTH2: {0x4b2da5de741630530000000800000008, otheruser1} WEBDAV-DIGEST authentication succeeded.
Feb 4 2010 13:00:36 RSAVALIDATE: success.
Feb 4 2010 13:00:36 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 13:00:36 RSAVALIDATE: success.
Feb 4 2010 13:00:36 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DHX authentication succeeded.
Feb 4 2010 13:00:37 KERBEROS-LOGIN-CHECK: user {0x4b39ec242b8dab1a0000000c0000000c, problemuser} authentication failed.
Feb 4 2010 13:00:39 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 13:00:40 RSAVALIDATE: success.
Feb 4 2010 13:00:40 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DHX authentication succeeded.
Feb 4 2010 13:00:40 KERBEROS-LOGIN-CHECK: user {0x4b39ec242b8dab1a0000000c0000000c, problemuser} authentication failed.
Feb 4 2010 13:00:40 RSAVALIDATE: success.
Feb 4 2010 13:00:40 USER: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} is the current user.
Feb 4 2010 13:00:40 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} CRAM-MD5 authentication succeeded.
Feb 4 2010 13:00:46 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 13:01:03 KERBEROS-LOGIN-CHECK: user {0x4b18381b6b8b45670000000300000003, server4.mycompany.org$} is in good standing.
Feb 4 2010 13:01:03 KERBEROS-LOGIN-CHECK: user {0x4b18381b6b8b45670000000300000003, server4.mycompany.org$} authentication succeeded.
Feb 4 2010 13:15:40 AUTH2: {0x4b39ed2d18901f590000001000000010, otheruser2} DIGEST-MD5 authentication succeeded.
Feb 4 2010 13:23:49 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 14:37:57 RSAVALIDATE: success.
Feb 4 2010 14:37:58 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 14:37:58 RSAVALIDATE: success.
Feb 4 2010 14:37:58 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DHX authentication succeeded.
Feb 4 2010 14:37:58 KERBEROS-LOGIN-CHECK: user {0x4b39ec242b8dab1a0000000c0000000c, problemuser} authentication failed.
Feb 4 2010 14:49:29 RSAVALIDATE: success.
Feb 4 2010 14:49:29 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DIGEST-MD5 authentication succeeded.
Feb 4 2010 14:49:30 RSAVALIDATE: success.
Feb 4 2010 14:49:30 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DHX authentication succeeded.
Feb 4 2010 14:49:30 KERBEROS-LOGIN-CHECK: user {0x4b39ec242b8dab1a0000000c0000000c, problemuser} authentication failed.
Feb 4 2010 14:49:32 RSAVALIDATE: success.
Feb 4 2010 14:49:32 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} DHX authentication succeeded.
Feb 4 2010 14:49:32 KERBEROS-LOGIN-CHECK: user {0x4b39ec242b8dab1a0000000c0000000c, problemuser} authentication failed.
Feb 4 2010 14:49:32 RSAVALIDATE: success.
Feb 4 2010 14:49:32 USER: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} is the current user.
Feb 4 2010 14:49:32 AUTH2: {0x4b39ec242b8dab1a0000000c0000000c, problemuser} CRAM-MD5 authentication succeeded.
Feb 4 2010 14:54:18 AUTH2: {0x4b2da5de741630530000000800000008, otheruser1} WEBDAV-DIGEST authentication succeeded.
1 reply
Sign in or join Beachball Help to reply.
- 0