Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EEA04200D1E for ; Wed, 4 Oct 2017 00:46:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id ED3E8160BD5; Tue, 3 Oct 2017 22:46:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3EF5F1609DE for ; Wed, 4 Oct 2017 00:46:04 +0200 (CEST) Received: (qmail 1845 invoked by uid 500); 3 Oct 2017 22:46:03 -0000 Mailing-List: contact issues-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 issues@ambari.apache.org Received: (qmail 1836 invoked by uid 99); 3 Oct 2017 22:46:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Oct 2017 22:46:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 8A26ADC742 for ; Tue, 3 Oct 2017 22:46:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 7n-qMYRwD_PX for ; Tue, 3 Oct 2017 22:46:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 424575F3D1 for ; Tue, 3 Oct 2017 22:46:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7D147E00DF for ; Tue, 3 Oct 2017 22:46:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 398A1242CB for ; Tue, 3 Oct 2017 22:46:00 +0000 (UTC) Date: Tue, 3 Oct 2017 22:46:00 +0000 (UTC) From: "Madhuvanthi Radhakrishnan (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-21865) NullPointerException during blueprint generation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 03 Oct 2017 22:46:05 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-21865. ------------------------------------------------ Resolution: Fixed > NullPointerException during blueprint generation > ------------------------------------------------ > > Key: AMBARI-21865 > URL: https://issues.apache.org/jira/browse/AMBARI-21865 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.3 > Reporter: amarnath reddy pappu > Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.6.0 > > > PROBLEM: > When customer tries to access Ambari Blueprint: > http://Ambarihost:8080/api/v1/clusters/TEST?format=blueprint > They see below error message web UI: > { "status": 500, "message": "Server Error" } > 7 Aug 2017 22:14:06,516 ERROR ambari-client-thread-214895 ContainerResponse:419 - The RuntimeException could not be mapped to a response, re-throwing to the HTTP container > java.lang.NullPointerException > at org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.splitAndTrimStrings(BlueprintConfigurationProcessor.java:1176) > at org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.parseNameNodes(BlueprintConfigurationProcessor.java:930) > Customer has setup a configuration for remote servers which are HA in their configs. > They started seeing this after making those changes. > dfs.namenode.http-address.nonha=:50070 > dfs.nameservices.internal=nonha > dfs.nameservices=nonha,hacluster > dfs.namenode.rpc-address.nonha=:8020 > dfs.namenode.rpc-address.hacluster.nn2=:8020 > dfs.namenode.rpc-address.hacluster.nn1=:8020 > dfs.ha.namenodes.hacluster=nn1,nn2 > dfs.client.failover.proxy.provider.hacluster=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider > Basically dfs.ha.namenodes.NNSERVICE value is not defined and it errors out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)