ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vivek Rathod (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19840) Atlas Metadata Server Fails to start
Date Fri, 03 Feb 2017 22:26:51 GMT

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

Vivek Rathod commented on AMBARI-19840:
---------------------------------------

The issue was that the cluster was wire encrypted and on deleting some services and adding
them back, those services were no longer configured to work with SSL. But Ranger still tried
to communicate to them using SSL. 

The solution is either to un-wire encrypt ranger, or the enable wire encryption back for the
newly added services. Resolving this as invalid buy

> Atlas Metadata Server Fails to start
> ------------------------------------
>
>                 Key: AMBARI-19840
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19840
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Vivek Rathod
>             Fix For: 2.5.0
>
>
> Atlas Metadata Server Fails to start after deleting and adding back atlas.
> STR:
> 1) Delete the following services from the cluster: Smartsense, Atlas, Hbase, Sqoop, Storm,
Knox, Flume and AMS
> 2) Add back the deleted services using Add service Wizard
> Atlas Metadata Server fails with
> {code}
> ERROR Java::OrgApacheHadoopHbaseIpc::RemoteWithExtrasException: org.apache.hadoop.hbase.coprocessor.CoprocessorException:
SSLContext must not be null
> 	at org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.grant(RangerAuthorizationCoprocessor.java:1180)
> 	at org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService$1.grant(AccessControlProtos.java:9933)
> 	at org.apache.hadoop.hbase.protobuf.generated.AccessControlProtos$AccessControlService.callMethod(AccessControlProtos.java:10097)
> 	at org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:7832)
> 	at org.apache.hadoop.hbase.regionserver.RSRpcServices.execServiceOnRegion(RSRpcServices.java:1961)
> 	at org.apache.hadoop.hbase.regionserver.RSRpcServices.execService(RSRpcServices.java:1943)
> 	at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32389)
> 	at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2141)
> 	at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112)
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:187)
> 	at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:167)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message