[ https://issues.apache.org/jira/browse/ACCUMULO-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated ACCUMULO-4421: --------------------------------- Attachment: ACCUMULO-4421-1.7.v3-addendum1.patch Here's an addendum on top of your v3 [~busbey]. Still running it through a build, but I think this should fix the present ticket renewal issue. > TraceServer should fall back to GENERIC_KERBEROS_PRINCIPAL when trace > specific kerberos settings are not present > ---------------------------------------------------------------------------------------------------------------- > > Key: ACCUMULO-4421 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4421 > Project: Accumulo > Issue Type: Bug > Components: trace > Affects Versions: 1.7.1, 1.7.2 > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Blocker > Fix For: 1.7.3, 1.8.0 > > Attachments: ACCUMULO-4421-1.7.v3-addendum1.patch, > ACCUMULO-4421-1.7.v3.patch, ACCUMULO-4421.1.patch, ACCUMULO-4421.2.patch > > > Prior to 1.7, the TraceServer always started using the same server utils as > the other daemons. Since a trace server has to talk to Accumulo and that > might involve needing a Kerberos Identity in 1.7+, it was switched to its own > setup. > Currently that setup will default back to GENERIC_KERBEROS_KEYTAB if a keytab > isn't specified for the trace user, but it will simply exit early if there > isn't a principal defined for hte trace user. It should instead default to > the GENERIC_KERBEROS_PRINCIPAL. -- This message was sent by Atlassian JIRA (v6.3.4#6332)