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 - 정상

5월 2022

Slurm security patch causing node unavailability
해결됨성능 저하2시간 30분
  • 해결됨UTC

    The scheduler and node states appear to be stable. Thank you for your patience and understanding.

    Please note that the intermittent deadlock issue is still not resolved, but we are actively monitoring that and intervening as necessary until we receive a solution.

  • 모니터링 중UTC

    The patch has been deployed and the scheduler restarted. Paused jobs are resuming.

    Any jobs which did not start or were stuck may have been flushed. So please check any pending jobs you might have had.

    Related doc: https://docs.rc.fas.harvard.edu/kb/running-jobs/.

  • 확인됨UTC

    We have tested the patch on our test cluster before releasing. We are now proceeding to deploy to the cluster. Thanks for your patience.

    UPDATE: jobs suspended, scheduler down for patching, nodes are updating.

  • 조사 중UTC

    The Slurm emergency security patch introduced a bug which is causing many of our nodes to be set to 'not responding'. The vendor has already identified the issue and issued another patch.

    We are deploying this patch after testing. Jobs will be paused and the scheduler and cluster will be unavailable while deploying the patch. Watch here for updates.

4월 2022

A cooling incident at the MGHPCC Datacenter has effected a number of systems
해결됨심각한 장애3시간 20분
  • 해결됨UTC

    All cooling, including the water cooling for water-cooled compute nodes, is back online. All partitions are open for jobs. Some compute nodes in various partitions may still require individual attention, so not every compute node is back online, but we will work to bring them all online in the coming hours.

  • 모니터링 중UTC

    Most storage in Holyoke is back up.

    The Slurm scheduler is back up and accepting jobs. However, most public partitions are down as the water cooling systems for those compute racks require in-person attention. RC staff are already en route to the datacenter to address this.

    The Academic Cluster is back up.

  • 조사 중UTC

    A cooling failure caused temperatures in the MGHPCC datacenter to exceed the safe range of operation for many systems, causing them to power down to prevent permanent damage.

    The cooling issue has been resolved and we are beginning to power systems back on. Expect outage on various systems until the issue is resolved.

  • 모니터링 중UTC

    A cooling failure caused temperatures in the MGHPCC datacenter to exceed the safe range of operation for many systems, causing them to power down to prevent permanent damage.

    The cooling issue has been resolved and we are beginning to power systems back on. Expect outage on various systems until the issue is resolved.

3월 2022

이전

3월 2022 ~ 5월 2022

다음