Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D986218D0E for ; Mon, 5 Oct 2015 14:31:27 +0000 (UTC) Received: (qmail 2371 invoked by uid 500); 5 Oct 2015 14:31:27 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 2337 invoked by uid 500); 5 Oct 2015 14:31:27 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 2317 invoked by uid 99); 5 Oct 2015 14:31:27 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2015 14:31:27 +0000 Date: Mon, 5 Oct 2015 14:31:27 +0000 (UTC) From: "Sumit Mohanty (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-13312) Enable Kerberos is not working MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-13312: ----------------------------------- Summary: Enable Kerberos is not working (was: Enbale Kerberos is not working) > Enable Kerberos is not working > ------------------------------ > > Key: AMBARI-13312 > URL: https://issues.apache.org/jira/browse/AMBARI-13312 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: trunk > Environment: SLES 11 SP3 > Reporter: Vijay Srinivasaraghavan > > I have installed MIT KDC server on host1. Hadoop cluster and Ambari Server running in host 2 (in two separate containers). I have created a hadoop cluster with ZK, YARN/MR2 and HDFS services. When I try to enable security by using existing KDC, I see below 2 issues. > 1) Ambari server krb5.conf is not getting updated with the values supplied in UI > 2) Service keytab (kerberos.service_check.100515.keytab) seems to be having some issues. > {code} > lglop193:/ # klist > klist: No credentials cache found (ticket cache FILE:/tmp/krb5cc_0) > Kerberos 4 ticket cache: /tmp/tkt0 > klist: You have no tickets cached > lglop193:/ # cd /etc/security/keytabs/ > lglop193:/etc/security/keytabs # ls > kerberos.service_check.100515.keytab > lglop193:/etc/security/keytabs # /usr/bin/kinit -c /var/lib/ambari-agent/tmp/kerberos_service_check_cc_8b60256b73fc5454fc5737d0a1ce9887 -kt /etc/security/keytabs/kerberos.service_check.100515.keytab C-100515@HADOOP.COM > kinit(v5): Key table entry not found while getting initial credentials > lglop193:/etc/security/keytabs # kinit C-100515 -k -t kerberos.service_check.100515.keytab > kinit(v5): Key table entry not found while getting initial credentials > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)