FAS Research Computing - Historia powiadomień

System w trakcie konserwacji

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

SLURM Scheduler - Cannon - Przerwa techniczna

Cannon Compute Cluster (Holyoke) - Przerwa techniczna

Boston Compute Nodes - Przerwa techniczna

GPU nodes (Holyoke) - Przerwa techniczna

seas_compute - Przerwa techniczna

Przerwa techniczna

SLURM Scheduler - FASSE - Przerwa techniczna

FASSE Compute Cluster (Holyoke) - Przerwa techniczna

Przerwa techniczna

Kempner Cluster CPU - Przerwa techniczna

Kempner Cluster GPU - Przerwa techniczna

Poprawne działanie

FASSE login nodes - Poprawne działanie

Poprawne działanie

Cannon Open OnDemand - Poprawne działanie

FASSE Open OnDemand - Poprawne działanie

Częściowa awaria

Netscratch (Global Scratch) - Poprawne działanie

Home Directory Storage - Boston - Poprawne działanie

Tape - (Tier 3) - Poprawne działanie

Holylabs - Poprawne działanie

Isilon Storage Holyoke (Tier 1) - Poprawne działanie

Holystore01 (Tier 0) - Poprawne działanie

HolyLFS04 (Tier 0) - Poprawne działanie

HolyLFS05 (Tier 0) - Poprawne działanie

HolyLFS06 (Tier 0) - Obniżona wydajność

Holyoke Tier 2 NFS - Częściowa awaria

Holyoke Specialty Storage - Poprawne działanie

holECS - Poprawne działanie

Isilon Storage Boston (Tier 1) - Poprawne działanie

BosLFS02 (Tier 0) - Poprawne działanie

Boston Tier 2 NFS - Poprawne działanie

CEPH Storage Boston (Tier 2) - Poprawne działanie

Boston Specialty Storage - Poprawne działanie

bosECS - Poprawne działanie

Samba Cluster - Poprawne działanie

Globus Data Transfer - Poprawne działanie

Historia powiadomień

Zobacz bieżący status

lip 2024

LIP30
Coldfront maintenance 7/30/24 noon-12:30
ZakończonoKonserwacja58 minut
  • Zakończono
    lipca 30, 2024 o 16:58UTC
    Zakończono
    lipca 30, 2024 o 16:58UTC

    Maintenance completed.

  • Zaplanowana
    lipca 30, 2024 o 16:00UTC
    Zaplanowana
    lipca 30, 2024 o 16:00UTC
    Coldfront will be unavailable Tuesday July 30th from 12:00-12:30 for crucial maintenance.
boslfs02 down
RozwiązanyObniżona wydajność20 minut
  • Rozwiązany
    UTC
    Rozwiązany
    boslfs02 is back up
  • Zidentyfikowany
    UTC
    Zidentyfikowany
    boslfs02 is currently experiencing degraded performance. We are actively working on this issue.
Authentication issues - Related to global Crowdstrike incident
RozwiązanyCzęściowa awaria75 godzin 59 minut
  • Rozwiązany
    UTC
    Rozwiązany

    All Crowdstrike-related resources are back up and operational.

  • Aktualizacja
    UTC
    Aktualizacja
    For FASRC resources affected by the Crowdstrike issue, most are back in full services. A few remaining issues involving the following may not be resolved until Monda: - waywiser2 - proteomics2 - tmsdb3 - lic3
  • Aktualizacja
    UTC
    Aktualizacja

    Please see HUIT Status (harvard.edu) for additional information on the global issue caused by Crowdstrike security which Harvard relies on. This is an ongoing issue university-wide.

    The systems that continue to be affected at FASRC are minimal, but some Windows-based systems managed by or connected to FASRC may still be affected.

  • Monitorowanie
    UTC
    Monitorowanie

    Authentication is back up and running. Windows machines are still in a bad state and will need remedial work to get them back in service.

  • Zidentyfikowany
    UTC
    Zidentyfikowany

    Authentication is back up and running. Windows machines are still in a bad state and will need remedial work to get them back in service.

  • Analiza
    UTC
    Analiza

    Authentication is back up and running. Windows machines are still in a bad state and will need remedial work to get them back in service.

