FAS Research Computing - Histórico de avisos

Todos os sistemas operacionais

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.

Operacional

SLURM Scheduler - Cannon - Operacional

Cannon Compute Cluster (Holyoke) - Operacional

Boston Compute Nodes - Operacional

GPU nodes (Holyoke) - Operacional

seas_compute - Operacional

Operacional

SLURM Scheduler - FASSE - Operacional

FASSE Compute Cluster (Holyoke) - Operacional

Operacional

Kempner Cluster CPU - Operacional

Kempner Cluster GPU - Operacional

Operacional

FASSE login nodes - Operacional

Operacional

Cannon Open OnDemand - Operacional

FASSE Open OnDemand - Operacional

Operacional

Netscratch (Global Scratch) - Operacional

Home Directory Storage - Boston - Operacional

Tape - (Tier 3) - Operacional

Holylabs - Operacional

Isilon Storage Holyoke (Tier 1) - Operacional

Holystore01 (Tier 0) - Operacional

HolyLFS04 (Tier 0) - Operacional

HolyLFS05 (Tier 0) - Operacional

HolyLFS06 (Tier 0) - Operacional

Holyoke Tier 2 NFS (new) - Operacional

Holyoke Specialty Storage - Operacional

holECS - Operacional

Isilon Storage Boston (Tier 1) - Operacional

BosLFS02 (Tier 0) - Operacional

Boston Tier 2 NFS (new) - Operacional

CEPH Storage Boston (Tier 2) - Operacional

Boston Specialty Storage - Operacional

bosECS - Operacional

Samba Cluster - Operacional

Globus Data Transfer - Operacional

Histórico de avisos

abr 2026

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

    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.

  • Atualizar
    UTC
    Atualizar

    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.

  • Atualizar
    UTC
    Atualizar

    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.

  • Identificado
    UTC
    Identificado

    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
  • Concluído
    abril 28, 2026 em 17:16UTC
    Concluído
    abril 28, 2026 em 17:16UTC

    Website maintenance has completed successfully.

  • Em curso
    abril 28, 2026 em 17:00UTC
    Em curso
    abril 28, 2026 em 17:00UTC
    Maintenance is now in progress
  • Ainda não começou
    abril 28, 2026 em 17:00UTC
    Ainda não começou
    abril 28, 2026 em 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.

mar 2026

Scheduler is degraded
  • Resolvido
    UTC
    Resolvido

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

  • Investigando
    UTC
    Investigando

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

Network issues - Cluster degraded
  • Resolvido
    UTC
    Resolvido

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

  • Monitorização
    UTC
    Monitorização

    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.

  • Identificado
    UTC
    Identificado

    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.

  • Investigando
    UTC
    Investigando

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

fev 2026

Tape outage
  • Resolvido
    UTC
    Resolvido

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

  • Monitorização
    UTC
    Monitorização

    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.

  • Identificado
    UTC
    Identificado

    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.

  • Investigando
    UTC
    Investigando

    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.

NESE tape maintenance Feb 19th 2026
  • Concluído
    fevereiro 19, 2026 em 22:00UTC
    Concluído
    fevereiro 19, 2026 em 22:00UTC
    Maintenance has completed successfully
  • Em curso
    fevereiro 19, 2026 em 13:00UTC
    Em curso
    fevereiro 19, 2026 em 13:00UTC
    Maintenance is now in progress
  • Ainda não começou
    fevereiro 19, 2026 em 13:00UTC
    Ainda não começou
    fevereiro 19, 2026 em 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

fev 2026 para abr 2026

Seguinte