FAS Research Computing - Historique des incidents

Tous les systèmes sont opérationnels

Status page for the Harvard FAS Research Computing cluster and other resources.

Cluster Utilization (VPN and FASRC login required): Cannon | FASSE


Please scroll down to see details on any Incidents or maintenance notices.
Monthly maintenance occurs on the first Monday of the month (except holidays).

GETTING HELP
Documentation: https://docs.rc.fas.harvard.edu | Account Portal https://portal.rc.fas.harvard.edu
Email: rchelp@rc.fas.harvard.edu | Support Hours

The colors shown in the bars below were chosen to increase visibility for color-blind visitors.
For higher contrast, switch to light mode at the bottom of this page if the background is dark and colors are muted.
Opérationnel

SLURM Scheduler - Cannon - Opérationnel

Cannon Compute Cluster (Holyoke) - Opérationnel

Boston Compute Nodes - Opérationnel

GPU nodes (Holyoke) - Opérationnel

seas_compute - Opérationnel

Opérationnel

SLURM Scheduler - FASSE - Opérationnel

FASSE Compute Cluster (Holyoke) - Opérationnel

Opérationnel

Kempner Cluster CPU - Opérationnel

Kempner Cluster GPU - Opérationnel

Opérationnel

FASSE login nodes - Opérationnel

Opérationnel

Cannon Open OnDemand - Opérationnel

FASSE Open OnDemand - Opérationnel

Opérationnel

Netscratch (Global Scratch) - Opérationnel

Home Directory Storage - Boston - Opérationnel

Tape - (Tier 3) - Opérationnel

Holylabs - Opérationnel

Isilon Storage Holyoke (Tier 1) - Opérationnel

Holystore01 (Tier 0) - Opérationnel

HolyLFS04 (Tier 0) - Opérationnel

HolyLFS05 (Tier 0) - Opérationnel

HolyLFS06 (Tier 0) - Opérationnel

Holyoke Tier 2 NFS (new) - Opérationnel

Holyoke Specialty Storage - Opérationnel

holECS - Opérationnel

Isilon Storage Boston (Tier 1) - Opérationnel

BosLFS02 (Tier 0) - Opérationnel

Boston Tier 2 NFS (new) - Opérationnel

CEPH Storage Boston (Tier 2) - Opérationnel

Boston Specialty Storage - Opérationnel

bosECS - Opérationnel

Samba Cluster - Opérationnel

Globus Data Transfer - Opérationnel

Historique des incidents

nov. 2024

holyscratch01 degraded
  • Résolu
    UTC
    Résolu
    holyscratch01 is operational. These failing object stores will continue to cause issues. Please move your scratch data to /n/netscratch if you have not already. Holyscratch01 will be set READ-ONLY on Dec. 2nd. https://www.rc.fas.harvard.edu/blog/announcing-netscratch/
  • Détecté
    UTC
    Détecté

    OST2b has wedged again. We are in the process of troubleshooting this incident.

holylfs06 stability issues
  • Résolu
    UTC
    Résolu
    holylfs06 issues resolved.
  • Identifié
    UTC
    Identifié
    We are working on an issue with holylfs06 Expect some instability or slowness.
Citrix (TMS/RCapps) down
  • Résolu
    UTC
    Résolu
    Citrix/RCapps is up and working again.
  • Identifié
    UTC
    Identifié
    rcapps.rc.fas.harvard.edu Citrix is down. We are investigating.
Globus - Boston collection unavailable
  • Résolu
    UTC
    Résolu

    The transfer nodes for Boston globus are working again. We will follow up with the vendor for any additional information on root cause.

    Thanks you for your patience.

  • Identifié
    UTC
    Identifié
    This issue has not yet been resolved. We have a ticket in with Globus and will update once we know more.
  • Détecté
    UTC
    Détecté
    The Boston collection appears unavailable in Globus. We are investigating.
Netscratch - some directories stalled/unavailable
  • Résolu
    UTC
    Résolu
    Netscratch is working normally. The vendor has collected logs and is determining next steps for prevention.
  • Identifié
    UTC
    Identifié

    We are seeing a recurrence of this issue. We are working to determine the cause and resolution.

  • Résolu
    UTC
    Résolu
    The instability has been identified and resolved. Netscratch has returned to normal, full operaiton.
  • Détecté
    UTC
    Détecté
    We have reports that some directories in netscratch are unavailable or intermittent. We are working with Vast to determine the cause. This is a new filesystem which is under heavy load for cluster use as well as migration from holyscratch01. We appreciate your understanding of these teething pains and will update you as soon as we have more details or resolution.

oct. 2024

holyscratch01 OST2b issues
  • Résolu
    UTC
    Résolu
    This incident has been resolved.
  • Détecté
    UTC
    Détecté

    OST2b (one of the bricks that make up holyscratch01) has wedged again. We are in the process of troubleshooting.

