[
https://issues.apache.org/jira/browse/ACCUMULO-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613350#comment-13613350
]
Josh Elser commented on ACCUMULO-1161:
--------------------------------------
[~vines] Alright, apparently I was missing, as compared to the 3G
native-standalone example, `trace.principal` and incorrectly had
`trace.password` instead of `trace.login.password`. Fixing those gets me traces
again. Do you see any problems adding a better description (the above kinda
sucks)? In my case, perhaps adding something to the
core/**/AccumuloSecurityException#getDefaultErrorMessage(SecurityErrorCode) to
handle the INSUFFICIENT_PROPERTIES code? Is there a better fix that isn't
initially obvious?
Also, do you think it would be good to look for this case and warn them that
they are specifying the old property and not the new? I just saw something
similar to this in regards to the Hadoop append/sync configuration params.
[~kturner] Can you double check your accumulo-site.xml against one of the
examples to see if you are incorrectly setting a property?
> Recent Traces link no longer works
> ----------------------------------
>
> Key: ACCUMULO-1161
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1161
> Project: Accumulo
> Issue Type: Bug
> Components: monitor
> Reporter: Eric Newton
> Assignee: John Vines
> Priority: Blocker
>
> I just get this stack trace:
> {noformat}
> org.apache.accumulo.core.client.AccumuloSecurityException: Error
> INSUFFICIENT_PROPERTIES for user null - Unknown security exception
> at
> org.apache.accumulo.core.security.handler.ZKAuthenticator.login(ZKAuthenticator.java:39)
> at
> org.apache.accumulo.server.monitor.servlets.trace.Basic.getScanner(Basic.java:80)
> at
> org.apache.accumulo.server.monitor.servlets.trace.Summary.pageBody(Summary.java:131)
> at
> org.apache.accumulo.server.monitor.servlets.BasicServlet.doGet(BasicServlet.java:61)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> {noformat}
--
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
