Stopping a master host (multi-host deployment)

Use this procedure to stop the Control Center service (serviced) on the master host in a multi-host deployment.
  1. Log in to the master host as root, or as a user with superuser privileges.
  2. Stop the top-level service serviced is managing, if necessary.
    1. Show the status of running services.
      serviced service status
      The top-level service is the service listed immediately below the headings line.
      • If the status of the top-level service and all child services is stopped, proceed to the next step.
      • If the status of the top-level service and all child services is not stopped, perform the remaining substeps.
    2. Stop the top-level service.
      Replace Service with the name or identifier of the top-level service:
      serviced service stop Service
    3. Monitor the stop.
      serviced service status
      When the status of the top-level service and all child services is stopped, proceed to the next step.
  3. Stop the Control Center service.
    systemctl stop serviced
  4. Ensure that no containers remain in the local repository.
    1. Display the identifiers of all containers, running and exited.
      docker ps -qa
      • If the command returns no result, stop. This procedure is complete.
      • If the command returns a result, perform the following substeps.
    2. Remove all remaining containers.
      docker ps -qa | xargs --no-run-if-empty docker rm -fv
    3. Display the identifiers of all containers, running and exited.
      docker ps -qa
      • If the command returns no result, stop. This procedure is complete.
      • If the command returns a result, perform the remaining substeps.
    4. Disable the automatic startup of serviced.
      systemctl disable serviced
    5. Reboot the host.
      reboot
    6. Log in to the master host as root, or as a user with superuser privileges.
    7. Enable the automatic startup of serviced.
      systemctl enable serviced