incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Tkhir (JIRA)" <>
Subject [jira] [Created] (AMBARI-2973) Ambari server and agent are not stopped during package uninstall
Date Wed, 21 Aug 2013 10:48:53 GMT
Vladimir Tkhir created AMBARI-2973:

             Summary: Ambari server and agent are not stopped during package uninstall
                 Key: AMBARI-2973
             Project: Ambari
          Issue Type: Bug
          Components: agent, controller
    Affects Versions: 1.4.1
            Reporter: Vladimir Tkhir
             Fix For: 1.4.1

When ambari-agent and ambari-server packages are uninstalled, uninstall scriplets don't stop
running services. That's why processes remain running even after package removal. 
That may cause issues during upgrade (if administrator misses the "stop services" step)
[root@host01 ~]$ ambari-server status
Using python  /usr/bin/python2.6
Ambari-server status
Ambari Server running
Found Ambari Server PID: '7850 at: /var/run/ambari-server/

[root@host01]# ambari-agent status
Found ambari-agent PID: 3521
ambari-agent running.
Agent PID at: /var/run/ambari-agent/
Agent out at: /var/log/ambari-agent/ambari-agent.out
Agent log at: /var/log/ambari-agent/ambari-agent.log

[root@host01]# rpm -e ambari-server
[root@host01]# rpm -e ambari-agent
[root@host01]# ps aux | grep ambari | grep -v grep | grep -v postgres
root      7850  2.1 13.2 3031480 254212 ?      Sl   20:51   0:36 /usr/jdk64/jdk1.6.0_31/bin/java
-server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60
-Xms512m -Xmx2048m -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/sbin:/bin:/usr/sbin:/usr/bin:/usr/lib/ambari-server/*
root      3521  0.7  1.1 499760 22544 ?        Sl   20:53   0:12 /usr/bin/python2.6 /usr/lib/python2.6/site-packages/ambari_agent/
start restart --expected-hostname=host01

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message