Revision as of 15:00, 23 January 2019

If you have one server you want to shut down and bring back up, make sure to keep the following in mind. Most of these points are non-technical.

Machines where this is okay

You may restart any of these machines relatively quickly and non-disruptively most of the time.

On the CS subdomain:

On the cluster subdomain:

compute nodes
in rare cases, individual clusters, one at a time (note that this excludes hopper, which should rarely be shut down)

For other machines, email the admin mailing list or talk to a faculty supervisor first.

The process to restart one of our servers is as follows:

Also remember these guidelines:

In an emergency (e.g. no services seem available, no one can log in to things), you can just restart the machine.
That said, give at least a few hours' notice if possible. These servers aren't in use 100% of the time but when they *are* in use it's important that people can continue to use them.
Be prepared to go to Noyes basement if there are problems restarting the server remotely. In other words, be on-campus and preferably in the science complex when you do this (or be in communication with an admin who is).

The point is to be courteous to the community for whom we run these servers.

@@ Line 17: / Line 17: @@
 = Reminders =
-Shutting a machine down is simple (<code>shutdown -h now</code> will do it, for the most part), so there's no "process" for this. However, there are some things to keep in mind:
+The process to restart one of our servers is as follows:
+# unmount file systems if applicable
+# check on backups if applicable
+# <code>shutdown -h now</code> when you're ready (you will immediately lose ssh connections)
+Also remember these guidelines:
 # In an emergency (e.g. no services seem available, no one can log in to things), you can just restart the machine.