FAS Research Computing - Kunngjøringshistorikk

BosLFS02 (Tier 0) opplever større avbrudd

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.

Operasjonell

SLURM Scheduler - Cannon - Operasjonell

Cannon Compute Cluster (Holyoke) - Operasjonell

Boston Compute Nodes - Operasjonell

GPU nodes (Holyoke) - Operasjonell

seas_compute - Operasjonell

Operasjonell

SLURM Scheduler - FASSE - Operasjonell

FASSE Compute Cluster (Holyoke) - Operasjonell

Operasjonell

Kempner Cluster CPU - Operasjonell

Kempner Cluster GPU - Operasjonell

Operasjonell

FASSE login nodes - Operasjonell

Operasjonell

Cannon Open OnDemand - Operasjonell

FASSE Open OnDemand - Operasjonell

Større avbrudd

Netscratch (Global Scratch) - Operasjonell

Home Directory Storage - Boston - Operasjonell

Tape - (Tier 3) - Operasjonell

Holylabs - Operasjonell

Isilon Storage Holyoke (Tier 1) - Operasjonell

Holystore01 (Tier 0) - Operasjonell

HolyLFS04 (Tier 0) - Operasjonell

HolyLFS05 (Tier 0) - Operasjonell

HolyLFS06 (Tier 0) - Operasjonell

Holyoke Tier 2 NFS - Operasjonell

Holyoke Specialty Storage - Operasjonell

holECS - Operasjonell

Isilon Storage Boston (Tier 1) - Operasjonell

BosLFS02 (Tier 0) - Større avbrudd

Boston Tier 2 NFS - Operasjonell

CEPH Storage Boston (Tier 2) - Operasjonell

Boston Specialty Storage - Operasjonell

bosECS - Operasjonell

Samba Cluster - Operasjonell

Globus Data Transfer - Operasjonell

Kunngjøringshistorikk

Se nåværende status

apr. 2026

Login and OOD node access restricted due to serious security issue - No ETA
LøstStørre avbrudd16 timer ett minutt
  • LøstUTC

    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.

  • OppdateringUTC

    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.

  • OppdateringUTC

    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.

  • IdentifisertUTC

    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.

APR28
Website security maintenance (www.rc and docs.rc) 4-28-26 1pm
FullførtVedlikehold16 minutter
  • Fullførtapril 28, 2026 kl. 17:16UTC

    Website maintenance has completed successfully.

  • Pågårapril 28, 2026 kl. 17:00UTC
    Maintenance is now in progress
  • Planlagtapril 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østNedsatt ytelse14 timer 55 minutter
  • LøstUTC

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

  • UndersøkerUTC

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

Network issues - Cluster degraded
LøstStørre avbrudd127 timer 7 minutter
  • LøstUTC

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

  • OvervåkerUTC

    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.

  • IdentifisertUTC

    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økerUTC

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

feb. 2026

Tape outage
LøstNedsatt ytelse113 timer 42 minutter
  • LøstUTC

    This incident has been resolved. Normal tape operations are restored.

  • OvervåkerUTC

    The tape library outage is further extended to Wednesday March 4th at 9am awaiting a hardware replacement part due today. Data can still be uploaded to lab collections via Globus, but be mindful of the 10 TB buffer file limit. The outage affects storage and recall from tape.

  • IdentifisertUTC

    NESE Tape Service is still working with IBM technical support at restoring the inventory. The expected downtime is extended until Tuesday March 3rd, 9am.
    Apologies for the inconvenvenience.

  • UndersøkerUTC

    NESE Tape service will be down or operating with degraded service (no store and recall) Friday from 12 Noon EST until as late as Monday, 2 March at 9 AM.

    SUMMARY OF ISSUE:

    NESE Tape service is currently not able to store or recall files to and from tape due to vendor firmware issues in the IBM TS4500 tape library. The issue is related to the library robotics and cartridge database and we do NOT expect any data loss from this issue.

    The issue is apparently due to an issue with the inventory database related to a recent firmware update. This database can be scrubbed and reconstructed by the library, which will scan the bar code labels on all the cartridges to rebuild the inventory. Association of files in Globus to tapes is handled separately from the tape library and is not affected by the firmware update.

FEB19
NESE tape maintenance Feb 19th 2026
FullførtVedlikehold9 timer
  • Fullførtfebruar 19, 2026 kl. 22:00UTC
    Maintenance has completed successfully
  • Pågårfebruar 19, 2026 kl. 13:00UTC
    Maintenance is now in progress
  • Planlagtfebruar 19, 2026 kl. 13:00UTC

    From our partners at NESE. Details follow:

    We are installing four new tape frames, which will bring the tape system raw storage capacity to 253 petabytes.

    Service Affected: NESE Tape Service

    Maintenance Window: 8:00 AM - 5:00 PM (EST)

    • The tape service will be unavailable.

    • All upgrade activities are expected to be completed on the same day.

    NOTES:

    • Monitor the MGHPCC Slack #nese channel for status updates and announcements

    • Monitor https://nese.instatus.com/ for real-time updates on progress

    Subscribe to https://nese.instatus.com/subscribe/email for updates and announcements

Forrige

feb. 2026 til apr. 2026

Neste