LIP18
boslogin01 rebooting
RozwiązanyKonserwacjagodzina 8 minut
  • Rozwiązany
    UTC
    Rozwiązany
    boslogin01 is rebooted and ready for use.
  • Zidentyfikowany
    UTC
    Zidentyfikowany
    boslogin01 will be rebooted at 11:05AM. Due to stuck mounts it is currently not working as expected. Please save any necessary work before the reboot.
Infiniband networking down
Rozwiązany13 minut
  • Aktualizacja
    UTC
    Aktualizacja
    This incident has been resolved.
  • Rozwiązany
    UTC
    Rozwiązany
    Infiniband has been restored
  • Zidentyfikowany
    UTC
    Zidentyfikowany
    The Infiniband fabric in MGHPCC that connects nodes with high-speed fiber is down. We are investigating. This _will_ cause performance issues and jobs may be stalled. Updates as we learn more.

cze 2024

Holylabs down
RozwiązanyPoważna awaria11 minut
  • Rozwiązany
    UTC
    Rozwiązany

    Holylabs has finished rebooting and should be accessible. This incident has been resolved.

  • Analiza
    UTC
    Analiza

    Due to mounting and access issues, holylabs needs to be rebooted. It will be unavailable during this time. We will update once it is back up.

FASRC websites unavailable
Rozwiązany6 minut
  • Rozwiązany
    UTC
    Rozwiązany

    This incident has been resolved. Both sites are working normally.

  • Analiza
    UTC
    Analiza

    https://www.rc.fas.harvard.edu/ and https://docs.rc.fas.harvard.edu/ are offline.

    We are currently investigating this issue.

Scratch instability
RozwiązanyObniżona wydajność41 minut
  • Rozwiązany
    UTC
    Rozwiązany
    This incident has been resolved.
  • Analiza
    UTC
    Analiza

    Global scratch (/n/holyscratch01) is currently experiencing instability.

    We are currently investigating this incident.

CZE24
MGHPCC Pod 8A Power Upgrade June 24 will idle some Cannon nodes
ZakończonoKonserwacja23 godziny 59 minut
  • Zakończono
    czerwca 25, 2024 o 04:00UTC
    Zakończono
    czerwca 25, 2024 o 04:00UTC
    Maintenance has completed successfully
  • W trakcie
    czerwca 24, 2024 o 16:01UTC
    W trakcie
    czerwca 24, 2024 o 16:01UTC
    Maintenance is now in progress
  • Zaplanowana
    czerwca 24, 2024 o 04:01UTC
    Zaplanowana
    czerwca 24, 2024 o 04:01UTC

    MGHPCC will be performing power upgrades on Pod 8A in order to increase density and allow more nodes to be added in that Pod's rows.  Similar to the May 13th work, this means that we will be idling half the nodes in 8A on two dates: June 17 and June 24th.

    These are all day events, meaning that the nodes in question will not be available for the 24 hours of that day.  This is being accomplished via reservations. So no jobs will be canceled but nodes will be drained and users may notice that their jobs may pend longer than normal as the scheduler idles these nodes.

    Where possible, please use or include other partitions in your job scripts and plan accordingly for any new or long-running jobs during that period: https://docs.rc.fas.harvard.edu/kb/running-jobs/#Slurm_partitions

    This affects the Cannon cluster. FASSE is not affected.

    Impacted partitions are:

    arguelles_delgado_gpu

    bigmem_intermediate

    bigmem

    blackhole_gpu

    eddy

    enos

    gershman gpu

    hejazi hernquist_ice

    hoekstra hsph

    huce_ice

    iaifi_gpu

    iaifi_gpu_priority

    iaifi_gpu_requeue

    intermediate

    itc_gpu

    itc_gpu_requeue

    joonholee

    jshapiro

    jshapiro_priority

    jshapiro_sapphire

    kempner

    kempner_dev

    kempner_h100

    kempner_requeue

    kempner_reservation

    kovac

    kozinsky

    kozinsky_gpu

    kozinsky_priority

    kozinsky_requeue

    murphy_ice

    ortegahernandez_ice

    sapphire

    seas_compute

    seas_gpu siag

    siag_combo

    siag_gpu

    sur test

    yao

    yao_priority

    zhuang

