Restarting and rebooting servers
You can restart or reboot servers to resolve operational errors.
Before you begin
About this task
If you have an operational error, restarting or rebooting a server might solve the problem. Restarting a server closes all the processes that are running and starts them again. Rebooting a server closes all running processes and reboots the server. Rebooting a server is more intrusive than restarting a server and takes longer, and is typically used if restart does not resolve the issue.
Note: If you restart or reboot a Gateway server, the server is reloaded. Reload is a DataPower® term that means the same as restart.
Attention:
- If you configure two Management servers, for example for high availability or workload management, the persistent record of the defined APIs is replicated to both of the Management servers in case one of the servers fails. If one Management server fails or is stopped, when it restarts it uses the information, as provided by the server that remained active.
- If both Management servers are taken offline in one order and put back online in the opposite order, any changes that are made during that time period might be lost because two differing views of what represents the most recent configuration are contained in the persistent storage. Therefore, ensure that one Management server is always active.
- When you reboot two or more servers in a Management cluster, you must reboot each server individually, following a strict sequential procedure; for details, see Rebooting a Management cluster.
Restriction: You cannot restart or reboot a server if it is still joining or integrating with the API Connect on-premises cloud. Otherwise, the server might remain in an inconsistent state.
Procedure
To restart or reboot a server, complete the following steps:
-
Navigate to the server that you want to restart and click the Server
Actions icon
, then click Restart Servers.
The Restart/Reboot Server window opens.
