FAS Research Computing - Shutdown nodes in 8A14, 8A16 and 8A18 - Cooling Leak – घटना विवरण

आंशिक रूप से प्रभावित प्रदर्शन का सामना कर रहा है

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.

Shutdown nodes in 8A14, 8A16 and 8A18 - Cooling Leak

हल हुआ
आंशिक आउटेज 30 %
शुरू हुआ १० महीने पहलेचला ४ दिन

प्रभावित

Cannon Cluster

आंशिक आउटेज से 9:45 PM तक 4:06 PM

SLURM Scheduler - Cannon

आंशिक आउटेज से 9:45 PM तक 4:06 PM

Cannon Compute Cluster (Holyoke)

आंशिक आउटेज से 9:45 PM तक 4:06 PM

Boston Compute Nodes

आंशिक आउटेज से 9:45 PM तक 4:06 PM

GPU nodes (Holyoke)

आंशिक आउटेज से 9:45 PM तक 4:06 PM

seas_compute

आंशिक आउटेज से 9:45 PM तक 4:06 PM

अपडेट
  • हल हुआ
    हल हुआ

    Thanks to staff that made multiple datacenter visits, the leak has been addressed and all systems are back up and running.

    This incident has been resolved.

  • निगरानी
    निगरानी

    8a14 and 8a18 are back online, 8a16 is still down

    That includes mweber_gpu and mweber_compute being back up and seas_gpu still partially down

  • अपडेट
    अपडेट

    Power and water is shutdown to these racks and the vendor is working to send someone in next working day to investigate. Partition totally down are mweber_compute, mweber_gpu, seas_gpu and seas_compute.

  • पहचाना गया
    पहचाना गया

    Row 8A18 (row 8A rack18) will also be shut down.

  • जांच जारी है
    जांच जारी है

    MGHPCC found a leak in 8A14 or 8A16 racks and asked us to shutdown those nodes. We are working with the vendor to fix the issue ASAP.