Stopping a master host node
Use this procedure to stop the Control Center service (serviced) on the master host in a high-availability deployment.
- Use the virtual hostname or virtual IP address of the high-availability cluster to log in to the Control Center master node as root, or as a user with superuser privileges.
Display the public hostname of the current node.
uname -nMake a note of which node (primary or secondary) is the current node, for use in a subsequent step.
Stop the top-level service serviced is managing, if necessary.
Show the status of running services.
serviced service statusThe 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.
Stop the top-level service.
Replace Service with the name or identifier of the top-level service:
serviced service stop Service
Monitor the stop.
serviced service statusWhen the status of the top-level service and all child services is stopped, proceed to the next step.
- Show the status of running services.
Stop Control Center with the cluster management tool.
pcs cluster standby --all
Monitor the status of cluster resources.
watch pcs statusMonitor the status until all resources report Stopped. Resolve any issues before continuing.
Ensure that no containers remain in the local repository.
Start the Docker service.
systemctl start docker
Display the identifiers of all containers, running and exited.
docker ps -qaIf the command returns a result, enter the following command:
docker ps -qa | xargs --no-run-if-empty docker rm -fv
Stop the Docker service.
systemctl stop docker
- Start the Docker service.
- To ensure that no containers remain in both Docker repositories, log in to the other master node as root, or as a user with superuser privileges, and then perform the preceding step.