Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 28 Dec 2013 04:46:50 +0000 (UTC)
From: "Grant Liu (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12679705.1384771011534.17718.1388206010147@arcas>
In-Reply-To: <JIRA.12679705.1384771011534@arcas>
References: <JIRA.12679705.1384771011534@arcas>
Subject: [jira] [Commented] (AMBARI-3792) Unable to connect to:
 https://server:8441/agent/v1/heartbeat/agent_hostname due to No JSON object
 could be decoded" when ping_port is not set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Grant Liu commented on AMBARI-3792:
-----------------------------------

For those examining this issue, note that the problem is intermittent and depends on timing when taking agents on and offline. So if you're seeing the error and a search landed you on this jira, this very likely does affect you.

> Unable to connect to: https://server:8441/agent/v1/heartbeat/agent_hostname due to No JSON object could be decoded" when ping_port is not set
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3792
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3792
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent, controller
>    Affects Versions: 1.4.1
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3792.patch
>
>
>  receive error "ERROR ... Controller.py:204 - Unable to connect to: https://server:8441/agent/v1/heartbeat/agenthost due to No JSON object could be decoded"
> 1.  Default the value to the default ping port rather than null for all_ping_ports on the server side.
> 2. Even if theere is a None in the json for ports make sure we dont break badly
> 3. When we break in manifestgenerator the exception should be caught and be in the ambari agent logs and shown in the logs that the generation of manifest broke and hte json for which it broke.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)