name node unable to start after with kerborose

[#1]

Hi Team,

We are not able to start the name node with kerborose setup, logs have been attached.namenode-log-5apr.txt

[#2]

@hadoop hdfs

Looks like the problem is due to Mixed Case of Hostname characters.

We see that the hostname is something like "rjio-UatCluster-NameNode1"

 http://rjio-UatCluster-NameNode1:8480/getJournal

But the Principal has lowercase hostname.

nn/rjio-uatcluster-namenode1@XXX.YYY.UAT

So please make sure that all your Hostnames in your cluster are in Lower case (Mixed case hostname can cause such issues in kerberized environments). Means the FQDN output should be in lowercase along with the hdfs-site.xml /core-site.xml hostnames (everything should be in lowercase)

# hostname -f

.

[#3]

@hadoop hdfs

Some snippet of your log where we can see the Hostnmae Case difference:

2018-04-04 22:30:12,204 INFO  security.UserGroupInformation (UserGroupInformation.java:loginUserFromKeytab(1101)) - Login successful for user nn/rjio-uatcluster-namenode1@XXX.YYY.UAT using keytab file /etc/security/keytabs/nn.service.keytab
.
.
2018-04-04 22:30:12,495 INFO  server.KerberosAuthenticationHandler (KerberosAuthenticationHandler.java:init(262)) - Login using keytab /etc/security/keytabs/spnego.service.keytab, for principal HTTP/rjio-uatcluster-namenode1@XXX.YYY.UAT
.

2018-04-04 22:30:12,502 INFO  server.KerberosAuthenticationHandler (KerberosAuthenticationHandler.java:init(262)) - Login using keytab /etc/security/keytabs/spnego.service.keytab, for principal HTTP/rjio-uatcluster-namenode1@XXX.YYY.UAT
.
2018-04-04 22:30:12,508 INFO  mortbay.log (Slf4jLog.java:info(67)) - Started HttpServer2$SelectChannelConnectorWithSafeStartup@rjio-UatCluster-NameNode1:50070

.

[#4]

@hadoop hdfs

First, make sure that the unlimited key JCE policy is installed and make sure spnego.service.keytab oermission is 444 as it requires access on all Journal node.