Hosting#

Rescale a server#

The Bytemark and Linode Control Panels make it easy to scale/resize a server (number of cores and GiB of RAM).

You must deploy the service to re-configure swap, Elasticsearch, PostgreSQL and/or uWSGI.

Recover a server#

If a server becomes inaccessible, including via SSH, log into the hosting provider and:

  1. Reboot the server. This often restores access, as unsaved changes to firewall rules are reset, system resources are freed, and running processes are restarted.

  2. Use a recovery system to restore access if the server remains inaccessible.

Linode#

Lish (Linode Shell) provides console access to our Linode instances, similar to connecting via SSH.

  1. Log into Linode

  2. Select the server you want to access

  3. Click Launch LISH Console

  4. Login as root, using the password from OCP’s LastPass account

Hetzner#

Hetzner offers two recovery methods.

Hetzner Rescue System#

The Hetzner Rescue System boots the server using a temporary recovery image, from which we can mount the server drives to fix issues.

  1. Log into Hetzner

  2. Select the server you want to access

  3. Activate the rescue system:

    1. Click the Rescue tab

    2. Set Operating system to Linux

    3. Set Architecture to 64 bit

    4. Select your key for Public key (if missing, add it in Key management)

    5. Click Activate rescue system

  4. Reboot the server:

    1. Click the Reset tab

    2. Set Reset type to Press power button of server or Send CTRL+ALT+DEL to the server

    3. Click Send

    It takes some time to process the instruction. If nothing happens after 5 minutes, try again using Execute an automatic hardware reset.

  5. Connect to the server as the root user using SSH

  6. Mount the drive(s):

    mount /dev/md/2 /mnt
    
  7. Optionally, chroot into the operating system:

    chroot-prepare /mnt
    chroot /mnt
    

KVM Console#

Hetzner technicians attach a remote console (KVM Console) to a dedicated server. This option is slow to set up, but might be required if the issue is with the network, firewall or SSH configuration.