Cluster creation issue with Ambari agent

mertez — Sat, 08 Oct 2016 05:54:21 GMT

While trying to create a single node cluster with Ambari server installed on it I am facing the following problems:

a) Using a wizard I am stuck at 'Confirm Hosts' page where status and progress bar are not changing.

b) When trying to manually install Ambari Agent an exception pointing to a Controller Register method is thrown (line 377). Config in the ambary-agent.ini points to the same host that I get from 'hostname -f'

ambari-agent.out

Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/threading.py", line 811, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.6/site-packages/ambari_agent/Controller.py", line 377, in run
    self.register = Register(self.config)
  File "/usr/lib/python2.6/site-packages/ambari_agent/Register.py", line 34, in __init__
    self.hardware = Hardware()
  File "/usr/lib/python2.6/site-packages/ambari_agent/Hardware.py", line 44, in __init__
    self.hardware.update(Facter().facterInfo())
  File "/usr/lib/python2.6/site-packages/ambari_agent/Facter.py", line 475, in facterInfo
    facterInfo = super(FacterLinux, self).facterInfo()
  File "/usr/lib/python2.6/site-packages/ambari_agent/Facter.py", line 175, in facterInfo
    facterInfo['netmask'] = self.getNetmask()
  File "/usr/lib/python2.6/site-packages/ambari_agent/Facter.py", line 382, in getNetmask
    if OSCheck.is_redhat7():
AttributeError: class OSCheck has no attribute 'is_redhat7'

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 306, in <module>
    main(heartbeat_stop_callback)
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 297, in main
    ExitHelper.execute_cleanup()
TypeError: unbound method execute_cleanup() must be called with ExitHelper instance as first argument (got nothing instead)

ambari-agent.log

INFO 2016-10-07 16:19:50,282 ExitHelper.py:53 - Performing cleanup before exiting...
INFO 2016-10-07 16:19:53,621 main.py:71 - loglevel=logging.INFO
INFO 2016-10-07 16:19:53,621 main.py:71 - loglevel=logging.INFO
INFO 2016-10-07 16:19:53,623 DataCleaner.py:39 - Data cleanup thread started
INFO 2016-10-07 16:19:53,624 DataCleaner.py:120 - Data cleanup started
INFO 2016-10-07 16:19:53,625 DataCleaner.py:122 - Data cleanup finished
INFO 2016-10-07 16:19:53,751 PingPortListener.py:50 - Ping port listener started on port: 8670
INFO 2016-10-07 16:19:53,754 main.py:283 - Connecting to Ambari server at https://hdp-master:8440 (192.168.209.128)
INFO 2016-10-07 16:19:53,754 NetUtil.py:60 - Connecting to https://hdp-master:8440/ca
INFO 2016-10-07 16:19:53,833 threadpool.py:52 - Started thread pool with 3 core threads and 20 maximum threads
WARNING 2016-10-07 16:19:53,833 AlertSchedulerHandler.py:243 - [AlertScheduler] /var/lib/ambari-agent/cache/alerts/definitions.json not found or invalid. No alerts will be scheduled until registration occurs.
INFO 2016-10-07 16:19:53,833 AlertSchedulerHandler.py:139 - [AlertScheduler] Starting <ambari_agent.apscheduler.scheduler.Scheduler object at 0x2d64d50>; currently running: False
INFO 2016-10-07 16:19:53,837 hostname.py:89 - Read public hostname 'hdp-master.crmt.com' using socket.getfqdn()
INFO 2016-10-07 16:19:53,844 logger.py:71 - call[['test', '-w', '/']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,852 logger.py:71 - call returned (0, '')
INFO 2016-10-07 16:19:53,852 logger.py:71 - call[['test', '-w', '/dev']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,857 logger.py:71 - call returned (0, '')
INFO 2016-10-07 16:19:53,858 logger.py:71 - call[['test', '-w', '/dev/shm']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,866 logger.py:71 - call returned (0, '')
INFO 2016-10-07 16:19:53,866 logger.py:71 - call[['test', '-w', '/run']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,872 logger.py:71 - call returned (0, '')
INFO 2016-10-07 16:19:53,873 logger.py:71 - call[['test', '-w', '/sys/fs/cgroup']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,879 logger.py:71 - call returned (1, '')
INFO 2016-10-07 16:19:53,879 logger.py:71 - call[['test', '-w', '/boot']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,886 logger.py:71 - call returned (0, '')
INFO 2016-10-07 16:19:53,887 logger.py:71 - call[['test', '-w', '/run/user/42']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,892 logger.py:71 - call returned (0, '')
INFO 2016-10-07 16:19:53,893 logger.py:71 - call[['test', '-w', '/run/user/1000']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,899 logger.py:71 - call returned (0, '')
INFO 2016-10-07 16:19:53,900 logger.py:71 - call[['test', '-w', '/run/user/0']] {'sudo': True, 'timeout': 5}
INFO 2016-10-07 16:19:53,906 logger.py:71 - call returned (0, '')
ERROR 2016-10-07 16:19:53,925 main.py:309 - Fatal exception occurred:
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 306, in <module>
    main(heartbeat_stop_callback)
  File "/usr/lib/python2.6/site-packages/ambari_agent/main.py", line 297, in main
    ExitHelper.execute_cleanup()
TypeError: unbound method execute_cleanup() must be called with ExitHelper instance as first argument (got nothing instead)

Specifications:

.- openssl.x86_64 1:1.0.1e-42.el7.9

- CentOS Linux release 7.2.1511

- Python 2.7.5

- Ambari 2.4.1.0

- Ambari Agent manually installed

Re: Cluster creation issue with Ambari agent

pankaj_singh — Sat, 08 Oct 2016 19:56:43 GMT

@mertez will recommend to re-install after cleaning the old installation.

yum remove ambari-agent
rm -rf /var/lib/ambari-agent
rm -rf /var/run/ambari-agent
rm -rf /usr/lib/amrbari-agent
rm /etc/yum.repos.d/ambari.repo
yum clean all
wget -nv http://public-repo-1.hortonworks.com/ambari/centos7/2.x/updates/2.4.1.0/ambari.repo -O /etc/yum.repos.d/ambari.repo
yum install ambari-agent

Re: Cluster creation issue with Ambari agent

mertez — Mon, 10 Oct 2016 22:55:13 GMT

Pankaj thanks for your help. The problem was in using ambari-server 2.4.1 and ambari-agent 2.2.1. After the upgrade the issue was gone.

First problem was solved by modifying the ambari user in ambari.properties.

question Cluster creation issue with Ambari agent in Archives of Support Questions (Read Only)

Cluster creation issue with Ambari agent

Re: Cluster creation issue with Ambari agent

Re: Cluster creation issue with Ambari agent