incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <>
Subject [jira] [Commented] (AMBARI-2678) Zookeeper smoke does not fail for exceptions thrown by zkCli
Date Mon, 22 Jul 2013 17:42:48 GMT


Sumit Mohanty commented on AMBARI-2678:

LGTM, +1.

I have some concerns if it will detect false negatives but can't think of any.
> Zookeeper smoke does not fail for exceptions thrown by zkCli
> ------------------------------------------------------------
>                 Key: AMBARI-2678
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.5
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.4.0
>         Attachments: AMBARI-2678.patch
> I am noticing 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: java.lang.IllegalArgumentException:
EncryptionKey: Key bytes cannot be null!
> 2013-07-12 04:57:12,957|beaver.machine|INFO|at<init>(
> 2013-07-12 04:57:12,957|beaver.machine|INFO|at
> 2013-07-12 04:57:12,958|beaver.machine|INFO|at
> 2013-07-12 04:57:12,958|beaver.machine|INFO|at
> 2013-07-12 04:57:12,959|beaver.machine|INFO|at
> 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> 2013-07-12 04:57:12,959|beaver.machine|INFO|at sun.reflect.NativeMethodAccessorImpl.invoke(
> 2013-07-12 04:57:12,960|beaver.machine|INFO|at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 2013-07-12 04:57:12,960|beaver.machine|INFO|at java.lang.reflect.Method.invoke(
> 2013-07-12 04:57:12,960|beaver.machine|INFO|at
> 2013-07-12 04:57:12,961|beaver.machine|INFO|at$000(
> 2013-07-12 04:57:12,961|beaver.machine|INFO|at$
> 2013-07-12 04:57:12,961|beaver.machine|INFO|at
> 2013-07-12 04:57:12,962|beaver.machine|INFO|at
> 2013-07-12 04:57:12,962|beaver.machine|INFO|at
> 2013-07-12 04:57:12,962|beaver.machine|INFO|at org.apache.zookeeper.Login.login(
> 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.Login.<init>(
> 2013-07-12 04:57:12,963|beaver.machine|INFO|at org.apache.zookeeper.client.ZooKeeperSaslClient.createSaslClient(
> 2013-07-12 04:57:12,964|beaver.machine|INFO|at org.apache.zookeeper.client.ZooKeeperSaslClient.<init>(

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:

View raw message