FAS Research Computing - Historique des avis

BosLFS02 (Tier 0) connaît une panne majeure

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.
Opérationnel

SLURM Scheduler - Cannon - Opérationnel

Cannon Compute Cluster (Holyoke) - Opérationnel

Boston Compute Nodes - Opérationnel

GPU nodes (Holyoke) - Opérationnel

seas_compute - Opérationnel

Opérationnel

SLURM Scheduler - FASSE - Opérationnel

FASSE Compute Cluster (Holyoke) - Opérationnel

Opérationnel

Kempner Cluster CPU - Opérationnel

Kempner Cluster GPU - Opérationnel

Opérationnel

FASSE login nodes - Opérationnel

Opérationnel

Cannon Open OnDemand - Opérationnel

FASSE Open OnDemand - Opérationnel

Panne majeure

Netscratch (Global Scratch) - Opérationnel

Home Directory Storage - Boston - Opérationnel

Tape - (Tier 3) - Opérationnel

Holylabs - Opérationnel

Isilon Storage Holyoke (Tier 1) - Opérationnel

Holystore01 (Tier 0) - Opérationnel

HolyLFS04 (Tier 0) - Opérationnel

HolyLFS05 (Tier 0) - Opérationnel

HolyLFS06 (Tier 0) - Opérationnel

Holyoke Tier 2 NFS - Opérationnel

Holyoke Specialty Storage - Opérationnel

holECS - Opérationnel

Isilon Storage Boston (Tier 1) - Opérationnel

BosLFS02 (Tier 0) - Panne majeure

Boston Tier 2 NFS - Opérationnel

CEPH Storage Boston (Tier 2) - Opérationnel

Boston Specialty Storage - Opérationnel

bosECS - Opérationnel

Samba Cluster - Opérationnel

Globus Data Transfer - Opérationnel

Historique des avis

Voir l’état actuel

avr. 2024

Scratch under high load
Résolu57 minutes
  • RésoluUTC

    The high I/O job has been identified. Scratch is back to normal operaiton.

  • En cours d'investigationUTC

    Scratch performance is degraded.

    holyscratch01 is under abnormally high I/O load.

    We are working to determine which job is the cause.

holynfs01 read-only mode - only affects certain NCF shares
Résolu450 heures
  • RésoluUTC

    All holynfs01 shares have been migrated or evacuated. Closing this incident. Holynfs01 remains online in read-only mode, but no shares rely on it now.

  • En cours d'investigationUTC

    holynfs01 has experienced a hardware failure. We have set all shares to read-only mode while we retrieve data from this server.

    If your group requires a writable space in the interim, please reach out and we will set one up for you or use scratch space for now.

    This only affects a handful of NCF shares, most inactive. But we are notifying all to cast a wide net.

holylogin[01-04] reboot
Résolu46 minutes
  • RésoluUTC
    This incident has been resolved.
  • En cours d'investigationUTC

    Due to stale file mounts for multiple groups, holylogin[01-04] will need to be rebooted at noon. Please save all work prior to the reboot.

gpu_test partition down
RésoluPerformances dégradées1 heure 35 minutes
  • RésoluUTC

    gpu_test and FASSE GPU partitions are back. We are looking into replacement power supply units to mitigate this issue.

  • En cours d'investigationUTC

    gpu_test is down again due to an IB switch failing

    the gpu partition in FASSE is also down

gpu_test partition down
RésoluPerformances dégradées43 minutes
  • RésoluUTC

    gpu_test is now operational and can be used.

    This incident has been resolved.

  • En cours d'investigationUTC

    An InfiniBand switch has failed in the cabinet housing the gpu_test nodes.

    Please use gpu_requeue or gpu in the meantime.

    We will update this incident when we have an ETA.

mars 2024

Internet acces to Holyoke interrupted 7:30-8am
Résolu
  • 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.
    UTC
holylabs instability
Résolu119 heures 57 minutes
  • RésoluUTC

    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.

  • En cours d'investigationUTC

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

  • Mettre à jourUTC

    Holylabs locked up again overnight. We are investigating.

  • SurveilléUTC

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

holyscratch01 performance degraded
Résolu139 heures 27 minutes
  • RésoluUTC

    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.

  • SurveilléUTC

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

  • En cours d'investigationUTC

    holyscratch01 performance degraded

    We are currently investigating this incident.

RC Ticket System and other VMs Offline - Expect Delays, emails will be delivered eventually
Résolu1 heure 14 minutes
  • RésoluUTC

    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.

  • En cours d'investigationUTC

    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)
Résolu5 heures 23 minutes
  • RésoluUTC
    This incident has been resolved.
  • SurveilléUTC

    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

févr. 2024

Ceph instability - Affects Boston VMs (Virtual Machines) and Tier2 Ceph shares
RésoluPerformances dégradées1 heure 34 minutes
  • RésoluUTC

    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

  • IdentifiéUTC

    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
RésoluPerformances dégradées28 heures 31 minutes
  • RésoluUTC

    This incident has been resolved.

  • En cours d'investigationUTC

    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
Résolu1 heure 37 minutes
  • RésoluUTC

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

  • IdentifiéUTC

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

  • SurveilléUTC

    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.

  • Mettre à jourUTC

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

  • IdentifiéUTC

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

  • En cours d'investigationUTC

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

BOSLFS02 Instability
Résolu356 heures 14 minutes
  • RésoluUTC
    This incident has been resolved.
  • En cours d'investigationUTC

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

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

boslffs instability
RésoluPerformances dégradées4 minutes
  • RésoluUTC
    This incident has been resolved.
  • IdentifiéUTC

    We are working on a fix for this incident.

Précédent

févr. 2024 à avr. 2024

Suivant

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