Coldfront down
Rozwiązany5 godzin 13 minut
  • Rozwiązany
    UTC
    Rozwiązany

    Coldfront is operating normally and to root cause has been determined and confirmed to be resolved.

  • Analiza
    UTC
    Analiza

    Coldfront is currently inaccessible to users. We are investigating this incident.

maj 2024

MAJ29
NESE Tape unavailable due to maintenance, ETA now Monday
RozwiązanyKonserwacja117 godzin 55 minut
  • Rozwiązany
    UTC
    Rozwiązany

    NESE maintenance has resolved and is now back in service

  • Monitorowanie
    UTC
    Monitorowanie

    A note from NESE. Their maintenance has been delayed by hardware issues. ETA now Monday 6/3

    Dear All,

    NESE Tape system upgrade is currently in progress. While IBM hardware
    team works on TS4500 library tape frame expansion and IBM software team
    works on ESS and Archive software and firmware upgrades, the work
    progress has been slowed down due to unforeseen hardware issues.We now expect to bring the tape service back into production this Monday
    morning. We apologize for any inconvenience caused by the delay.

  • Zidentyfikowany
    UTC
    Zidentyfikowany

    Due to maintenance at our tape partner, NESE (Northeast Storage Exchange), access to tape allocations will be unavailable until at least late Thursday (5/30). Normal operations will resume by Friday (5/31).

    If you continue to have issues with a Globus tape endpoint on Friday, please contact FASRC or NESE

