[
https://issues.apache.org/jira/browse/AMBARI-22834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356674#comment-16356674
]
Matthias commented on AMBARI-22834:
-----------------------------------
Facing the same problem - this causes the alert to Flicker multiple times per
day.
I wonder why this is classified as a "minor" issue - I get about 20-30 emails
per day due to this issue (if i don't remove the stale interpreter-pid file
manually).
Fixing this should be simple - changing the check from
{code:python}
pid_file = glob.glob(zeppelin_pid_dir + '/zeppelin-*.pid')[0]
{code}
to
{code:python}
pid_file = glob.glob(zeppelin_pid_dir + '/zeppelin-zeppelin*.pid')[0]
{code}
> Zeppelin Alert checks wrong pid file
> ------------------------------------
>
> Key: AMBARI-22834
> URL: https://issues.apache.org/jira/browse/AMBARI-22834
> Project: Ambari
> Issue Type: Bug
> Components: alerts
> Affects Versions: trunk, 2.6.2
> Reporter: Kevin Risden
> Priority: Minor
>
> The Zeppelin alert check doesn't check hte actual Zeppelin pid file. Instead
> it can pick up interpreter pid files.
> {code:python}
> pid_file = glob.glob(zeppelin_pid_dir + '/zeppelin-*.pid')[0]
> {code}
> This is wrong when there are multiple files in the pid dir starting with
> "zeppelin-".
> {code:bash}
> ls -l /var/run/zeppelin/
> -rw-r--r-- 1 zeppelin hadoop 7 Jan 16 12:01
> zeppelin-interpreter-livy-zeppelin-HOSTNAME.pid
> -rw-r--r-- 1 zeppelin hadoop 7 Jan 16 11:56 zeppelin-zeppelin-HOSTNAME.pid
> {code}
> *
> [https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/package/scripts/alert_check_zeppelin.py]
> *
> [https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/alert_check_zeppelin.py]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
