Start/Stop/Restart App Center Private Cloud

Article:TECH192002  |  Created: 2012-06-28  |  Updated: 2014-05-06  |  Article URL http://www.symantec.com/docs/TECH192002
Article Type
Technical Solution

Product(s)

Issue



An update needs to be applied to Nukona App Center and the commands to Stop/Start/Restart the daemons need to be run.


Error



No errors are displayed when running these commands.


Environment



Nukona App Center 3.0 through 4.1.18 are affected by these commands.

RHEL/CentOS 5.5-5.8 64-bit.


Cause



When installing an update to a Private Cloud tenant of Nukona App Center the services need to be in specific states during portions of the upgrade.


Solution



The following commands need to be run with either root or sudo permissions using the terminal:

cd /usr/local/nukona/bin
./nukona-services.sh stop
./nukona-services.sh start
./nukona-services.sh restart

In order to see if the daemons for the App Center are running the following commands can be run using the terminal.

ps -ef | grep monit
ps -ef | grep push
ps -ef | grep mdm
ps -ef | grep batch
ps -ef | grep wrap

Nukona App Center starts the daemons upon reboot of the server.  

*Note* If the environment being worked on has been upgraded several times it is recommended that a check is performed to ensure the daemons are still set to initiate on boot. The following command can be executed in the terminal to confirm this configuration.

chkconfig --list

There will be many entries in this list. The pertinent ones to spot will be "monit" and "httpd." You will need to verify that 3, 4, and 5 are set to "on."

The output of the previous command should display the following if set correctly:

monit          0:off   1:off   2:on    3:on    4:on   5:on    6:off
httpd           0:off   1:off   2:on    3:on    4:off   5:on    6:off

If either 3, 4, or 5 are set to "off," then the following commands can be issued to enable them.

chkconfig --levels 345 monit on
chkconfig --levels 345 httpd on

The following command can then be re-run to verify the proper configuration.

chkconfig --list




Article URL http://www.symantec.com/docs/TECH192002


Terms of use for this information are found in Legal Notices