[
https://issues.apache.org/jira/browse/HADOOP-13005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688678#comment-16688678
]
Andrew K Long commented on HADOOP-13005:
----------------------------------------
I ran into this as well while setting up my dev environment on OSX. I was able
to fix this by editing my /etc/hosts file to include the domain name.
> if local hostname doesn't resolve, HttpServer2 fails with a kerberos exception
> ------------------------------------------------------------------------------
>
> Key: HADOOP-13005
> URL: https://issues.apache.org/jira/browse/HADOOP-13005
> Project: Hadoop Common
> Issue Type: Bug
> Components: net
> Affects Versions: 2.7.2
> Environment: a VM whose hostname was no longer in /etc/hosts
> Reporter: Steve Loughran
> Priority: Minor
>
> When a service (NN, DN) is started and the local hostname isn't in
> /etc/hosts, things will, obviously, fail.
> However, the failure is reported as a wrapped Kerberos Exception, rather than
> going via the NetUtils.wrapException handling code
> {{java.lang.RuntimeException: Could not resolve Kerberos principal name:
> java.net.UnknownHostException: xubunty: xubunty: unknown error}}
> The text is a dangerous distraction from the real cause. Especially as it
> appears even on systems which aren't running kerberos.
> A fail-fast check could go into the http server startup process ahead of the
> security setup; NetUtils could add special reporting of the
> unknown-local-host problem
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
