[
https://issues.apache.org/jira/browse/AMBARI-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863011#comment-13863011
]
Dmitry Lysnichenko commented on AMBARI-3792:
--------------------------------------------
Problem is usually caused by the fact that the server unexpectedly terminated
connection for any reason (and as a result, agent has got an invalid json
instead of heartbeat response). Reasons may be different, for example:
- significant difference in local time settings between agent and server (SSL
does not work in this case)
- networking problems
- agent's passphrase/certificate is not valid
- some server-side error while processing heartbeat
Generally, it makes sense to study server logs as well in this situation.
> 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)
