FAS Research Computing - Notishistorik

Alla system fungerar

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.

I drift

SLURM Scheduler - Cannon - I drift

Cannon Compute Cluster (Holyoke) - I drift

Boston Compute Nodes - I drift

GPU nodes (Holyoke) - I drift

seas_compute - I drift

I drift

SLURM Scheduler - FASSE - I drift

FASSE Compute Cluster (Holyoke) - I drift

I drift

Kempner Cluster CPU - I drift

Kempner Cluster GPU - I drift

I drift

FASSE login nodes - I drift

I drift

Cannon Open OnDemand - I drift

FASSE Open OnDemand - I drift

I drift

Netscratch (Global Scratch) - I drift

Home Directory Storage - Boston - I drift

Tape - (Tier 3) - I drift

Holylabs - I drift

Isilon Storage Holyoke (Tier 1) - I drift

Holystore01 (Tier 0) - I drift

HolyLFS04 (Tier 0) - I drift

HolyLFS05 (Tier 0) - I drift

HolyLFS06 (Tier 0) - I drift

Holyoke Tier 2 NFS (new) - I drift

Holyoke Specialty Storage - I drift

holECS - I drift

Isilon Storage Boston (Tier 1) - I drift

BosLFS02 (Tier 0) - I drift

Boston Tier 2 NFS (new) - I drift

CEPH Storage Boston (Tier 2) - I drift

Boston Specialty Storage - I drift

bosECS - I drift

Samba Cluster - I drift

Globus Data Transfer - I drift

Notishistorik

maj 2026

apr. 2026

Login and OOD node access restricted due to serious security issue - No ETA
  • Löst
    UTC
    Löst

    The cluster has been rebooted and all nodes, including login and OOD, have been patched.

    The scheduler is re-opened and jobs which were preempted/requeued have priority for re-scheduling.

    Some non-standard, lab-owned nodes may still require patching. The owners of these machines may be contacted about this.

    Thank you for your patience. This is a global issue and is being addressed at centers everywhere.

  • Uppdatering
    UTC
    Uppdatering

    To mitigate this exploit we will need to restart -all nodes- on the cluster.

    This will begin at 1PM and run until all nodes have restarted (no ETA).

    This will mean any un-finished jobs will be terminated. There is no way to avoid this.

    We will then be validating the fix before re-opening the login. OOD nodes, and scheduler.

    Next steps and updates will be posted here.

  • Uppdatering
    UTC
    Uppdatering

    We are developing a plan of attack to mitigate this exploit. Please know that this is a very serious issue and so we are treating it as such. Thank you for your understanding.

    We are currently awaiting further information from the Redhat/Fedora/Rocky community but building a plan in the meantime with the information we have. More details to follow as we can share them.

    If you need to access storage (except scratch and home directories), Globus is still online and available. But again, login nodes and OOD are not available.

  • Identifierat
    UTC
    Identifierat

    Due to a serious in-the-wild exploit which can compromise Fedora-based Linux distributions including Rocky, which is used on the cluster, we need to restrict access. All login and OOD nodes are shut down until a fix can be put in place. Jobs running on the cluster will continue running.

    No ETA, There is not fix at this time. We will update our status page in the morning once we have more information or a fix to roll out.

    This is a serious exploit and we do not take this measure lightly. Please follow this status page for updates and eventual resolution.

Website security maintenance (www.rc and docs.rc) 4-28-26 1pm
  • Slutfört
    april 28, 2026 kl 17:16UTC
    Slutfört
    april 28, 2026 kl 17:16UTC

    Website maintenance has completed successfully.

  • Pågår
    april 28, 2026 kl 17:00UTC
    Pågår
    april 28, 2026 kl 17:00UTC
    Maintenance is now in progress
  • Planerat
    april 28, 2026 kl 17:00UTC
    Planerat
    april 28, 2026 kl 17:00UTC

    Security updates are required for www.rc.fas.harvard.edu and docs.rc.fas.harvard.edu
    This work will take place today between 1pm and 2pm
    Both sites will be down for very short periods during the updates.

mars 2026

Scheduler is degraded
  • Löst
    UTC
    Löst

    This incident has been resolved. The scheduler is running normally.

  • Undersöker
    UTC
    Undersöker

    The scheduler is in a degraded state due to thrashing
    We are actively working to resolve this problem.

Network issues - Cluster degraded
  • Löst
    UTC
    Löst

    This incident has been resolved by draining and rebooting any nodes with stuck mounts.

  • Monitorerar
    UTC
    Monitorerar

    Mounts to Holyoke Isilon (specifically /n/sw) are broken on numerous nodes across the cluster. We have a check rolling out to find these nodes so we can remediate them individually. Until remediated the cluster will be in a degraded state. Running jobs may randomly die or fail as they hit nodes that have stale mounts.

    It will be risky to run jobs for the next hour and then, after that point, the cluster will have a large number of nodes closed waiting for them to drain so we can reboot them and fix the mounts.

    At this time we are unaware of any holy-isilon problems other than the effect this had on cluster nodes/running jobs. We will update should we identify any data storage concerns.

  • Identifierat
    UTC
    Identifierat

    Mounts to Holyoke Isilon (specifically /n/sw) are broken on numerous nodes across the cluster. We have a check rolling out to find these nodes so we can remediate them individually. Until remediated the cluster will be in a degraded state. Running jobs may randomly die or fail as they hit nodes that have stale mounts.

    It will be risky to run jobs for the next hour and then, after that point, the cluster will have a large number of nodes closed waiting for them to drain so we can reboot them and fix the mounts.

  • Undersöker
    UTC
    Undersöker

    A network issue affecting storage critical to the cluster is It's causing instability. The cluster is currently in a degraded state as a result. We are looking into the problem. Updates to follow..

mars 2026 till maj 2026

Nästa