Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4E25C10EBB for ; Wed, 17 Jul 2013 00:18:50 +0000 (UTC) Received: (qmail 24465 invoked by uid 500); 17 Jul 2013 00:18:50 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 24429 invoked by uid 500); 17 Jul 2013 00:18:50 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 24386 invoked by uid 99); 17 Jul 2013 00:18:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jul 2013 00:18:50 +0000 Date: Wed, 17 Jul 2013 00:18:49 +0000 (UTC) From: "Siddharth Wagle (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-2665) Zookeeper throws an stacktrace on Ambari secure cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-2665?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-2665: ------------------------------------ Description:=20 Zookeeper tests throwing following exceptions on Ambari secure cluster- watcher=3Dorg.apache.zookeeper.ZooKeeperMain$MyWatcher@67ad77a7 2013-07-12 04:57:12,600|beaver.machine|INFO|2013-07-12 04:57:12,596 - WARN = [main-SendThread(ip-10-164-35-39.ec2.internal:2181):ZooKeeperSaslClient$Cl= ientCallbackHandler@437] - Could not login: the client is being asked for a= password, but the Zookeeper client code does not currently support obtaini= ng a password from the user. Make sure that the client is configured to use= a ticket cache (using the JAAS configuration setting 'useTicketCache=3Dtru= e)' and restart the client. If you still get this message after that, the T= GT in the ticket cache has expired and must be manually refreshed. To do so= , first determine if you are using a password or a keytab. If the former, r= un kinit in a Unix shell in the environment of the user who is running this= Zookeeper client using the command 'kinit ' (where is the n= ame of the client's Kerberos principal). If the latter, do 'kinit -k -t ' (where is the name of the Kerberos principal, and is the location of the keytab file). After manually refreshing your = cache, restart this client. If you continue to see this message after manua= lly refreshing your cache, ensure that your KDC host's clock is in sync wit= h this host's clock. 2013-07-12 04:57:12,956|beaver.machine|INFO|2013-07-12 04:57:12,955 - WARN = [main-SendThread(ip-10-164-35-39.ec2.internal:2181):ClientCnxn$SendThread@= 949] - SASL configuration failed: javax.security.auth.login.LoginException:= java.lang.IllegalArgumentException: EncryptionKey: Key bytes cannot be nul= l! 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.Encryption= Key.(EncryptionKey.java:203) 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.Encryption= Key.acquireSecretKeys(EncryptionKey.java:180) 2013-07-12 04:57:12,958|beaver.machine|INFO|at sun.security.krb5.Encryption= Key.acquireSecretKeys(EncryptionKey.java:159) 2013-07-12 04:57:12,958|beaver.machine|INFO|at com.sun.security.auth.module= .Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:656) 2013-07-12 04:57:12,959|beaver.machine|INFO|at com.sun.security.auth.module= .Krb5LoginModule.login(Krb5LoginModule.java:542) 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAcce= ssorImpl.invoke0(Native Method) 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAcce= ssorImpl.invoke(NativeMethodAccessorImpl.java:39) 2013-07-12 04:57:12,960|beaver.machine|INFO|at sun.reflect.DelegatingMethod= AccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2013-07-12 04:57:12,960|beaver.machine|INFO|at java.lang.reflect.Method.inv= oke(Method.java:597) 2013-07-12 04:57:12,960|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.invoke(LoginContext.java:769) 2013-07-12 04:57:12,961|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.access$000(LoginContext.java:186) 2013-07-12 04:57:12,961|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext$4.run(LoginContext.java:683) 2013-07-12 04:57:12,961|beaver.machine|INFO|at java.security.AccessControll= er.doPrivileged(Native Method) 2013-07-12 04:57:12,962|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.invokePriv(LoginContext.java:680) 2013-07-12 04:57:12,962|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.login(LoginContext.java:579) 2013-07-12 04:57:12,962|beaver.machine|INFO|at org.apache.zookeeper.Login.l= ogin(Login.java:292) 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.Login.<= init>(Login.java:93) 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.client.= ZooKeeperSaslClient.createSaslClient(ZooKeeperSaslClient.java:198) 2013-07-12 04:57:12,964|beaver.machine|INFO|at org.apache.zookeeper.client.= ZooKeeperSaslClient.(ZooKeeperSaslClient.java:104) was: I am noticing Zookeeper tests throwing following exceptions on Ambari secur= e cluster- watcher=3Dorg.apache.zookeeper.ZooKeeperMain$MyWatcher@67ad77a7 2013-07-12 04:57:12,600|beaver.machine|INFO|2013-07-12 04:57:12,596 - WARN = [main-SendThread(ip-10-164-35-39.ec2.internal:2181):ZooKeeperSaslClient$Cl= ientCallbackHandler@437] - Could not login: the client is being asked for a= password, but the Zookeeper client code does not currently support obtaini= ng a password from the user. Make sure that the client is configured to use= a ticket cache (using the JAAS configuration setting 'useTicketCache=3Dtru= e)' and restart the client. If you still get this message after that, the T= GT in the ticket cache has expired and must be manually refreshed. To do so= , first determine if you are using a password or a keytab. If the former, r= un kinit in a Unix shell in the environment of the user who is running this= Zookeeper client using the command 'kinit ' (where is the n= ame of the client's Kerberos principal). If the latter, do 'kinit -k -t ' (where is the name of the Kerberos principal, and is the location of the keytab file). After manually refreshing your = cache, restart this client. If you continue to see this message after manua= lly refreshing your cache, ensure that your KDC host's clock is in sync wit= h this host's clock. 2013-07-12 04:57:12,956|beaver.machine|INFO|2013-07-12 04:57:12,955 - WARN = [main-SendThread(ip-10-164-35-39.ec2.internal:2181):ClientCnxn$SendThread@= 949] - SASL configuration failed: javax.security.auth.login.LoginException:= java.lang.IllegalArgumentException: EncryptionKey: Key bytes cannot be nul= l! 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.Encryption= Key.(EncryptionKey.java:203) 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.Encryption= Key.acquireSecretKeys(EncryptionKey.java:180) 2013-07-12 04:57:12,958|beaver.machine|INFO|at sun.security.krb5.Encryption= Key.acquireSecretKeys(EncryptionKey.java:159) 2013-07-12 04:57:12,958|beaver.machine|INFO|at com.sun.security.auth.module= .Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:656) 2013-07-12 04:57:12,959|beaver.machine|INFO|at com.sun.security.auth.module= .Krb5LoginModule.login(Krb5LoginModule.java:542) 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAcce= ssorImpl.invoke0(Native Method) 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAcce= ssorImpl.invoke(NativeMethodAccessorImpl.java:39) 2013-07-12 04:57:12,960|beaver.machine|INFO|at sun.reflect.DelegatingMethod= AccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 2013-07-12 04:57:12,960|beaver.machine|INFO|at java.lang.reflect.Method.inv= oke(Method.java:597) 2013-07-12 04:57:12,960|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.invoke(LoginContext.java:769) 2013-07-12 04:57:12,961|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.access$000(LoginContext.java:186) 2013-07-12 04:57:12,961|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext$4.run(LoginContext.java:683) 2013-07-12 04:57:12,961|beaver.machine|INFO|at java.security.AccessControll= er.doPrivileged(Native Method) 2013-07-12 04:57:12,962|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.invokePriv(LoginContext.java:680) 2013-07-12 04:57:12,962|beaver.machine|INFO|at javax.security.auth.login.Lo= ginContext.login(LoginContext.java:579) 2013-07-12 04:57:12,962|beaver.machine|INFO|at org.apache.zookeeper.Login.l= ogin(Login.java:292) 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.Login.<= init>(Login.java:93) 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.client.= ZooKeeperSaslClient.createSaslClient(ZooKeeperSaslClient.java:198) 2013-07-12 04:57:12,964|beaver.machine|INFO|at org.apache.zookeeper.client.= ZooKeeperSaslClient.(ZooKeeperSaslClient.java:104) Console logs at - http://10.10.11.125/home/jenkins/qe-artifacts/ambari_rhel= -6.3_secure_1373589723_hiveoozie_mysql/zookeeper-1373620471/console.log Dont see such exceptions on gs installed clusters. =20 > Zookeeper throws an stacktrace on Ambari secure cluster > ------------------------------------------------------- > > Key: AMBARI-2665 > URL: https://issues.apache.org/jira/browse/AMBARI-2665 > Project: Ambari > Issue Type: Bug > Components: agent > Affects Versions: 1.2.5 > Reporter: Siddharth Wagle > Assignee: Siddharth Wagle > Fix For: 1.2.5 > > > Zookeeper tests throwing following exceptions on Ambari secure cluster- > watcher=3Dorg.apache.zookeeper.ZooKeeperMain$MyWatcher@67ad77a7 > 2013-07-12 04:57:12,600|beaver.machine|INFO|2013-07-12 04:57:12,596 - WAR= N [main-SendThread(ip-10-164-35-39.ec2.internal:2181):ZooKeeperSaslClient$= ClientCallbackHandler@437] - Could not login: the client is being asked for= a password, but the Zookeeper client code does not currently support obtai= ning a password from the user. Make sure that the client is configured to u= se a ticket cache (using the JAAS configuration setting 'useTicketCache=3Dt= rue)' and restart the client. If you still get this message after that, the= TGT in the ticket cache has expired and must be manually refreshed. To do = so, first determine if you are using a password or a keytab. If the former,= run kinit in a Unix shell in the environment of the user who is running th= is Zookeeper client using the command 'kinit ' (where is the= name of the client's Kerberos principal). If the latter, do 'kinit -k -t <= keytab> ' (where is the name of the Kerberos principal, and = is the location of the keytab file). After manually refreshing you= r cache, restart this client. If you continue to see this message after man= ually refreshing your cache, ensure that your KDC host's clock is in sync w= ith this host's clock. > 2013-07-12 04:57:12,956|beaver.machine|INFO|2013-07-12 04:57:12,955 - WAR= N [main-SendThread(ip-10-164-35-39.ec2.internal:2181):ClientCnxn$SendThrea= d@949] - SASL configuration failed: javax.security.auth.login.LoginExceptio= n: java.lang.IllegalArgumentException: EncryptionKey: Key bytes cannot be n= ull! > 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.Encrypti= onKey.(EncryptionKey.java:203) > 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.Encrypti= onKey.acquireSecretKeys(EncryptionKey.java:180) > 2013-07-12 04:57:12,958|beaver.machine|INFO|at sun.security.krb5.Encrypti= onKey.acquireSecretKeys(EncryptionKey.java:159) > 2013-07-12 04:57:12,958|beaver.machine|INFO|at com.sun.security.auth.modu= le.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:656) > 2013-07-12 04:57:12,959|beaver.machine|INFO|at com.sun.security.auth.modu= le.Krb5LoginModule.login(Krb5LoginModule.java:542) > 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAc= cessorImpl.invoke0(Native Method) > 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAc= cessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 2013-07-12 04:57:12,960|beaver.machine|INFO|at sun.reflect.DelegatingMeth= odAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 2013-07-12 04:57:12,960|beaver.machine|INFO|at java.lang.reflect.Method.i= nvoke(Method.java:597) > 2013-07-12 04:57:12,960|beaver.machine|INFO|at javax.security.auth.login.= LoginContext.invoke(LoginContext.java:769) > 2013-07-12 04:57:12,961|beaver.machine|INFO|at javax.security.auth.login.= LoginContext.access$000(LoginContext.java:186) > 2013-07-12 04:57:12,961|beaver.machine|INFO|at javax.security.auth.login.= LoginContext$4.run(LoginContext.java:683) > 2013-07-12 04:57:12,961|beaver.machine|INFO|at java.security.AccessContro= ller.doPrivileged(Native Method) > 2013-07-12 04:57:12,962|beaver.machine|INFO|at javax.security.auth.login.= LoginContext.invokePriv(LoginContext.java:680) > 2013-07-12 04:57:12,962|beaver.machine|INFO|at javax.security.auth.login.= LoginContext.login(LoginContext.java:579) > 2013-07-12 04:57:12,962|beaver.machine|INFO|at org.apache.zookeeper.Login= .login(Login.java:292) > 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.Login= .(Login.java:93) > 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.clien= t.ZooKeeperSaslClient.createSaslClient(ZooKeeperSaslClient.java:198) > 2013-07-12 04:57:12,964|beaver.machine|INFO|at org.apache.zookeeper.clien= t.ZooKeeperSaslClient.(ZooKeeperSaslClient.java:104) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira