[ https://issues.apache.org/jira/browse/AMBARI-17956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ellis Tite updated AMBARI-17956: -------------------------------- Description: Something is repeatedly calling ambari-server start, we are having to close multiple instances of ambari-server with different pid's and it is preventing us seeing new stacks until we get them all. Checking in the pid file when this happens there are often 2 pid's in there. This doesn't occur with previous versions of ambari. Sometimes, killing the processes with the pid's in the pid file and then spamming "ambari-server stop" manages to kill the instances and get us back to normality, other times we've been forced to add "exit 1" to /etc/init.d/ambari-server and then kill all the ambari service processes. This happens very regularly: we tend to add a stack, restart ambari, then when we try to add another stack and restart ambari-server again we hit this issue. was: Something is repeatedly calling ambari-server start, we are having to close multiple instances of ambari-server with different pid's and it is preventing us seeing new stacks until we get them all. Checking in the pid file when this happens there are often 2 pid's in there. This doesn't occur with previous versions of ambari. Sometimes, killing the processes with the pid's in the pid file and then spamming "ambari-server stop" manages to kill the instances and get us back to normality, other times we've been forced to add "exit 1" to /etc/init.d/ambari-server and then kill all the ambari service processes. This happens very regularly: we tend to add a stack, restart ambari, then when we try to add another stack and restart ambari-server we hit this issue. > ambari launches multiple server instances > ----------------------------------------- > > Key: AMBARI-17956 > URL: https://issues.apache.org/jira/browse/AMBARI-17956 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.2.2 > Environment: Centos 6 > HDP 2.4 > Reporter: Ellis Tite > Priority: Critical > > Something is repeatedly calling ambari-server start, we are having to close > multiple instances of ambari-server with different pid's and it is preventing > us seeing new stacks until we get them all. Checking in the pid file when > this happens there are often 2 pid's in there. This doesn't occur with > previous versions of ambari. > Sometimes, killing the processes with the pid's in the pid file and then > spamming "ambari-server stop" manages to kill the instances and get us back > to normality, other times we've been forced to add "exit 1" to > /etc/init.d/ambari-server and then kill all the ambari service processes. > This happens very regularly: we tend to add a stack, restart ambari, then > when we try to add another stack and restart ambari-server again we hit this > issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)