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 2014/01/27 12:24:38 UTC

[jira] [Resolved] (AMBARI-4354) HostCleanup should also clean /tmp/hadoop-*

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

Dmitry Lysnichenko resolved AMBARI-4354.
----------------------------------------

    Resolution: Fixed

> HostCleanup should also clean /tmp/hadoop-*
> -------------------------------------------
>
>                 Key: AMBARI-4354
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4354
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.4.2
>            Reporter: Dmytro Shkvyra
>            Assignee: Dmytro Shkvyra
>             Fix For: 1.5.1
>
>
> HostCleanup should also check the following directories (and clean):
> /tmp/hadoop-*
> For example, if the /tmp/hadoop-nagios directory is present, but it doesn't have the right ownership/perms for nagios user, the Hive Metastore Nagios alert will occur. I saw this after doing an install on an un-clean machine.
> {code}
> Hive Metastore status
> CRIT for about a minute
> CRITICAL: Error accessing Hive Metastore status [Error creating temp dir in hadoop.tmp.dir /tmp/hadoop-nagios due to Permission denied]
> {code}
> An easy way to reproduce this:
> 1) Perform install
> 2) Go to Nagios server machine
> 3) Change perms on /tmp/hadoop-nagios so that the nagios user does not have access
> 4) The Nagios alert will fire



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)