[ https://issues.apache.org/jira/browse/AMBARI-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Onischuk updated AMBARI-18267: ------------------------------------- Attachment: AMBARI-18267.patch > Confusing output of "ambari-server status" > ------------------------------------------ > > Key: AMBARI-18267 > URL: https://issues.apache.org/jira/browse/AMBARI-18267 > Project: Ambari > Issue Type: Bug > Reporter: Andrew Onischuk > Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-18267.patch, AMBARI-18267.patch > > > When server is stopped, "ambari-server status" always reports about Stale PID > File (there is no stale pid file) > > > [root@c6401 ~]# ambari-server stop > Using python /usr/bin/python > Stopping ambari-server > Ambari Server stopped > [root@c6401 ~]# ll /var/run/ambari-server/ambari-server.pid > ls: cannot access /var/run/ambari-server/ambari-server.pid: No such file > or directory > [root@c6401 ~]# ambari-server status > Using python /usr/bin/python > Ambari-server status > Ambari Server not running. Stale PID File at: > /var/run/ambari-server/ambari-server.pid > > Looks like it's very old behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)