ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (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
Date Mon, 18 Nov 2013 10:37:21 GMT
Dmytro Sen created AMBARI-3792:
----------------------------------

             Summary: 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


 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#6144)

Mime
View raw message