ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15961) Kerberos wizard stuck trying to schedule service check operation
Date Tue, 19 Apr 2016 04:05:25 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247148#comment-15247148
] 

Hadoop QA commented on AMBARI-15961:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12799426/AMBARI-15961_branch-2.2_01.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6525//console

This message is automatically generated.

> Kerberos wizard stuck trying to schedule service check operation
> ----------------------------------------------------------------
>
>                 Key: AMBARI-15961
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15961
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.2
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: kerberos, kerberos-wizard, kerberos_descriptor
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15961_branch-2.2_01.patch
>
>
> Attached jstack after firing up the curl call.
> {code}
> curl -u admin:admin -H "X-Requested-By:ambari" -i -X POST -d'{"RequestInfo":{"context":"Kerberos
Service Check","command":"KERBEROS_SERVICE_CHECK","operation_level":{"level":"CLUSTER","cluster_name":"c1"}},"Requests/resource_filters":[{"service_name":"KERBEROS"}]}'
http://104.196.89.51:8080/api/v1/clusters/c1/requests
> {code}
> Behavior:
> - Call timedout on the UI and wizard cannot proceed further.
> - Exception in the server log after long wait:
> {code}
> 12 Apr 2016 23:01:45,231  INFO [qtp-ambari-client-818] AmbariManagementControllerImpl:3376
- Received action execution request, clusterName=c1, request=isCommand :true, action :null,
command :KERBEROS_SERVICE_CHECK, inputs :{}, resourceFilters: [RequestResourceFilter{serviceName='KERBEROS',
componentName='null', hostNames=[]}], exclusive: false, clusterName :c1
> 12 Apr 2016 23:01:45,409  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: HIVE
> 12 Apr 2016 23:01:45,410  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: AMBARI_METRICS
> 12 Apr 2016 23:01:45,410  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: HDFS
> 12 Apr 2016 23:01:45,410  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: MAPREDUCE2
> 12 Apr 2016 23:01:45,410  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: OOZIE
> 12 Apr 2016 23:01:45,410  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: TEZ
> 12 Apr 2016 23:01:45,411  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: HBASE
> 12 Apr 2016 23:01:45,411  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: ZOOKEEPER
> 12 Apr 2016 23:01:45,411  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: KERBEROS
> 12 Apr 2016 23:01:45,411  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: YARN
> 12 Apr 2016 23:01:45,411  INFO [qtp-ambari-client-818] AmbariCustomCommandExecutionHelper:1135
- Iterating service type Instance in getCommandJson:: PIG
> 12 Apr 2016 23:03:49,984  WARN [qtp-ambari-client-818] MITKerberosOperationHandler:434
- Failed to execute kadmin:
>         Command: /usr/bin/kadmin -s perf-b-3.c.pramod-thangali.internal -p admin -w ********
-r EXAMPLE.COM -q "get_principal admin"
>         ExitCode: 1
>         STDOUT: Authenticating as principal admin with password.
>         STDERR: kadmin: Client not found in Kerberos database while initializing kadmin
interface
> {code}



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

Mime
View raw message