FAS Research Computing - Notice history

Globus Data Transfer experiencing partial outage

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

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


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.
Operational

SLURM Scheduler - Cannon - Operational

Cannon Compute Cluster (Holyoke) - Operational

Boston Compute Nodes - Operational

GPU nodes (Holyoke) - Operational

seas_compute - Operational

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

Partial outage

Netscratch (Global Scratch) - Operational

Holyscratch01 (Pending Retirement) - Operational

Home Directory Storage - Boston - Operational

HolyLFS06 (Tier 0) - Operational

HolyLFS04 (Tier 0) - Operational

HolyLFS05 (Tier 0) - Operational

Holystore01 (Tier 0) - Operational

Holylabs - Operational

BosLFS02 (Tier 0) - Operational

Isilon Storage Boston (Tier 1) - Operational

Isilon Storage Holyoke (Tier 1) - Operational

CEPH Storage Boston (Tier 2) - Operational

Tape - (Tier 3) - Operational

Boston Specialty Storage - Operational

Holyoke Specialty Storage - Operational

Samba Cluster - Operational

Globus Data Transfer - Partial outage

bosECS - Operational

holECS - Operational

Notice history

Nov 2024

Citrix (TMS/RCapps) down
  • Resolved
    Resolved
    Citrix/RCapps is up and working again.
  • Identified
    Identified
    rcapps.rc.fas.harvard.edu Citrix is down. We are investigating.
Globus - Boston collection unavailable
  • Identified
    Identified
    This issue has not yet been resolved. We have a ticket in with Globus and will update once we know more.
  • Investigating
    Investigating
    The Boston collection appears unavailable in Globus. We are investigating.
Netscratch - some directories stalled/unavailable
  • Resolved
    Resolved
    Netscratch is working normally. The vendor has collected logs and is determining next steps for prevention.
  • Identified
    Identified

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

  • Resolved
    Resolved
    The instability has been identified and resolved. Netscratch has returned to normal, full operaiton.
  • Investigating
    Investigating
    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.
Loss of nodes in row 7c
  • Resolved
    Resolved

    Cooling has been restored and the impacted nodes are back online. This incident has been resolved.

  • Identified
    Identified
    Due to a cooling issue for these nodes, we will leave them down until we have an all-clear from the facility or vendor. All other nodes are up and running and thew cluster is otherwise operating normally. We will update as the situation changes.
  • Investigating
    Investigating
    Cannon nodes in 7c02-12 are down. We are investigating.
boslogin05 unstable, requires reboot
  • Resolved
    Resolved
    Reboot comp-leted at 11:08am
  • Identified
    Identified
    boslogin05 is unstable and will be rebooted at 11am

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.

Sep 2024 to Nov 2024

Next

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