[
https://issues.apache.org/jira/browse/HADOOP-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826623#comment-16826623
]
Todd Lipcon commented on HADOOP-16276:
--------------------------------------
Would it be easier to just require that the keytab and other paths be specified
as absolute paths instead of relative? i.e. this could be considered a bug in
the management software for not specifying an absolute path.
Aside from that point, it seems like it would be easier to assign some local
variable like "$JSVC_EXTRA_OPTS" which would be empty in the old-version case,
and set to '-cwd $PWD' in the new-version case. Then you don't need to
duplicate the rest of the command line arguments.
> 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.2.0, 3.1.2
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Attachments: HADOOP-16276.001.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: [email protected]
For additional commands, e-mail: [email protected]
