[
https://issues.apache.org/jira/browse/AMBARI-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk resolved AMBARI-7239.
-------------------------------------
Resolution: Fixed
Committed to trunk
> Ambari items in /tmp
> --------------------
>
> Key: AMBARI-7239
> URL: https://issues.apache.org/jira/browse/AMBARI-7239
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 1.7.0
>
>
> I notice two items in /tmp:
> ambari_commons
> ambari-server
> Looks like ambari-server (on ambari server machine) after I downloaded ZK
> client configs (so this might be related to all client config generation):
>
>
>
> [vagrant@c6401 tmp]$ cd ambari-server/
> [vagrant@c6401 ambari-server]$ ls
> ZOOKEEPER_CLIENT-configs.tar.gz ZOOKEEPER_CLIENT-configuration.json
>
> Looks like ambari_commons had things related to host registration / checks (on
> any agent machine):
>
>
>
> [vagrant@c6401 tmp]$ cd ambari_commons/
> [vagrant@c6401 ambari_commons]$ ls
> firewall.py firewall.pyc __init__.py __init__.pyc os_check.py
> os_check.pyc
>
> I also saw these files (on ambari-server machine and agent machines):
>
>
>
> -rwxr-xr-x 1 vagrant vagrant 1539 Sep 5 01:36 os_check_type1409880999.py
> -rwxr-xr-x 1 vagrant vagrant 8361 Sep 5 01:36 setupAgent1409881000.py
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