MAJ21
Annual MGHPCC/Holyoke data center power downtime - May 21-24 2024
ZakończonoKonserwacja80 godzin 50 minut
  • Zakończono
    maja 24, 2024 o 21:50UTC
    Zakończono
    maja 24, 2024 o 21:50UTC

    2024 MGHPCC downtime complete

    DOWNTIME COMPLETE

    The annual multi-day power downtime at MGHPCC (https://www.rc.fas.harvard.edu/blog/2024-mghpcc-power-downtime/) is complete (with any exceptions noted below). Normal service resumes today (Friday May 24th) at 5pm.

    The cluster has been updated to Rocky Linux 8.9. Several network, InfiniBand, computer, and storage firmware updates were installed. Available security updates were also installed.

    CANNON NODES

    More than 90% of nodes are up and all partitions are enabled. If your specialty partition has a downed node, we will attend to this on Tuesday.

    FASSE OOD

    Some updates are still propagating. If your FASSE Open OnDemand/VDI session does not work initially, please wait or retry your job/session.

    POST-DOWNTIME SUPPORT

    If you have any further concerns or unanswered questions please submit a help ticket (https://portal.rc.fas.harvard.edu/rcrt/submit_ticket) and we will do our best to respond quickly. Please bear in mind it is a long weekend, so lingering issues may not be dealt with until Tuesday.

    Also, have a good long Memorial Day weekend!

    Thanks,

    FAS Research Computing

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

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

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

    rchelp@rc.fas.harvard.edu  

  • Aktualizacja
    maja 24, 2024 o 21:08UTC
    Aktualizacja
    maja 24, 2024 o 21:08UTC

    We are currently delayed opening the cluster due to some lingering issues.

    We will re-open as soon as possible or update again at 6pm.

  • Aktualizacja
    maja 24, 2024 o 13:47UTC
    Aktualizacja
    maja 24, 2024 o 13:47UTC

    Power work completed by facility. Currently on schedule for powerup and return to service. ETA 5pm.

  • W trakcie
    maja 21, 2024 o 13:00UTC
    W trakcie
    maja 21, 2024 o 13:00UTC
    Maintenance is now in progress
  • Zaplanowana
    maja 21, 2024 o 13:00UTC
    Zaplanowana
    maja 21, 2024 o 13:00UTC

    The 2024 MGHPCC data center annual power downtime will take place May 21-24, 2024.

    We will begin our shutdown on Tuesday May 21st and expect a return to service by 5PM Friday May 24th.

    - Jobs: Please plan ahead as all still running jobs on the morning of May 21st will be stopped and canceled and will need to be resubmitted after the downtime. Pending jobs will remain in the queue until the cluster returns to regular service on May 24th.

    - Access: The cluster, scheduler, login, and OoD nodes will be unavailable for the duration of the downtime. New lab and account requests should wait until after the downtime.

    - Storage: All Holyoke storage will be powered down and unavailable for the duration of the downtime. Boston storage will remain online, but your ability to access it may be impacted and network changes may briefly affect its availability.

    Further details, an explanation for this year's change in scheduling, a visual timeline, and a list of maintenance tasks overview can be found at:

    https://www.rc.fas.harvard.edu/blog/2024-mghpcc-power-downtime/

    Progress of the downtime will be posted here on our status page during the event. Note that you can subscribe to receive updates as they happen. Click Get Updates in the upper right.

    MAJOR TASK OVERVIEW

    • OS upgrade to Rocky 8.9 - Point upgrade, no code rebuilds will be required. Switch from system OFED to Mellanox OFED on nodes for improved performance

    • Infiniband (network) upgrades

    • BIOS updates (various)

    • Storage firmware updates

    • Network Maintenance

    • Decommission old nodes (targets contacted)

    • Additional minor one-off updates and maintenance (cable swap, reboots, etc.)

    Thanks,

    FAS Research Computing

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

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

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

Ticket system slow
Rozwiązany55 minut
  • Rozwiązany
    UTC
    Rozwiązany
    This incident has been resolved.
  • Zidentyfikowany
    UTC
    Zidentyfikowany

    Delayed email is the root of this issue. We are working to resolve or work around this issue.

  • Analiza
    UTC
    Analiza

    The ticketing system (which uses HUIT services) is experiencing lag. New ticket autoreplies and ticket responses may be delayed. We are currently investigating this incident.

Many nodes in 8A down - affects sapphire, test, bigmem, and other partitions
Rozwiązany13 godzin 13 minut
  • Rozwiązany
    UTC
    Rozwiązany
    This incident has been resolved.
  • Analiza
    UTC
    Analiza

    We are still unable to resolve the issue with these nodes and are working with the facility, networking, and our staff to find a solution. The affected partitions (noted in previous update below) will be resource-constrained and continue to be slow or unable to queue new jobs.


    If you are using a partition that cannot queue new jobs, please consider adding additional partitions to your job: https://docs.rc.fas.harvard.edu/kb/running-jobs/#Slurm_partitions

    Also, a reminder that the data center power downtime will begin Tuesday morning. So any new jobs scheduled for more than 3 days will not complete: https://www.rc.fas.harvard.edu/blog/2024-mghpcc-power-downtime/

  • Zidentyfikowany
    UTC
    Zidentyfikowany

    We are still working on the root cause and resolution for these downed nodes.

    Partitions with one or more affected nodes [involves multiple nodes unless denoted as (1) ]:

    arguelles_delgado_gpu (1)

    hsph

    joonholee

    jshapiro_sapphire

    lichtmandce01

    bigmem

    gpu_requeue (1)

    intermediate

    sapphire

    serial_requeue (1)

    shared (1)

    test

    yao / yao_priority

    use 'sinfo -p [partition name]' if you wish to see the down nodes in particular queue

  • Analiza
    UTC
    Analiza

    We are currently investigating this incident. An unknown outage has downed many nodes in row 8A of our data center. More information to follow.

    Includes nodes from the sapphire, test, gpu, and other partitions.

Problem with holystore01
Rozwiązany13 godzin 32 minuty
  • Rozwiązany
    UTC
    Rozwiązany

    holystore01 is back to normal operation. Please report any continued issues with holystore01 to FASRC.

  • Analiza
    UTC
    Analiza

    We are currently investigating a hardware problem on holystore01. This may affect file access, conda/mamba environments, and some logins.

Poprzednia

maj 2024 do lip 2024

Następny

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