You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Yesha Vora (JIRA)" <ji...@apache.org> on 2018/05/14 20:56:00 UTC
[jira] [Created] (AMBARI-23838) Amabri server gets NPE due to
ambari agent failure while registration
Yesha Vora created AMBARI-23838:
-----------------------------------
Summary: Amabri server gets NPE due to ambari agent failure while registration
Key: AMBARI-23838
URL: https://issues.apache.org/jira/browse/AMBARI-23838
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Yesha Vora
One of the ambari agent logs fails to handle registration with below stack trace
{code:java}
INFO 2018-05-14 20:38:02,377 HeartbeatThread.py:128 - Registration response received
ERROR 2018-05-14 20:38:02,378 HeartbeatThread.py:104 - Exception in HeartbeatThread. Re-running the registration
Traceback (most recent call last):
File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line 91, in run
self.register()
File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line 131, in register
self.handle_registration_response(response)
File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line 189, in handle_registration_response
raise Exception(error_message)
Exception: Registration failed
INFO 2018-05-14 20:38:02,379 transport.py:358 - Receiver loop ended{code}
Due to this failure, ambari server gets NPE.
{code}
2018-05-14 20:38:02,222 INFO [agent-register-processor-4] HeartBeatHandler:312 - agentOsType = centos7
2018-05-14 20:38:02,296 INFO [agent-register-processor-4] HostImpl:345 - Received host registration, host=[hostname=xx,fqdn=xx,domain=xxx,architecture=x86_64,processorcount=2,physicalprocessorcount=2,osname=centos,osversion=7.4.1708,osfamily=redhat,memory=16777216,uptime_hours=2238,mounts=(available=233881212,mountpoint=/,used=16772348,percent=7%,size=264091716,device=/dev/mapper/docker-253:5-3014660-4abca9bb09ce35db7850a7e6c617cd995ba5093a32b05ab6ac9374c858091864,type=ext4)]
, registrationTime=1526330282222, agentVersion=2.7.0.0
2018-05-14 20:38:02,308 INFO [agent-register-processor-4] TopologyManager:643 - TopologyManager.onHostRegistered: Entering
2018-05-14 20:38:02,308 INFO [agent-register-processor-4] TopologyManager:645 - TopologyManager.onHostRegistered: host = xxx is already associated with the cluster or is currently being processed
2018-05-14 20:38:02,309 INFO [agent-register-processor-4] HeartbeatController:105 -
java.lang.NullPointerException{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)