Hi Patrick, I've posted some details on ZOOKEEPER-1437. I didn't get a chance to post a demo yet though. On May 25, 2012 2:07 AM, "Patrick Hunt" <[email protected]> wrote:
> Seems the client is sending a 0 size token in this case: "Size of > client SASL token: 0" > > Eugene any insight? > > Patrick > > On Fri, May 18, 2012 at 8:40 AM, Antonio Mauriello <[email protected]> > wrote: > > Hi, > > > > In a specif scenario where the Zookeeper Server get killed and restarted > > while a java zk client is connected I get the following in the log: > (Please > > note the Error at bottom) > > > > [main-SendThread(localhost:60728)] DEBUG > > org.apache.zookeeper.client.ZooKeeperSaslClient - > > ClientCnxn:sendSaslPacket:length=0 > > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:60728] DEBUG > > org.apache.zookeeper.server.ZooKeeperServer - Responding to client SASL > > token. > > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:60728] DEBUG > > org.apache.zookeeper.server.ZooKeeperServer - Size of client SASL > token: 0 > > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:60728] DEBUG > > org.apache.zookeeper.server.ZooKeeperServer - Size of server SASL > > response: 101 > > [main-SendThread(localhost:60728)] DEBUG org.apache.zookeeper.ClientCnxn > - > > Reading reply sessionid:0x1376082ca4f0000, packet:: clientPath:null > > serverPath:null finished:false header:: 9,102 replyHeader:: 9,0,0 > > request:: response:: > > > #7265616c6d3d227a6b2d7361736c2d6d6435222c6e6f6e63653d22717a485932306a56743534552f483668315837734e2b4b56656e4c335772666458716f6468336247222c636861727365743d7574662d382c616c676f726974686d3d6d64352d73657373 > > 2012-05-18 15:14:16,908 [SyncThread:0] DEBUG > > org.apache.zookeeper.server.FinalRequestProcessor - Processing request:: > > sessionid:0x1376082ca4f0000 type:ping cxid:0xfffffffffffffffe > > zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a > > 2012-05-18 15:14:16,908 [SyncThread:0] DEBUG > > org.apache.zookeeper.server.FinalRequestProcessor - > > sessionid:0x1376082ca4f0000 type:ping cxid:0xfffffffffffffffe > > zxid:0xfffffffffffffffe txntype:unknown reqpath:n/a > > > > [main-EventThread] DEBUG org.apache.zookeeper.client.ZooKeeperSaslClient > - > > ServerSaslResponseCallback(): using empty data[] as server response > > (length=0) > > [main-EventThread] DEBUG org.apache.zookeeper.client.ZooKeeperSaslClient > - > > saslToken (server) length: 0 > > [main-EventThread] DEBUG org.apache.zookeeper.client.ZooKeeperSaslClient > - > > saslClient.evaluateChallenge(len=0) > > [main-EventThread] ERROR org.apache.zookeeper.client.ZooKeeperSaslClient > - > > An error: (java.security.PrivilegedActionException: > > javax.security.sasl.SaslException: DIGEST-MD5: Digest-challenge format > > violation: algorithm directive missing) occurred when evaluating > Zookeeper > > Quorum Member's received SASL token. Zookeeper Client will go to > > AUTH_FAILED state. > > [main-EventThread] ERROR org.apache.zookeeper.client.ZooKeeperSaslClient > - > > SASL authentication failed using login context 'null'. > > > > > > I was wondering why the "empty data[]" is expected since it always drives > > in my case to a SASL authentication failed. > > > > > > I know this is not the correct set up but at moment only one Zk server is > > set up. Not sure if this is actually causing the issue. > > > > > > Thanks > > Antonio >
