Cannot shut down server because a service fails to stop

If the upgrade does not complete successfully because a service fails to stop, you can attempt to correct the error by forcing the service to shut down, so that the upgrade process can resume.

About this task

The GDU Upgrade Software task cannot complete if the server is prevented from shutting down because a service fails to stop. When this occurs, the GDU Upgrade Software task stops at the "Stopping services" stage and manual intervention is required to stop the service.

Allow 30 minutes to elapse for the service to complete processing before concluding that the service is hung, and the following troubleshooting steps are required.

Steps

From the service laptop, log in to the grid node:
1. Enter the following command: ssh admin@grid_node_IP
2. Enter the password listed in the Passwords.txt file.
3. Enter the following command to switch to root: su -
4. Enter the password listed in the Passwords.txt file.
When you are logged in as root, the prompt changes from $ to #.
Display the status of services on the server: /usr/local/servermanager/reader.rb
Examine the output to determine if any services are stuck in the "Stopping..." state.
For any service that is hung, shut down the service forcibly: /etc/init.d/service_name force-stop
The service may appear as unknown (blue) in the StorageGRID Webscale system until it is restarted.