accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bus...@apache.org
Subject [6/6] accumulo git commit: Merge branch '1.8'
Date Fri, 07 Oct 2016 05:29:23 GMT
Merge branch '1.8'


Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/9dddeed8
Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/9dddeed8
Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/9dddeed8

Branch: refs/heads/master
Commit: 9dddeed885d8ae4c6ba34eca561dcdb747131d68
Parents: 1c218de 91269bf
Author: Sean Busbey <busbey@cloudera.com>
Authored: Fri Oct 7 00:28:21 2016 -0500
Committer: Sean Busbey <busbey@cloudera.com>
Committed: Fri Oct 7 00:28:21 2016 -0500

----------------------------------------------------------------------
 docs/src/main/asciidoc/chapters/kerberos.txt | 104 +++++++++++++++++++++-
 1 file changed, 101 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/accumulo/blob/9dddeed8/docs/src/main/asciidoc/chapters/kerberos.txt
----------------------------------------------------------------------
diff --cc docs/src/main/asciidoc/chapters/kerberos.txt
index 7817c8d,bfb7cb7..48553b7
--- a/docs/src/main/asciidoc/chapters/kerberos.txt
+++ b/docs/src/main/asciidoc/chapters/kerberos.txt
@@@ -558,5 -621,40 +621,40 @@@ Caused by: org.apache.thrift.transport.
  on, is extremely important when negotiating an SASL connection. This problem commonly arises
when the Accumulo
  servers are not configured to listen on the address denoted by their FQDN.
  
 -The values in the Accumulo "hosts" files (In +$ACCUMULO_CONF_DIR+: +masters+, +monitors+,
+slaves+, +tracers+,
 +The values in the Accumulo "hosts" files (In +$ACCUMULO_CONF_DIR+: +masters+, +monitors+,
+tservers+, +tracers+,
  and +gc+) should match the instance componentof the Kerberos server principal (e.g. +host+
in +accumulo/host@EXAMPLE.COM+).
+ 
+ *Q*: After configuring my system for Kerberos, server processes come up normally and I can
interact with the system. However,
+ when I attempt to use the "Recent Traces" page on the Monitor UI I get a stacktrace similar
to:
+ 
+ ----
+                                                                          java.lang.AssertionError:
AuthenticationToken should not be null
+                                                                    at org.apache.accumulo.monitor.servlets.trace.Basic.getScanner(Basic.java:139)
+                                                                   at org.apache.accumulo.monitor.servlets.trace.Summary.pageBody(Summary.java:164)
+                                                                   at org.apache.accumulo.monitor.servlets.BasicServlet.doGet(BasicServlet.java:63)
+                                                                            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.handler.ScopedHandler.handle(ScopedHandler.java:143)
+                                                                    at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
+                                                                 at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
+                                                                 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)
+ 
+ ----
+ 
+ *A*: This indicates that the Monitor has not been able to successfully log in a client-side
user to read from the +trace+ table. Accumulo allows the TraceServer to rely on the property
+general.kerberos.keytab+ as a fallback when logging in the trace user if the +trace.token.property.keytab+
property isn't defined. Some earlier versions of Accumulo did not do this same fallback for
the Monitor's use of the trace user. The end result is that if you configure +general.kerberos.keytab+
and not +trace.token.property.keytab+ you will end up with a system that properly logs trace
information but can't view it.
+ 
+ Ensure you have set +trace.token.property.keytab+ to point to a keytab for the principal
defined in +trace.user+ in the +accumulo-site.xml+ file for the Monitor, since that should
work in all versions of Accumulo.


Mime
View raw message