Environment
Objective
Manually stop cb-services in the correct order in situations where partial services may have come up and restarting fails
Resolution
- Check the status of running services
- service cb-enterprise status
- Manually stop each running services in order of this list
- /usr/share/cb/cbservice cb-nginx stop
/usr/share/cb/cbservice cb-enterprised stop
/usr/share/cb/cbservice cb-allianceclient stop
/usr/share/cb/cbservice cb-liveresponse stop
/usr/share/cb/cbservice cb-datastore stop
/usr/share/cb/cbservice cb-sensorservices stop
/usr/share/cb/cbservice cb-coreservices stop
/usr/share/cb/cbservice cb-solr stop
/usr/share/cb/cbservice cb-rabbitmq stop
/usr/share/cb/cbservice cb-redis stop
/usr/share/cb/cbservice cb-datagrid stop
/usr/share/cb/cbservice cb-pgsql stop
- Once services are confirmed to be stopped, kill any additional running services such as epmd
- Clear any failed status in systemctl
- systemctl reset-failed cb-enterprise
Additional Notes
- To check for any orphaned cb services use:
- ps -ef | grep cb
- NOTE: cbdaemon and event-forwarder services should not affect the startup and shutdown of server services
- killall -KILL -u cb kills any processes owned by the cb user. A similar effect can be achieved by manually killing any pids returned with the above ps command