You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2015/05/11 16:42:59 UTC
[jira] [Updated] (AMBARI-11043) falcon client not initalizing for
secure clusters
[ https://issues.apache.org/jira/browse/AMBARI-11043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Levas updated AMBARI-11043:
----------------------------------
Description:
{code}
# falcon admin -version
ERROR: Unable to initialize Falcon Client object
{code}
It would also be immensely helpful if we print some logs some where for this. Or create an env var that when set allows us to see debug logs because i have no idea why this error came up and how to debug any further. Nothing ever made it to the server side logs.
#Solution#
The *.falcon.http.authentication.kerberos.name.rules need to be uodated such that they are the same as hadoop.security.auth_to_local. To do this, add the following under the relevant service item in the Falcon kerberos.json file:
{code}
"auth_to_local_properties" : [
"falcon-startup.properties/*.falcon.http.authentication.kerberos.name.rules"
],
{code}
For example:
{code}
{
"services": [
{
"name": "FALCON",
...
"auth_to_local_properties" : [
"falcon-startup.properties/*.falcon.http.authentication.kerberos.name.rules"
],
...
}
]
}
{code}
was:
{code}
# falcon admin -version
ERROR: Unable to initialize Falcon Client object
{code}
It would also be immensely helpful if we print some logs some where for this. Or create an env var that when set allows us to see debug logs because i have no idea why this error came up and how to debug any further. Nothing ever made it to the server side logs.
> falcon client not initalizing for secure clusters
> -------------------------------------------------
>
> Key: AMBARI-11043
> URL: https://issues.apache.org/jira/browse/AMBARI-11043
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Blocker
> Labels: falcon, kerberos
> Fix For: 2.1.0
>
>
> {code}
> # falcon admin -version
> ERROR: Unable to initialize Falcon Client object
> {code}
> It would also be immensely helpful if we print some logs some where for this. Or create an env var that when set allows us to see debug logs because i have no idea why this error came up and how to debug any further. Nothing ever made it to the server side logs.
> #Solution#
> The *.falcon.http.authentication.kerberos.name.rules need to be uodated such that they are the same as hadoop.security.auth_to_local. To do this, add the following under the relevant service item in the Falcon kerberos.json file:
> {code}
> "auth_to_local_properties" : [
> "falcon-startup.properties/*.falcon.http.authentication.kerberos.name.rules"
> ],
> {code}
> For example:
> {code}
> {
> "services": [
> {
> "name": "FALCON",
> ...
> "auth_to_local_properties" : [
> "falcon-startup.properties/*.falcon.http.authentication.kerberos.name.rules"
> ],
> ...
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)