ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12564) Logging of exceptions in python code in Ambari Agent
Date Tue, 28 Jul 2015 15:33:04 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-12564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644540#comment-14644540
] 

Hudson commented on AMBARI-12564:
---------------------------------

SUCCESS: Integrated in Ambari-branch-2.1 #281 (See [https://builds.apache.org/job/Ambari-branch-2.1/281/])
AMBARI-12564. Logging of exceptions in python code in Ambari Agent (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bb879dbc7df8944669a8aa6e15e158b1484658c4)
* ambari-agent/src/main/python/ambari_agent/main.py


> Logging of exceptions in python code in Ambari Agent
> ----------------------------------------------------
>
>                 Key: AMBARI-12564
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12564
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.1
>
>
> Today if Ambari Agent python code throws the exception and the stack trace get
> rerouted to /var/log/ambari_agent/ambari_agent.out . This is not logged by our
> agent and therefore it makes it hard to RCA Ambari Agent failures, let alone
> know that Ambari Agent failed.  
> I am hoping it is possible to wrap the entry code to Ambari Agent in a
> try/catch and log the error message and stack trace to the log appenders and
> only then have ambari agent throw.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message