ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-9627) RU - NodeManager failed to restart in Kerberized clusters
Date Fri, 13 Feb 2015 15:43:11 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-9627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alejandro Fernandez updated AMBARI-9627:
----------------------------------------
    Attachment: AMBARI-9627.patch

> RU - NodeManager failed to restart in Kerberized clusters
> ---------------------------------------------------------
>
>                 Key: AMBARI-9627
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9627
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9627.patch
>
>
> Node Manager failed to restart in a Kerberized cluster while performing a Rolling Upgrade.
> I deployed a 3-node cluster with all services from HDDFS through ZK, then enabled Namenode
HA, and kerberized the cluster.
> When I performed a RU from 2.2.0.0 GA bits to 2.2.1.0-2260, I first had to comment out
an error in ZK server, and when I got to the Slaves group, NodeManager failed. See attached
log.
> {code}
> Fail: Execution of '/usr/bin/kinit -kt /etc/security/keytabs/nm.service.keytab nm/_HOST@EXAMPLE.COM;'
returned 1. kinit: Keytab contains no suitable keys for nm/_HOST@EXAMPLE.COM while getting
initial credentials
> {code}
> {code}
> [root@c6404 ~]# klist -kt /etc/security/keytabs/nm.service.keytab
> Keytab name: FILE:/etc/security/keytabs/nm.service.keytab
> KVNO Timestamp         Principal
> ---- ----------------- --------------------------------------------------------
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
>    1 02/12/15 23:23:29 nm/c6404.ambari.apache.org@EXAMPLE.COM
> {code}
> This means that params.py is probably missing to replace _HOST with the value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message