ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-11717) Ambari-agent died when trying to auto restart itself
Date Fri, 05 Jun 2015 10:42:01 GMT
Dmitry Lysnichenko created AMBARI-11717:
-------------------------------------------

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


{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)

Mime
View raw message