Troubleshooting Servers (Obsolete)

Owned by Former user (Deleted)
Last updated: Jul 30, 2021 by Eddie Rubeiz
2 min read

This page and all its descendants are obsolete.

Step-by-step guide

  1. If the problem is with Archivesspace, check the Archivesspace page.
  2. If the problem is with Staging, check with developers to see if any recent code changes have been made to be aware of.
  3. Check to see which of the following likely problems are being encountered
    1. If the site is completely unreachable go to Site Unreachable (Obsolete)
    2. If the site can be reached, but searching does not work go to Site's search is broken
    3. If the site can be reached, but the viewer does not work to Viewer is broken
    4. If The site can be reached, but downloads do not work go to Derived Images not working and the As yet unwritten Fedora not working.
    5. If the site can be reached, but staff cannot add/edit works go here
    6. If the site can be reached, but new works added are not generating derived images go here.
  4. If the box itself cannot be reached try the following steps to troubleshoot ssh problems.
    1. Check the key you're using
    2. Try using the ubuntu default admin if your normal account does not work
    3. Log into AWS and go to the EC2 Service.
    4. In Instances find the server you want to check.
    5. Are the Instance Status and Status columns green or yellow?
      1. If they are all clear select the box
      2. Go to Instance Settings and Get System Log, check for errors
        1. Volume mount issues are a likely error
      3. If there are no errors, try to reboot the machine by using Action→Instance State→ Reboot. Notify Michelle and all digital collections team to see if this will be an issue.
        1. If it still is not accessible, it may be a local setting.
          1. Turn off the box, if it does not have an elastic IP be aware the public facing IP will change as a result of this.
          2. Unmount the root volume. In the EC2 screen go to Volumes
            1. Find the volume labeled sda1 for the machine you want
            2. Select it and go to Actions→ Detach Volume
            3. Keep it selected and use Actions → Attach Volume to attach it a working machine
              1. Make a note of what it attaches as in the attachment column (i.e. /dev/sdh)
            4. Log into the machine you attached it to, ideally a newly made box or something in staging
            5. Mount the disk to an easy to use location like /mnt with sudo mount /dev/xvd[]1 with [] being the letter from iii substep 1. While AWS reports them as sdX the machine sees them as xvdX
            6. Go to the /log directory in the mounted disk, and check the syslog for useful error messages.