FAS Research Computing - அறிவிப்பு வரலாறு

BosLFS02 (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 - இயங்குகிறது

அறிவிப்பு வரலாறு

தற்போதைய நிலையைக் காண்க

ஜூலை 2023

Numerous nodes in bad state
தீர்க்கப்பட்டது1 மணி நேரம் 17 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    The affected partitions are back up within acceptable operating percentages.

  • அடையாளம் காணப்பட்டதுUTC

    Numerous nodes are in a bad state (marked 'drng', but not those marked 'drain'). We are aware and are working to re-open these nodes as quickly as possible.

    This includes but is not limited to nodes in: argelles-delgado, kozinsky, seas_compute, kempner, and other partitions.

Software modules not available
தீர்க்கப்பட்டதுபகுதி செயலிழப்பு35 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    Modules should be available again across Cannon and FASSE. If you have an open session, please log out and log in again to use modules.

    This incident has been resolved.

  • விசாரிக்கப்படுகிறதுUTC

    An unexpected bug has broken software module availability at this time. Module commands such as module load, module spider, etc may not work.

    We are currently investigating this incident.

Access Issues with holylabs storage server
தீர்க்கப்பட்டது23 மணி நேரம் 50 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    This incident has been resolved.

  • புதுப்பிப்புUTC

    We have brought the server back online in a "workaround" state and will be continuing to investigate the root cause. Access should be normal.

  • விசாரிக்கப்படுகிறதுUTC

    Lab Storage on holylabs file server is currently inaccessible. We are currently investigating this incident.

boslfs02 down
தீர்க்கப்பட்டதுபெரிய செயலிழப்பு12 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    This incident has been resolved.

  • விசாரிக்கப்படுகிறதுUTC

    boslfs02 is currently inaccessible. We are investigating this incident.

A100 GPU issue
தீர்க்கப்பட்டது986 மணி நேரம் 51 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    Firmware updates have resolved this issue.

  • புதுப்பிப்புUTC

    The proscribed driver update did not fix this issue.

    We are working with Nvidia to find a fix. As a stop-gap nodes which get stuck/flagged will be marked in Slurm for reboot and rebooted once empty of jobs.

    If a A100 GPU host your lab owns is stuck in a bad state, please let us know and we will mark and reboot it.

  • அடையாளம் காணப்பட்டதுUTC

    A100s are open but still experiencing some instability. Infrequently, you may hit the issue we noted earlier.

    We are continuing to work on a solution.

  • விசாரிக்கப்படுகிறதுUTC

    An NVIDIA bug may be causing failures in A100 GPUs. nvidia-smi command is slow, or outputs "ERR!" or "No GPUs are found".

    Jobs on affected nodes may fail.

    We are investigating this issue.

ஜூன் 2023

Mounting storage from campus network
தீர்க்கப்பட்டதுசெயல்திறன் குறைந்துள்ளது6 மணி நேரம் 50 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    This incident has been resolved.

  • விசாரிக்கப்படுகிறதுUTC

    Due to a HUIT networking issue, mounting storage from wired campus connections may not work.

    We are working with HUIT to resolve this.

    In the meantime, you should still be able to mount storage while connected to the RC VPN.

ஜூன்20
Emergency maintenance 6/20/23 - Cannon Slurm Scheduler
முடிந்ததுபராமரிப்பு
  • திட்டமிடப்பட்டதுஜூன் 20, 2023 இல் முற்பகல் 11:00UTC

    WHAT
    Emergency Cannon cluster scheduler maintenance Tuesday June 20th from 7am - 11am (actual end time estimated). Running jobs will be paused during maintenance.

    Note: FASSE is unaffected by this.

    WHY
    As most of you know, there are on-going issues with the Cannon scheduler after the downtime and OS upgrades. This behavior did not show up in our earlier testing and only manifested once we were under load from user jobs again.

    After investigation we found that the scheduler is oscillating between two states every hour. During even hours the scheduler would enter a high thread state where all the traffic would pile up, causing any queries to either take a long time or time out. During odd hours the scheduler would enter a low thread state and operate normally. During periods where the scheduler is responding, jobs can be submitted and should then run normally.

    Unfortunately the root cause is still not known, and we are working closely with the vendor, SchedMD, to find a solution to return the cluster to stability. The version of slurm that we are running is 22.05.7, which while very stable — we have been running on it for the past 5 months with no problems — appears to be having issues at scale on Rocky 8.

    There is a newer version of the scheduler available, 23.02.3. This new version has a host of improvements. While the specific issue described above is not listed as one of the items fixed in this version, we anticipate that the upgrade may fix this issue owing to the various code improvements contained therein.

    Barring any solutions found over the long weekend, we intend to hold an emergency maintenance period on Tuesday June 20th starting at 7am. Running jobs will be paused. We will return Cannon to service as soon as we've completed work. Status of this maintenance will be tracked here on our status page.

    We thank you for your patience and understanding. Our team is hard at work answering your tickets and making sure that the cluster is back to full health. Also as a reminder that we hold additional Office Hours each week in June. See: https://www.rc.fas.harvard.edu/training/office-hours/

    FAS Research Computing
    https://www.rc.fas.harvard.edu/
    https://docs.rc.fas.harvard.edu/
    https://status.rc.fas.harvard.edu/

  • முடிந்ததுஜூன் 20, 2023 இல் முற்பகல் 1:16UTC

    CANCELLED

    Emergency maintenance has has been cancelled. A solution to the scheduler issue has been found and Slurm is once again operating normally.

    We thank you for your patience and understanding.

Slurm scheduler slowness/delays
தீர்க்கப்பட்டது155 மணி நேரம் 8 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    This incident has been resolved.

    A solution to the Slurm scheduler issue has been found and implemented. The scheduler is now operating normally.

    Thank you for your patience and understanding.

  • புதுப்பிப்புUTC

    PLEASE SEE EMERGENCY MAINTENANCE NOTICE BELOW
    Emergency maintenance Tuesday June 20th 7am-11am. Running jobs will be paused.

    We are still working on finding the root cause of the scheduler slowness and timeouts. We are working with SchedMD and have sent diagnostic information for analysis.

    At this time the scheduler is up but may become unresponsive to your commands at times. You can wait and retry them.

    Jobs, once launched, should run as expected.

    OOD/VDI are working, but job submission may also be affected.

    If you receive salloc: error: Job submit/allocate failed: Invalid account or account/partition combination specified, waiting a moment and re-submitting your job again should result in a successful submission.

    Addendum: It was determined that the issue is cyclical and you will have the best luck during odd hours (e.g. - after 1pm, before 2pm) and less success interfacing with the scheduler during even hours (e.g. - after 2pm, before 3pm).

    We regret the impact this is having on your work. Updates will follow as we have them.

  • புதுப்பிப்புUTC

    We are still working on finding the root cause of the slowness and are working with the vendor to troubleshoot.

    At this time the scheduler is up but may become responsive to your commands at times. Jobs, once launched, should run as expected.

  • புதுப்பிப்புUTC

    Slurm is still being overwhelmed with large numbers of requests. VDI timeouts/502 errors, interactive job connections, job submissions, are all impacted.

    We are in contact with the Slurm developers to find a better resolution.

  • கண்காணிக்கப்படுகிறதுUTC

    We have implemented updates and the scheduler appears stable and responsive.
    We will continue to monitor and update this incident.

  • விசாரிக்கப்படுகிறதுUTC

    We are currently investigating performance issues with the scheduler. This manifests in slowness when submitting jobs, job submission fails some percentage of the time, and timeout errors (including OOD/VDI).

    Also, some jobs may not exit cleanly putting nodes into drain status.

    We are working to resolve this issue. Updates to follow.

Cannon and FASSE OOD (VDI) issues
தீர்க்கப்பட்டது24 மணி நேரம் 35 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    This incident has been resolved. FASSE and Cannon OOD are both available.

  • கண்காணிக்கப்படுகிறதுUTC

    Cannon and FASSE OOD are not fully operational due to slurm being slow. With slurm slow, the apps wait too long to be launched and it can throw 502 errors

  • அடையாளம் காணப்பட்டதுUTC

    Cannon OOD is operational.

    FASSE OOD is still experiencing issues and showing errors for new connections. Existing connections are working.
    WIP

  • விசாரிக்கப்படுகிறதுUTC

    We are currently investigating issues with OOD (OpenOnDemand aka VDI).

fasselogin nodes
தீர்க்கப்பட்டது59 நிமிடங்கள்
  • தீர்க்கப்பட்டதுUTC

    Login to fasselogin is working. Additional login nodes are not in the rotation and will be added back once they are healthy again. But normal login is working.

  • விசாரிக்கப்படுகிறதுUTC

    We are currently investigating an issue with fasse login nodes (fasselogin) timing out or not connectring.

மே 2023

இந்த மாதம் அறிவிப்புகள் எதுவும் தெரிவிக்கப்படவில்லை

முந்தையது

மே 2023 வரை ஜூலை 2023

அடுத்து

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