FAS Research Computing - Geschichte beachten

Alle Systeme funktionieren

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.
Funktionsfähig

SLURM Scheduler - Cannon - Funktionsfähig

Cannon Compute Cluster (Holyoke) - Funktionsfähig

Boston Compute Nodes - Funktionsfähig

GPU nodes (Holyoke) - Funktionsfähig

seas_compute - Funktionsfähig

Funktionsfähig

SLURM Scheduler - FASSE - Funktionsfähig

FASSE Compute Cluster (Holyoke) - Funktionsfähig

Funktionsfähig

Kempner Cluster CPU - Funktionsfähig

Kempner Cluster GPU - Funktionsfähig

Funktionsfähig

FASSE login nodes - Funktionsfähig

Funktionsfähig

Cannon Open OnDemand - Funktionsfähig

FASSE Open OnDemand - Funktionsfähig

Funktionsfähig

Netscratch (Global Scratch) - Funktionsfähig

Home Directory Storage - Boston - Funktionsfähig

Tape - (Tier 3) - Funktionsfähig

Holylabs - Funktionsfähig

Isilon Storage Holyoke (Tier 1) - Funktionsfähig

Holystore01 (Tier 0) - Funktionsfähig

HolyLFS04 (Tier 0) - Funktionsfähig

HolyLFS05 (Tier 0) - Funktionsfähig

HolyLFS06 (Tier 0) - Funktionsfähig

Holyoke Tier 2 NFS (new) - Funktionsfähig

Holyoke Specialty Storage - Funktionsfähig

holECS - Funktionsfähig

Isilon Storage Boston (Tier 1) - Funktionsfähig

BosLFS02 (Tier 0) - Funktionsfähig

Boston Tier 2 NFS (new) - Funktionsfähig

CEPH Storage Boston (Tier 2) - Funktionsfähig

Boston Specialty Storage - Funktionsfähig

bosECS - Funktionsfähig

Samba Cluster - Funktionsfähig

Globus Data Transfer - Funktionsfähig

Geschichte beachten

Okt. 2024

holyscratch01 OST2b issues
  • Gelöst
    Gelöst
    This incident has been resolved.
  • Analyse
    Analyse

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

holyscratch01 OST2b issues
  • Gelöst
    Gelöst
    This incident has been resolved.
  • Analyse
    Analyse

    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
  • Gelöst
    Gelöst
    The instability has been resolved.
  • Identifizierung
    Identifizierung
    We are continuing to work on a fix for this incident.
  • Gelöst
    Gelöst
    This incident has been resolved.
  • Analyse
    Analyse
    We are currently investigating this incident.
holyscratch01 reboot
  • Gelöst
    Gelöst
    This incident has been resolved.
  • Analyse
    Analyse

    We are rebooting holyscratch01 to clear a stuck state.

holyscratch01 degraded
  • Gelöst
    Gelöst
    OST2b failed over
  • Überprüfung
    Überprüfung
    holyscratch01 - OST2b failing over

Sep. 2024

Virtual Machine hypervisor down - Affects FASSE login/OOD
  • Gelöst
    Gelöst
    Resolving. The hypervisor and all but one VM, which has separate issue, are operational.
  • Update
    Update

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

  • Überprüfung
    Überprüfung

    FASSE OOD is back up

    FASSE login nodes are still down

  • Identifizierung
    Identifizierung

    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
  • Gelöst
    Gelöst
    The failover is complete.
  • Identifizierung
    Identifizierung
    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
  • Gelöst
    Gelöst
    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
  • Gelöst
    Gelöst
    holyscratch01 was found to be in a degraded state around 9:15AM and returned to operation at 9:25AM
holyscratch01 - OST2b stuck
  • Update
    Update
    This incident has been resolved.
  • Gelöst
    Gelöst
    holyscratch01 and affected nodes are reopened
  • Identifizierung
    Identifizierung
    holyscratch01 is seeing degraded performance and many nodes are closed off.

Aug. 2024

holylfs04 down
  • Gelöst
    Gelöst
    holylfs04 is back up
  • Analyse
    Analyse
    Holylfs04 needs to be rebooted to address performance issues.
Cannon cluster degraded
  • Gelöst
    Gelöst
    The power issue has been resolved. All nodes that were drained are now being re-opened.
  • Analyse
    Analyse

    Due to temporary power availability issues in MGHPCC, half the nodes in 8A have been set to drain. This affects all partitions. Jobs will take longer to schedule but will not be terminated.

    We will reopen these nodes once the power issue has been resolved at the datacenter. No ETA at this time

boslfs02 degraded
  • Gelöst
    Gelöst
    boslfs02 is back up
  • Analyse
    Analyse
    boslfs02 needs to be rebalanced. Access may be inconsistent
Starfish upgrade
  • Abgeschlossen
    August 27, 2024 um 12:00
    Abgeschlossen
    August 27, 2024 um 12:00

    Starfish is back up

  • Update
    August 26, 2024 um 14:35
    Update
    August 26, 2024 um 14:35

    Starfish maintenance is still ongoing, no ETA at this time.

  • In Bearbeitung
    August 24, 2024 um 00:00
    In Bearbeitung
    August 24, 2024 um 00:00
    Maintenance is now in progress
  • Geplant
    August 24, 2024 um 00:00
    Geplant
    August 24, 2024 um 00:00

    The Starfish Zones Dashboard will be undergoing a few upgrades and maintenance this weekend from Friday, August 23rd at 8AM until Monday, August 26th at 8AM. The dashboard will not be accessible during this time. Further details will be provided, if needed. Please email rchelp@rc.fas.harvard.edu if you have any questions or concerns.

Rebalancing boslfs02
  • Gelöst
    Gelöst
    This incident has been resolved.
  • Überprüfung
    Überprüfung

    We are working on rebalancing boslfs02, there may be a short period of degraded performance

Aug. 2024 zu Okt. 2024

Nächste

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