[
https://issues.apache.org/jira/browse/AMBARI-15063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149894#comment-15149894
]
Hudson commented on AMBARI-15063:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4338 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4338/])
AMBARI-15063 : Metrics monitor fails on restart (avijayan) (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d412ca11c8347fb89e7a5318c72a7dc24d0c2ff9])
* ambari-metrics/ambari-metrics-host-monitoring/conf/unix/ambari-metrics-monitor
*
ambari-metrics/ambari-metrics-timelineservice/conf/unix/ambari-metrics-collector
> Metrics monitor fails on restart
> --------------------------------
>
> Key: AMBARI-15063
> URL: https://issues.apache.org/jira/browse/AMBARI-15063
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.2.1
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15063.patch
>
>
> PROBLEM
> Metrics Monitor failed to START at install on 1 host. Restart also never
> worked.
> BUG
> Ambari metrics monitor startup script had a stale pid file with value as 327,
> and it used "ps ax -o pid | grep <pid>" to check if the process is running.
> This returned true since there was a process with process Id = 3327. Hence,
> the script always assumed that the metric monitor process was already running.
> FIX
> Change to use grep exact match (grep -w) while checking for process with
> process ID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
