[
https://issues.apache.org/jira/browse/HADOOP-12777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135925#comment-15135925
]
Xiaoyu Yao commented on HADOOP-12777:
-------------------------------------
The document says that "The password file is looked up in the Hadoop’s
configuration directory via the classpath." I would assume your file in
"Hadoop's configuration directory" is already part of the hadoop classpath. Can
check "hadoop claasspath --glob" to confirm?
> keystore password file is not looked up in Hadoop's configuration directory.
> -----------------------------------------------------------------------------
>
> Key: HADOOP-12777
> URL: https://issues.apache.org/jira/browse/HADOOP-12777
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 2.7.2, 3.0.0
> Reporter: Takashi Ohnishi
>
> The KMS document note that the keystore password file configured by
> {{hadoop.security.keystore.java-keystore-provider.password-file}} is looked
> up in Hadoop's configuration directory, but actually it is not.
> If setting it and put the password files on the configured path, KMS fails to
> start with the below error.
> {code}
> ERROR: Hadoop KMS could not be started
> REASON: java.io.IOException: Password file does not exists
> Stacktrace:
> ---------------------------------------------------
> java.io.IOException: Password file does not exists
> {code}
> I have found the file can be picked up from
> {{$HADOOP_PREFIX/share/hadoop/kms/tomcat/webapps/kms/WEB-INF/classes/}},
> which seems to be a tomcat classpath.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)