FAS Research Computing - Notice history

seas_compute experiencing degraded performance

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
https://docs.rc.fas.harvard.edu | https://portal.rc.fas.harvard.edu | Email: rchelp@rc.fas.harvard.edu

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.
Degraded performance

SLURM Scheduler - Cannon - Operational

Cannon Compute Cluster (Holyoke) - Operational

Boston Compute Nodes - Operational

GPU nodes (Holyoke) - Operational

seas_compute - Degraded performance

Operational

SLURM Scheduler - FASSE - Operational

FASSE Compute Cluster (Holyoke) - Operational

Operational

Kempner Cluster CPU - Operational

Kempner Cluster GPU - Operational

Operational

Login Nodes - Boston - Operational

Login Nodes - Holyoke - Operational

FASSE login nodes - Operational

Operational

Cannon Open OnDemand/VDI - Operational

FASSE Open OnDemand/VDI - Operational

Operational

Netscratch (Global Scratch) - Operational

Home Directory Storage - Boston - Operational

Tape - (Tier 3) - Operational

Holylabs - Operational

Isilon Storage Holyoke (Tier 1) - Operational

Holystore01 (Tier 0) - Operational

HolyLFS04 (Tier 0) - Operational

HolyLFS05 (Tier 0) - Operational

HolyLFS06 (Tier 0) - Operational

Holyoke Tier 2 NFS (new) - Operational

Holyoke Specialty Storage - Operational

holECS - Operational

Isilon Storage Boston (Tier 1) - Operational

BosLFS02 (Tier 0) - Operational

Boston Tier 2 NFS (new) - Operational

CEPH Storage Boston (Tier 2) - Operational

Boston Specialty Storage - Operational

bosECS - Operational

Samba Cluster - Operational

Globus Data Transfer - Operational

Notice history

Oct 2024

holyscratch01 OST2b issues
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

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

holyscratch01 OST2b issues
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    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
  • Resolved
    Resolved
    The instability has been resolved.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
holyscratch01 reboot
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    We are rebooting holyscratch01 to clear a stuck state.

holyscratch01 degraded
  • Resolved
    Resolved
    OST2b failed over
  • Monitoring
    Monitoring
    holyscratch01 - OST2b failing over

Sep 2024

Virtual Machine hypervisor down - Affects FASSE login/OOD
  • Resolved
    Resolved
    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.

  • Monitoring
    Monitoring

    FASSE OOD is back up

    FASSE login nodes are still down

  • Identified
    Identified

    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
  • Resolved
    Resolved
    The failover is complete.
  • Identified
    Identified
    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
  • Resolved
    Resolved
    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
  • Resolved
    Resolved
    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.
  • Resolved
    Resolved
    holyscratch01 and affected nodes are reopened
  • Identified
    Identified
    holyscratch01 is seeing degraded performance and many nodes are closed off.

Aug 2024

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

    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
  • Resolved
    Resolved
    boslfs02 is back up
  • Investigating
    Investigating
    boslfs02 needs to be rebalanced. Access may be inconsistent
Starfish upgrade
  • Completed
    August 27, 2024 at 12:00 PM
    Completed
    August 27, 2024 at 12:00 PM

    Starfish is back up

  • Update
    August 26, 2024 at 2:35 PM
    In progress
    August 26, 2024 at 2:35 PM

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

  • In progress
    August 24, 2024 at 12:00 AM
    In progress
    August 24, 2024 at 12:00 AM
    Maintenance is now in progress
  • Planned
    August 24, 2024 at 12:00 AM
    Planned
    August 24, 2024 at 12:00 AM

    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
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

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

Aug 2024 to Oct 2024

Next

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