You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jaimin D Jetly (JIRA)" <ji...@apache.org> on 2014/01/31 22:04:09 UTC

[jira] [Updated] (AMBARI-4494) Need to provide info on where to look for command logs

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

Jaimin D Jetly updated AMBARI-4494:
-----------------------------------

    Attachment: AMBARI-4494.patch

> Need to provide info on where to look for command logs
> ------------------------------------------------------
>
>                 Key: AMBARI-4494
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4494
>             Project: Ambari
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>            Priority: Critical
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4494.patch
>
>
> After a failure during install or start, the UI only shows a subset of logs. It's hard to see a full-trace of the commands executed to try to determine the problem.
> The user will typically have to go onto the agent host, find the /var/lib/ambari-agent/data directory, then try to find the right output, error and command txt files to see the full trace, which are named based on id.
> The user does not easily know the id, and does not easily know anything about these files, or where to find them.
> The UI should show this information just so the user knows where to look.



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