You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2015/06/05 12:44:00 UTC

[jira] [Updated] (AMBARI-11717) Ambari-agent died when trying to auto restart itself

     [ https://issues.apache.org/jira/browse/AMBARI-11717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko updated AMBARI-11717:
----------------------------------------
    Attachment: AMBARI-11717.patch

> Ambari-agent died when trying to auto restart itself
> ----------------------------------------------------
>
>                 Key: AMBARI-11717
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11717
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11717.patch
>
>
> {code}
> INFO 2015-05-19 15:49:39,909 NetUtil.py:60 - Connecting to https://1d8.vm:8440/connection_info
> INFO 2015-05-19 15:49:40,063 security.py:93 - SSL Connect being called.. connecting to the server
> INFO 2015-05-19 15:49:40,215 security.py:55 - SSL connection established. Two-way SSL authentication is turned off on the server.
> INFO 2015-05-19 15:49:40,261 Controller.py:245 - Heartbeat response received (id = 380)
> ERROR 2015-05-19 15:49:40,261 Controller.py:263 - Error in responseId sequence - restarting
> {code}
> out file is empty
> STR:
> deploy multi-node cluster in virtual machines
> make snapshots
> in few hours, revert to previous snapshots. All agents except an agent on server host are dead
> EXPECTED:
> agents should just reconnect to server
> *While suspending Ambari cluster in VM is definitely not supported, we should ensure that auto restart on invalid responce Id is not actually killing agents.*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)