FAS Research Computing - Notice history

System Under Maintenance

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.
Under maintenance

SLURM Scheduler - Cannon - Under maintenance

Cannon Compute Cluster (Holyoke) - Under maintenance

Boston Compute Nodes - Under maintenance

GPU nodes (Holyoke) - Under maintenance

seas_compute - Under maintenance

Under maintenance

SLURM Scheduler - FASSE - Under maintenance

FASSE Compute Cluster (Holyoke) - Under maintenance

Under maintenance

Kempner Cluster CPU - Under maintenance

Kempner Cluster GPU - Under maintenance

Under maintenance
Under maintenance

Login Nodes - Holyoke - Under maintenance

Login Nodes - Boston - Under maintenance

FASSE login nodes - Under maintenance

Under maintenance

Cannon Open OnDemand - Under maintenance

FASSE Open OnDemand - Under maintenance

Operational

Netscratch (Global Scratch) - Operational

Home Directory Storage - Boston - Operational

Tape - (Tier 3) - Operational

Holylabs - Operational

Isilon Storage Holyoke (Tier 1) - Operational

Holystore01 (Tier 0) - Operational

HolyLFS04 (Tier 0) - Operational

HolyLFS05 (Tier 0) - Operational

HolyLFS06 (Tier 0) - Operational

Holyoke Tier 2 NFS - Operational

Holyoke Specialty Storage - Operational

holECS - Operational

Isilon Storage Boston (Tier 1) - Operational

BosLFS02 (Tier 0) - Operational

Boston Tier 2 NFS - Operational

CEPH Storage Boston (Tier 2) - Operational

Boston Specialty Storage - Operational

bosECS - Operational

Samba Cluster - Operational

Globus Data Transfer - Operational

Notice history

View current status

May 2024

MAY29
NESE Tape unavailable due to maintenance, ETA now Monday
ResolvedMaintenance117 hours 55 minutes
  • ResolvedUTC

    NESE maintenance has resolved and is now back in service

  • MonitoringUTC

    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.

  • IdentifiedUTC

    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

MAY21
Annual MGHPCC/Holyoke data center power downtime - May 21-24 2024
CompletedMaintenance80 hours 50 minutes
  • CompletedMay 24, 2024 at 9:50 PMUTC

    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  

  • UpdateMay 24, 2024 at 9:08 PMUTC

    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.

  • UpdateMay 24, 2024 at 1:47 PMUTC

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

  • In progressMay 21, 2024 at 1:00 PMUTC
    Maintenance is now in progress
  • PlannedMay 21, 2024 at 1:00 PMUTC

    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
Resolved55 minutes
  • ResolvedUTC
    This incident has been resolved.
  • IdentifiedUTC

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

  • InvestigatingUTC

    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
Resolved13 hours 13 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    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/

  • IdentifiedUTC

    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

  • InvestigatingUTC

    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
Resolved13 hours 32 minutes
  • ResolvedUTC

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

  • InvestigatingUTC

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

Apr 2024

Scratch under high load
Resolved57 minutes
  • ResolvedUTC

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

  • InvestigatingUTC

    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
Resolved450 hours
  • ResolvedUTC

    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.

  • InvestigatingUTC

    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
Resolved46 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    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
ResolvedDegraded performance1 hour 35 minutes
  • ResolvedUTC

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

  • InvestigatingUTC

    gpu_test is down again due to an IB switch failing

    the gpu partition in FASSE is also down

gpu_test partition down
ResolvedDegraded performance43 minutes
  • ResolvedUTC

    gpu_test is now operational and can be used.

    This incident has been resolved.

  • InvestigatingUTC

    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.

Mar 2024

Internet acces to Holyoke interrupted 7:30-8am
Resolved
  • 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
Resolved119 hours 57 minutes
  • ResolvedUTC

    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.

  • InvestigatingUTC

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

  • UpdateUTC

    Holylabs locked up again overnight. We are investigating.

  • MonitoringUTC

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

holyscratch01 performance degraded
Resolved139 hours 27 minutes
  • ResolvedUTC

    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.

  • MonitoringUTC

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

  • InvestigatingUTC

    holyscratch01 performance degraded

    We are currently investigating this incident.

RC Ticket System and other VMs Offline - Expect Delays, emails will be delivered eventually
Resolved1 hour 14 minutes
  • ResolvedUTC

    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.

  • InvestigatingUTC

    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)
Resolved5 hours 23 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC

    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

Previous

Mar 2024 to May 2024

Next

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