holyscratch01 OST2b issues
  • Résolu
    UTC
    Résolu
    This incident has been resolved.
  • Détecté
    UTC
    Détecté

    OST2b on holyscratch01 (one of the bricks that makes up holyscratch01) is hung up. We are failing it over the rectify scratch performance issues.

holyscratch01 Instability
  • Résolu
    UTC
    Résolu
    The instability has been resolved.
  • Identifié
    UTC
    Identifié
    We are continuing to work on a fix for this incident.
  • Résolu
    UTC
    Résolu
    This incident has been resolved.
  • Détecté
    UTC
    Détecté
    We are currently investigating this incident.
holyscratch01 reboot
  • Résolu
    UTC
    Résolu
    This incident has been resolved.
  • Détecté
    UTC
    Détecté

    We are rebooting holyscratch01 to clear a stuck state.

holyscratch01 degraded
  • Résolu
    UTC
    Résolu
    OST2b failed over
  • Surveillé
    UTC
    Surveillé
    holyscratch01 - OST2b failing over

sept. 2024

Virtual Machine hypervisor down - Affects FASSE login/OOD
  • Résolu
    UTC
    Résolu
    Resolving. The hypervisor and all but one VM, which has separate issue, are operational.
  • Mettre à jour
    UTC
    Mettre à jour

    FASSE Open OnDemand and FASSE login services should be operational now.

  • Surveillé
    UTC
    Surveillé

    FASSE OOD is back up

    FASSE login nodes are still down

  • Identifié
    UTC
    Identifié

    One of the hypervisors managing virtual machines is down. We are working to bring it back up. This does affect FASSE login and FASSE OOD nodes as well as may degrade OpenAuth (two-factor).

    Affected hosts are:
    HOST -- STATUS

    dataverse-backup UNKNOWN

    demo2-l3-fs UNKNOWN

    enos-vote-l3-fs UNKNOWN

    fasselogin01 UNKNOWN

    fasselogin02 UNKNOWN

    frontier-squid02 UNKNOWN

    frontier-squid03 UNKNOWN

    frontier-squid04 UNKNOWN

    goel-adm24-l3-fs UNKNOWN

    goel-blind-l3-fs UNKNOWN

    goel-l3-fs UNKNOWN

    h-dev-fasseooda-01 UNKNOWN

    h-dev-fasseooda-lb01 UNKNOWN

    h-dev-fasseoodb-lb11 UNKNOWN

    h-fasseooda-01 UNKNOWN

    h-fasseooda-lb02 UNKNOWN

    h-fasseoodb-lb11 UNKNOWN

    h-fasseoodb-lb12 UNKNOWN

    h-fasseoodc-lb21 UNKNOWN

    h-fasseoodc-lb22 UNKNOWN

    h-qa-fasseooda-01 UNKNOWN

    h-qa-fasseooda-lb02 UNKNOWN

    holy-es-master01 UNKNOWN

    holy-es-master02 UNKNOWN

    holy-es-master03 UNKNOWN

    holynagios UNKNOWN

    kreindlerl3-fs UNKNOWN

    martin-su-l3-fs UNKNOWN

    mcconnell-l3-fs UNKNOWN

    openauth02 jtriley UNKNOWN

    shleifer-dsl3-fs UNKNOWN

    stock-solar-l3-fs UNKNOWN

    stopsack-l3-fs UNKNOWN

    xcat UNKNOWN

holyscratch01
  • Résolu
    UTC
    Résolu
    The failover is complete.
  • Identifié
    UTC
    Identifié
    The object storage target OST2b on holyscratch01 is again causing degraded performance. We are failing it over to the backup. We're aware that this issue is a concern, but please know that an entire new scratch filesystem is forthcoming. Thanks for your understanding.
holyscratch01 issues overnight
  • Résolu
    UTC
    Résolu
    holyscratch01 was at times degraded over the weekend. The OST causing the issues was restarted and the filesystem should be back to normal.
holyscratch01 degraded performance
  • Résolu
    UTC
    Résolu
    holyscratch01 was found to be in a degraded state around 9:15AM and returned to operation at 9:25AM
holyscratch01 - OST2b stuck
  • Mettre à jour
    UTC
    Mettre à jour
    This incident has been resolved.
  • Résolu
    UTC
    Résolu
    holyscratch01 and affected nodes are reopened
  • Identifié
    UTC
    Identifié
    holyscratch01 is seeing degraded performance and many nodes are closed off.

sept. 2024 à nov. 2024

Suivant

For issues not shown here, please contact FASRC via
https://portal.rc.fas.harvard.edu or email rchelp@rc.fas.harvard.edu