[
https://issues.apache.org/jira/browse/HADOOP-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HADOOP-16276:
--------------------------------
Attachment: HADOOP-16276.002.patch
Status: Patch Available (was: In Progress)
[~tlipcon] Thanks for comments.
Yeah it would be a solution to require the management software to specify an
absolute path for keytabs. But I think it is jsvc's fault in the first place
that it changed its default behavior. We could see this patch as a
compatibility fix.
rev 002 uploaded: avoided duplicate cmdline, using "cwd ." instead of "cwd
${pwd}", adjusted if condition position, test passed with jsvc 1.0.10 and jsvc
1.1.0.
> 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: [email protected]
For additional commands, e-mail: [email protected]
