(You must already be logged in to Gitlab or you’ll hit a 404)
Select ‘Reboot your server’ and you will be guided through the rebooting process.
Note that you should only use these mechanisms if the normal
reboot command doesn’t work - on Dedicated Servers, and if you choose a “forced” reboot with Legacy Virtual Machines, you risk recent changes to your system being lost or corrupted as it is equivalent to “pulling the plug”.
Here is what the process looks like for a Legacy Virtual Machine (the process will be similar for a Dedicated Server):
After making your choice your machine should reboot, and you should receive a final confirmation dialogue.
The above mechanism is best suited when interactively controlling a server’s power, but it is less convenient for power fencing defective nodes in a cluster.
It is possible to control the power of a server by connecting to the console shell with one of the following commands
powerstate, for example:
ssh -i stoneboat.dh.key firstname.lastname@example.org poweroff
The exit status will indicate whether the machine was successfully powered down or not.
powerstate returns the current status of the server’s power, one of
MIXED (when the machine has more that one PSU connected and they are not all in the same state).