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 "Siyao Meng (JIRA)" <ji...@apache.org> on 2019/05/02 17:26:00 UTC
[jira] [Updated] (HADOOP-16276) Fix jsvc startup command in
hadoop-functions.sh due to jsvc >= 1.0.11 changed default current working
directory
[ https://issues.apache.org/jira/browse/HADOOP-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siyao Meng updated HADOOP-16276:
--------------------------------
Status: In Progress (was: Patch Available)
> Fix jsvc startup command in hadoop-functions.sh due to jsvc >= 1.0.11 changed default current working directory
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-16276
> URL: https://issues.apache.org/jira/browse/HADOOP-16276
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.1.2, 3.2.0
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Attachments: HADOOP-16276.001.patch, HADOOP-16276.002.patch
>
>
> In CDH6, when we bump jsvc from 1.0.10 to 1.1.0 we hit *KerberosAuthException: failure to login / LoginException: Unable to obtain password from user* due to DAEMON-264 and our
> *dfs.nfs.keytab.file* config uses a relative path. I will probably file another jira to issue a warning like *hdfs.keytab not found* before KerberosAuthException in this case.
> The solution is to add *-cwd $(pwd)* in function hadoop_start_secure_daemon in hadoop-functions.sh but I will have to consider the compatibility with older jsvc versions <= 1.0.10. Will post the patch after I tested it.
> Thanks [~tlipcon] for finding the root cause.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org