FAS Research Computing - История уведомлений

HolyLFS06 (Tier 0) испытывает серьезный сбой

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.

Работает

SLURM Scheduler - Cannon - Работает

Cannon Compute Cluster (Holyoke) - Работает

Boston Compute Nodes - Работает

GPU nodes (Holyoke) - Работает

seas_compute - Работает

Работает

SLURM Scheduler - FASSE - Работает

FASSE Compute Cluster (Holyoke) - Работает

Работает

Kempner Cluster CPU - Работает

Kempner Cluster GPU - Работает

Работает

FASSE login nodes - Работает

Работает

Cannon Open OnDemand - Работает

FASSE Open OnDemand - Работает

Полная недоступность

Netscratch (Global Scratch) - Работает

Home Directory Storage - Boston - Работает

Tape - (Tier 3) - Работает

Holylabs - Работает

Isilon Storage Holyoke (Tier 1) - Работает

Holystore01 (Tier 0) - Работает

HolyLFS04 (Tier 0) - Работает

HolyLFS05 (Tier 0) - Работает

HolyLFS06 (Tier 0) - Полная недоступность

Holyoke Tier 2 NFS - Работает

Holyoke Specialty Storage - Работает

holECS - Работает

Isilon Storage Boston (Tier 1) - Работает

BosLFS02 (Tier 0) - Работает

Boston Tier 2 NFS - Работает

CEPH Storage Boston (Tier 2) - Работает

Boston Specialty Storage - Работает

bosECS - Работает

Samba Cluster - Работает

Globus Data Transfer - Работает

История уведомлений

Посмотреть текущий статус

мая 2026

апр. 2026

Login and OOD node access restricted due to serious security issue - No ETA
РешеноПолная недоступность16 часов 1 минута
  • РешеноUTC

    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.

  • ОбновлениеUTC

    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.

  • ОбновлениеUTC

    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.

  • ОпределеноUTC

    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.

АПР28
Website security maintenance (www.rc and docs.rc) 4-28-26 1pm
ЗавершеноТехническое обслуживание16 минут
  • Завершеноапреля 28, 2026 в 17:16UTC

    Website maintenance has completed successfully.

  • В ходе выполненияапреля 28, 2026 в 17:00UTC
    Maintenance is now in progress
  • Запланированоапреля 28, 2026 в 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.

мар. 2026

Scheduler is degraded
РешеноПроизводительность снижена14 часов 55 минут
  • РешеноUTC

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

  • ИзучаетсяUTC

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

Network issues - Cluster degraded
РешеноПолная недоступность127 часов 7 минут
  • РешеноUTC

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

  • МониторингUTC

    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.

  • ОпределеноUTC

    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.

  • ИзучаетсяUTC

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

Назад

мар. 2026 до мая 2026

Следующая