FAS Research Computing - История на известията

Всички системи работят

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 (new) - Работи

Holyoke Specialty Storage - Работи

holECS - Работи

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

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

Boston Tier 2 NFS (new) - Работи

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

Boston Specialty Storage - Работи

bosECS - Работи

Samba Cluster - Работи

Globus Data Transfer - Работи

История на известията

мар 2024

Internet acces to Holyoke interrupted 7:30-8am
  • Решен
    Решен
    There was a brief disruption in the connectivity from MGHPCC to the outside world/Internet. During this period outside attempts to connect to services hosted in Holyoke would time out. Internal data center network remained normal and no jobs were affected.
holylabs instability
  • Решен
    Решен

    After making some hardware and network changes, we monitored holylabs yesterday and overnight and have determined that it is stable again.

    We will continue to monitor but currently believe this issue has been resolved.

  • Разследва се
    Разследва се

    Holylabs was again unstable over the weekend. We are actively working this issue and will update as soon as possible.

  • Актуализация
    Актуализация

    Holylabs locked up again overnight. We are investigating.

  • Наблюдаваме
    Наблюдаваме

    Holylabs became stuck overnight and was restarted. It is back up and we are monitoring.

holyscratch01 performance degraded
  • Решен
    Решен

    holyscratch01 is currently stable. However, it continues to be under heavy utilization as a matter of course due to job loads.

    There is a plan underway to replace holyscratch01, but no ETA at this time as we are still qualifying and planning purchasing. We will notify the community when an ETA is known. Until then please be aware that load on scratch may continue along this trend. Thanks for your understanding.

  • Наблюдаваме
    Наблюдаваме

    Performance has improved, but we are still monitoring some high loads across object storage units.

  • Разследва се
    Разследва се

    holyscratch01 performance degraded

    We are currently investigating this incident.

RC Ticket System and other VMs Offline - Expect Delays, emails will be delivered eventually
  • Решен
    Решен

    VMs are returning to operation. If you receive an error (on Portal, Coldfront, etc) please wait a few minutes and try again.

    Ticket system is online and starting to receive delayed emails.

  • Разследва се
    Разследва се

    The RT ticket system is currently offline due to a VM issue.

    Any emails sent to the ticket system will eventually be delivered once it recovers, but until then expect delayed response.

FASRC maintenance update - All jobs requeued (Cannon and FASSE)
  • Решен
    Решен
    This incident has been resolved.
  • Наблюдаваме
    Наблюдаваме

    Informational Notice

    The Slurm upgrade to 23.11.4 was completed successfully during maintenance. However a complication with the automation of Slurm's cryptographic keys occurred during the upgrade which caused nodes to lose the ability to talk to the Slurm master. The Slurm master therefore viewed those nodes as down and requeued their jobs.

    All jobs on Cannon and FASSE were requeued.

    This is deeply regrettable but the chain of events which caused this could not be foreseen.

    To check the status of your jobs, see the common Slurm commands at:

    https://docs.rc.fas.harvard.edu/kb/convenient-slurm-commands/#Information_on_jobs

    FAS Research Computing

    https://docs.rc.fas.harvard.edu/

    rchelp@rc.fas.harvard.edu

фев 2024

Ceph instability - Affects Boston VMs (Virtual Machines) and Tier2 Ceph shares
  • Решен
    Решен

    The Ceph instability has been resolved. Ceph Tier2 shares, VDI, and VMs should be back to their normal state.

    If your VM, /net/fs-[labname] share, or VDI session is still impacted, please contact rchelp@rc.fas.harvard.edu

  • Идентифициран
    Идентифициран

    The infrastructure behind Tier2 Ceph shares and VMs is unstable.
    This also affects VDI/OOD which relies on virtual machines.

    /net/fs-[labname] shares, new OOD/VDI sessions, and VMs are affected and may will be inaccessible until this is resolved.

    Thanks for your patience.

holyscratch01 performance
  • Решен
    Решен

    This incident has been resolved.

  • Разследва се
    Разследва се

    holyscratch01 is experiencing high load. Performance may be delayed.

    OOD is also affected as a result of this.

    We are currently investigating this incident.

