You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/03/03 18:28:05 UTC

[jira] [Created] (ACCUMULO-3636) Can't view recent traces in monitor with kerberos/sasl enabled

Josh Elser created ACCUMULO-3636:
------------------------------------

             Summary: Can't view recent traces in monitor with kerberos/sasl enabled
                 Key: ACCUMULO-3636
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3636
             Project: Accumulo
          Issue Type: Bug
          Components: monitor
            Reporter: Josh Elser
            Assignee: Josh Elser
            Priority: Blocker
             Fix For: 1.7.0


{noformat}
org.apache.accumulo.core.client.AccumuloException: java.lang.IllegalArgumentException: Cannot determine SASL mechanism for token class: class org.apache.accumulo.core.client.security.tokens.PasswordToken
	at org.apache.accumulo.core.client.impl.ServerClient.execute(ServerClient.java:66)
	at org.apache.accumulo.core.client.impl.ConnectorImpl.<init>(ConnectorImpl.java:67)
	at org.apache.accumulo.server.client.HdfsZooInstance.getConnector(HdfsZooInstance.java:159)
	at org.apache.accumulo.monitor.servlets.trace.Basic.getScanner(Basic.java:98)
	at org.apache.accumulo.monitor.servlets.trace.Summary.pageBody(Summary.java:148)
	at org.apache.accumulo.monitor.servlets.BasicServlet.doGet(BasicServlet.java:66)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:738)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:551)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:219)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1111)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:478)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1045)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
	at org.eclipse.jetty.server.Server.handle(Server.java:462)
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:279)
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:232)
	at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:534)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Cannot determine SASL mechanism for token class: class org.apache.accumulo.core.client.security.tokens.PasswordToken
	at org.apache.accumulo.core.rpc.SaslConnectionParams.updateFromToken(SaslConnectionParams.java:157)
	at org.apache.accumulo.core.rpc.SaslConnectionParams.<init>(SaslConnectionParams.java:145)
	at org.apache.accumulo.core.rpc.SaslConnectionParams.<init>(SaslConnectionParams.java:135)
	at org.apache.accumulo.core.client.impl.ClientContext.getSaslParams(ClientContext.java:139)
	at org.apache.accumulo.core.client.impl.ThriftTransportKey.<init>(ThriftTransportKey.java:42)
	at org.apache.accumulo.core.client.impl.ServerClient.getConnection(ServerClient.java:134)
	at org.apache.accumulo.core.client.impl.ServerClient.getConnection(ServerClient.java:116)
	at org.apache.accumulo.core.client.impl.ServerClient.getConnection(ServerClient.java:112)
	at org.apache.accumulo.core.client.impl.ServerClient.executeRaw(ServerClient.java:94)
	at org.apache.accumulo.core.client.impl.ServerClient.execute(ServerClient.java:60)
	... 23 more
{noformat}

Looks like the monitor is trying to use a password token to fetch traces regardless of the "mode" of RPC in use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)