accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1161) Recent Traces link no longer works
Date Tue, 26 Mar 2013 00:47:15 GMT


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:
>             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
> 	at org.apache.accumulo.server.monitor.servlets.trace.Basic.getScanner(
> 	at org.apache.accumulo.server.monitor.servlets.trace.Summary.pageBody(
> 	at org.apache.accumulo.server.monitor.servlets.BasicServlet.doGet(
> 	at javax.servlet.http.HttpServlet.service(
> 	at javax.servlet.http.HttpServlet.service(
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(
> 	at org.mortbay.jetty.handler.ContextHandler.handle(
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(
> 	at org.mortbay.jetty.Server.handle(
> 	at org.mortbay.jetty.HttpConnection.handleRequest(
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
> 	at org.mortbay.jetty.HttpParser.parseNext(
> 	at org.mortbay.jetty.HttpParser.parseAvailable(
> 	at org.mortbay.jetty.HttpConnection.handle(
> 	at$
> 	at org.mortbay.thread.QueuedThreadPool$
> {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:

View raw message