All Cluster nodes down or draining
  • Решен
    Решен

    Clusters are back in production status. We will continue to monitor for any aberrant behavior, but this incident has been resolved.

  • Идентифициран
    Идентифициран

    I spoke too soon, partial recovery, I'll update here when we are sure everything is back in production, apologies.

  • Наблюдаваме
    Наблюдаваме

    All cannon nodes are back in service and slurm is resuming jobs, fasse is coming back up as well, we will monitor the situation, but anticipate a return to full normal operations shortly.

  • Актуализация
    Актуализация

    The nodes are coming back into normal service, we anticipate this to be fairly quick

  • Идентифициран
    Идентифициран

    slurm is operational, jobs are idled and should resume as normal

  • Разследва се
    Разследва се

    We are currently investigating this incident. We will update here as we can

BOSLFS02 Instability
  • Решен
    Решен
    This incident has been resolved.
  • Разследва се
    Разследва се

    Boslfs02 (/n/boslfs02) is currently experiencing instability.

    We are working on the issue and will update this incident as the situation progresses.

boslffs instability
  • Решен
    Решен
    This incident has been resolved.
  • Идентифициран
    Идентифициран

    We are working on a fix for this incident.

яну 2024

fasselogin nodes down
  • Решен
    Решен

    fasselogin machines are back in service

  • Идентифициран
    Идентифициран

    We have identified the underlying issue and are working on fixing the FASSE login nodes. In the meantime, please use FASSE VDI. Updates to come.

  • Разследва се
    Разследва се

    fasselogin01/02 are currently down. We are investigating this incident.

Ceph instability - Affects Boston VMs (Virtual Machines) and Tier2 Ceph shares
  • Решен
    Решен

    The Ceph instability has been resolved. Ceph Tier2 shares, VDI, and VMs should be back to their normal state.

    If your VM, /net/fs-[labname] share, or VDI session is still impacted, please contact rchelp@rc.fas.harvard.edu

  • Идентифициран
    Идентифициран

    The infrastructure behind Tier2 Ceph shares and VMs is unstable.
    This also affects VDI/OOD which relies on virtual machines.

    /net/fs-[labname] shares, new OOD/VDI sessions, and VMs are affected and may will be inaccessible until this is resolved.

    Thanks for your patience.

Ceph instability - Affects Boston VMs (Virtual Machines) and Tier2 Ceph shares
  • Решен
    Решен

    The Ceph instability has been resolved. Ceph Tier2 shares, VDI, and VMs should be back to their normal state.

    If your VM, /net/fs-[labname] share, or VDI session is still impacted, please contact rchelp@rc.fas.harvard.edu

  • Идентифициран
    Идентифициран

    The infrastructure behind Tier2 Ceph shares and VMs is unstable.
    This also affects VDI/OOD which relies on virtual machines.

    /net/fs-[labname] shares, new OOD/VDI sessions, and VMs are affected and may will be inaccessible until this is resolved.

    Thanks for your patience.

Coldfront timeout
  • Решен
    Решен

    Coldfront is accessible again. Thanks for your patience so that would could investigate further. We've added new logging to have a better view into this should it happen again.

  • Разследва се
    Разследва се

    Coldfront is currently up but inaccessible. Login attempts will result in a timeout/proxy error.
    We would like time to gather forensics to sort out why this is happening before restarting the service.

    If you need to access Coldfront, please try again later today.

Ceph instability - Affects Boston VMs (Virtual Machines) and Tier2 Ceph shares
  • Решен
    Решен

    The Ceph instability has been resolved. Ceph Tier2 shares, VDI, and VMs should be back to their normal state.

    If your VM, /net/fs-[labname] share, or VDI session is still impacted, please contact rchelp@rc.fas.harvard.edu

  • Идентифициран
    Идентифициран

    The infrastructure behind Tier2 Ceph shares and VMs is unstable.
    This also affects VDI/OOD which relies on virtual machines.

    /net/fs-[labname] shares, new OOD/VDI sessions, and VMs are affected and may will be inaccessible until this is resolved.

    Thanks for your patience.

яну 2024 до мар 2024

Следващ

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