Process does not restart after target host reboot
If you completed installing products in the BMC Cloud Lifecycle Management solution, but the proceses (on Linux) for the products do not start up after a host reboot, you might need to restart the processes manually. For Windows, the service for a given product or component will be restarted automatically.
The following table lists the steps that you must perform to restart the processes.
Product name | To start | To stop |
|---|---|---|
BMC BladeLogic Server Automation RSCD agent | /opt/bmc/rscd/NSH/conf/rscd start | /opt/bmc/rscd/NSH/conf/rscd stop |
BMC Remedy AR System Server and IT Service Management | /opt/bmc/ARSystem/bin/arsystem start | /opt/bmc/ARSystem/bin/arsystem stop |
BMC Remedy AR System - Cloud Database | /opt/bmc/ARSystem/bin/arsystem start | /opt/bmc/ARSystem/bin/arsystem stop |
BMC Remedy Mid Tier | /opt/apache/tomcat6.0/bin/startup.sh start | /opt/apache/tomcat6.0/bin/startup.sh stop |
BMC Atrium Core Web Services | /opt/bmc/AtriumWebRegistry/shared/tomcat/bin/startup.sh start | /opt/bmc/AtriumWebRegistry/shared/tomcat/bin/startup.sh stop |
BMC BladeLogic Server Automation |
|
|
BMC Atrium Orchestrator |
|
|
BMC BladeLogic Network Automation | /etc/init.d/enatomcat start | /etc/init.d/enatomcat stop |
BMC Cloud Platform Manager (OSGi) | /etc/init.d/bmccsm start | /etc/init.d/bmccsm stop |
PXE Server |
|
|
BMC BladeLogic Server Automation - Advanced Repeater | /etc/init.d/AdvancedRepeater start | /etc/init.d/AdvancedRepeater stop |
BMC BladeLogic Network Automation - Device Agent | /etc/init.d/bcanagent start | /etc/init.d/bcanagent stop |