Starting, Stopping, and Restarting the Cloudera Manager Server
Some common reasons why you might need to start, stop, and restart the Clouder Manager Server include:
- You have modified Cloudera Manager configuration settings (for example, TLS/SSL) and must restart Cloudera Manager before the updates take effect
- You have edited the database properties file (/etc/cloudera-scm-server/db.properties) file, which contains information about the Cloudera Manager database and required access credentials
- Either the Cloudera log properties file /etc/default/cloudera-scm-server or log4j.properties file have been modified
- You added a new CSD file (at /opt/cloudera/csd)
sudo service cloudera-scm-server start
Note that if you wish to start the Cloudera Manager GUI at this point, it may take up to five minutes after executing the start command before it becomes available.
You can stop (for example, to perform maintenance on its host) or restart the Cloudera Manager Server without affecting the other services running on your cluster. Statistics data used by activity monitoring and service monitoring will continue to be collected during the time the server is down.
sudo service cloudera-scm-server stop
sudo service cloudera-scm-server restart