You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/02/25 00:17:00 UTC
[jira] [Updated] (HADOOP-18645) Provide keytab file key name with ServiceStateException
[ https://issues.apache.org/jira/browse/HADOOP-18645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HADOOP-18645:
------------------------------------
Labels: pull-request-available (was: )
> Provide keytab file key name with ServiceStateException
> -------------------------------------------------------
>
> Key: HADOOP-18645
> URL: https://issues.apache.org/jira/browse/HADOOP-18645
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
>
>
> {code:java}
> util.ExitUtil - Exiting with status 1: org.apache.hadoop.service.ServiceStateException: java.io.IOException: Running in secure mode, but config doesn't have a keytab
> 1: org.apache.hadoop.service.ServiceStateException: java.io.IOException: Running in secure mode, but config doesn't have a keytab
> at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:264)
> ..
> ..
> {code}
>
>
> When multiple downstreamers use different configs to present the same keytab file, if one of the config key gets missing or overridden as part of config generators, it becomes bit confusing for operators to realize which config is missing for a particular service, especially when keytab file value is already present with different config.
> It would be nice to report config key with the stacktrace error message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org