[
https://issues.apache.org/jira/browse/AMBARI-12564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644588#comment-14644588
]
Hudson commented on AMBARI-12564:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #3182 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3182/])
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=f97945c9f441882094734b01a41726767249bb56)
* 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)
