You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/07/17 02:36:48 UTC
[jira] [Commented] (AMBARI-2665) Zookeeper throws an stacktrace on
Ambari secure cluster
[ https://issues.apache.org/jira/browse/AMBARI-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710542#comment-13710542 ]
Sumit Mohanty commented on AMBARI-2665:
---------------------------------------
LGTM, +1
> 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
>
> Attachments: AMBARI-2665-1.patch, AMBARI-2665.patch
>
>
> Zookeeper tests throwing following exceptions on Ambari secure cluster-
> watcher=org.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$ClientCallbackHandler@437] - Could not login: the client is being asked for a password, but the Zookeeper client code does not currently support obtaining a password from the user. Make sure that the client is configured to use a ticket cache (using the JAAS configuration setting 'useTicketCache=true)' 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 this Zookeeper client using the command 'kinit <princ>' (where <princ> is the name of the client's Kerberos principal). If the latter, do 'kinit -k -t <keytab> <princ>' (where <princ> is the name of the Kerberos principal, and <keytab> is the location of the keytab file). After manually refreshing your cache, restart this client. If you continue to see this message after manually refreshing your cache, ensure that your KDC host's clock is in sync with 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 null!
> 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.EncryptionKey.<init>(EncryptionKey.java:203)
> 2013-07-12 04:57:12,957|beaver.machine|INFO|at sun.security.krb5.EncryptionKey.acquireSecretKeys(EncryptionKey.java:180)
> 2013-07-12 04:57:12,958|beaver.machine|INFO|at sun.security.krb5.EncryptionKey.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.NativeMethodAccessorImpl.invoke0(Native Method)
> 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 2013-07-12 04:57:12,960|beaver.machine|INFO|at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2013-07-12 04:57:12,960|beaver.machine|INFO|at java.lang.reflect.Method.invoke(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.AccessController.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.<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.<init>(ZooKeeperSaslClient.java:104)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira