FAS Research Computing - 알림 내역

일부 시스템에서 성능 저하가 발생했습니다

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

FASSE Open OnDemand/VDI - 정상

정상

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 (new) - 정상

Holyoke Specialty Storage - 정상

holECS - 정상

Isilon Storage Boston (Tier 1) - 정상

BosLFS02 (Tier 0) - 정상

Boston Tier 2 NFS (new) - 정상

CEPH Storage Boston (Tier 2) - 정상

Boston Specialty Storage - 정상

bosECS - 정상

Samba Cluster - 정상

Globus Data Transfer - 정상

알림 내역

3월 2026

Scheduler is degraded
  • 해결됨
    해결됨

    This incident has been resolved. The scheduler is running normally.

  • 조사 중
    조사 중

    The scheduler is in a degraded state due to thrashing
    We are actively working to resolve this problem.

two-factor.rc.fas.harvard.edu (openauth) error
  • 해결됨
    해결됨

    This incident has been resolved. two-factor.rc.fas.harvard.edu is working normally again.

  • 조사 중
    조사 중

    We are currently investigating this incident. Requesting a new token or re-requesting your token from two-factor is not currently working.

The web front end to two-factor.rc.fas.harvard.edu is currently not allowing logins, generating new tokens is currently unavailable
  • 해결됨
    해결됨
    This incident has been resolved.
  • 조사 중
    조사 중
    We are currently investigating this incident.
Network issues - Cluster degraded
  • 해결됨
    해결됨

    This incident has been resolved by draining and rebooting any nodes with stuck mounts.

  • 모니터링 중
    모니터링 중

    Mounts to Holyoke Isilon (specifically /n/sw) are broken on numerous nodes across the cluster. We have a check rolling out to find these nodes so we can remediate them individually. Until remediated the cluster will be in a degraded state. Running jobs may randomly die or fail as they hit nodes that have stale mounts.

    It will be risky to run jobs for the next hour and then, after that point, the cluster will have a large number of nodes closed waiting for them to drain so we can reboot them and fix the mounts.

    At this time we are unaware of any holy-isilon problems other than the effect this had on cluster nodes/running jobs. We will update should we identify any data storage concerns.

  • 확인됨
    확인됨

    Mounts to Holyoke Isilon (specifically /n/sw) are broken on numerous nodes across the cluster. We have a check rolling out to find these nodes so we can remediate them individually. Until remediated the cluster will be in a degraded state. Running jobs may randomly die or fail as they hit nodes that have stale mounts.

    It will be risky to run jobs for the next hour and then, after that point, the cluster will have a large number of nodes closed waiting for them to drain so we can reboot them and fix the mounts.

  • 조사 중
    조사 중

    A network issue affecting storage critical to the cluster is It's causing instability. The cluster is currently in a degraded state as a result. We are looking into the problem. Updates to follow..

ColdFront is down.
  • 해결됨
    해결됨

    Cold front is back up. Thank you for your patience.

  • 확인됨
    확인됨

    ColdFront is down. We are working to bring it back up. The instance got replaced last night, but it had trouble configuring itself on the way up again.

2월 2026

Tape outage
  • 해결됨
    해결됨

    This incident has been resolved. Normal tape operations are restored.

  • 모니터링 중
    모니터링 중

    The tape library outage is further extended to Wednesday March 4th at 9am awaiting a hardware replacement part due today. Data can still be uploaded to lab collections via Globus, but be mindful of the 10 TB buffer file limit. The outage affects storage and recall from tape.

  • 확인됨
    확인됨

    NESE Tape Service is still working with IBM technical support at restoring the inventory. The expected downtime is extended until Tuesday March 3rd, 9am.
    Apologies for the inconvenvenience.

  • 조사 중
    조사 중

    NESE Tape service will be down or operating with degraded service (no store and recall) Friday from 12 Noon EST until as late as Monday, 2 March at 9 AM.

    SUMMARY OF ISSUE:

    NESE Tape service is currently not able to store or recall files to and from tape due to vendor firmware issues in the IBM TS4500 tape library. The issue is related to the library robotics and cartridge database and we do NOT expect any data loss from this issue.

    The issue is apparently due to an issue with the inventory database related to a recent firmware update. This database can be scrubbed and reconstructed by the library, which will scan the bar code labels on all the cartridges to rebuild the inventory. Association of files in Globus to tapes is handled separately from the tape library and is not affected by the firmware update.

Starfish dashboard is unavailable
  • 해결됨
    해결됨

    This incident has been resolved. The Starfish dashboard is available.

  • 조사 중
    조사 중

    The starfish dashboard is unavailable. We are currently investigating this issue with Starfish..

Starfish maintenance Feb 25, 2026 all day
  • 완료됨
    2월 26, 2026 ~에서 14:00
    완료됨
    2월 26, 2026 ~에서 14:00
    Maintenance has completed successfully
  • 진행 중
    2월 25, 2026 ~에서 14:00
    진행 중
    2월 25, 2026 ~에서 14:00
    Maintenance is now in progress
  • 예정됨
    2월 25, 2026 ~에서 14:00
    예정됨
    2월 25, 2026 ~에서 14:00

    Starfish will be unavailable starting Wednesday, February 25th at 9AM until Thursday, February 26th at 9AM, for routine maintenance. The online dashboard will be inaccessible during this time.

Authentication outage
  • 해결됨
    해결됨

    Openauth/radius is now operational. This update was created by an automated monitoring service.

  • 조사 중
    조사 중

    Authentication issues with openauth/radius. This incident was created by an automated monitoring service.

NESE tape maintenance Feb 19th 2026
  • 완료됨
    2월 19, 2026 ~에서 22:00
    완료됨
    2월 19, 2026 ~에서 22:00
    Maintenance has completed successfully
  • 진행 중
    2월 19, 2026 ~에서 13:00
    진행 중
    2월 19, 2026 ~에서 13:00
    Maintenance is now in progress
  • 예정됨
    2월 19, 2026 ~에서 13:00
    예정됨
    2월 19, 2026 ~에서 13:00

    From our partners at NESE. Details follow:

    We are installing four new tape frames, which will bring the tape system raw storage capacity to 253 petabytes.

    Service Affected: NESE Tape Service

    Maintenance Window: 8:00 AM - 5:00 PM (EST)

    • The tape service will be unavailable.

    • All upgrade activities are expected to be completed on the same day.

    NOTES:

    • Monitor the MGHPCC Slack #nese channel for status updates and announcements

    • Monitor https://nese.instatus.com/ for real-time updates on progress

    Subscribe to https://nese.instatus.com/subscribe/email for updates and announcements

1월 2026

Coldfront down
  • 해결됨
    해결됨

    Coldfront is operational. Thank you for your patience.

  • 조사 중
    조사 중

    We are currently investigating an issues with Coldfront. No ETA.

holystore01 down
  • 해결됨
    해결됨

    holystore01 is back up and usable.

    This incident has been resolved.

  • 조사 중
    조사 중

    The filesystem holystore01 is experiencing a network failure and in a bad state.

    Some files on holystore01 may not be accessible while this is ongoing. We are working to restore access, and apologize for the inconvenience.

Grafana Cloud is down
  • 해결됨
    해결됨
    is back up. This incident was automatically resolved by Instatus monitoring.
  • 조사 중
    조사 중
    is down at the moment. This incident was automatically created by Instatus monitoring.
holystore01 is wedging. We are rebooting.
  • 해결됨
    해결됨
    This incident has been resolved.
  • 확인됨
    확인됨

    holystore01 is wedging. We are rebooting.

FASRC monthly maintenance Monday January 12th, 2026 9am-1pm
  • 완료됨
    1월 12, 2026 ~에서 18:00
    완료됨
    1월 12, 2026 ~에서 18:00
    Maintenance has completed successfully
  • 진행 중
    1월 12, 2026 ~에서 14:00
    진행 중
    1월 12, 2026 ~에서 14:00
    Maintenance is now in progress
  • 예정됨
    1월 12, 2026 ~에서 14:00
    예정됨
    1월 12, 2026 ~에서 14:00

    Monthly maintenance will take place on January 12th, 2026. Our maintenance tasks should be completed between 9am-1pm.

    NOTICES:

    • Changes to SEAS partitions, please see tasks below.

    • Changes to job age priority weighting, please see tasks below.

    • Status Page: You can subscribe to our status to receive notifications of maintenance, incidents, and their resolution at https://status.rc.fas.harvard.edu/ (click Get Updates for options).

    • We'd love to hear success stories about your or your lab's use of FASRC. Submit your story here.

    MAINTENANCE TASKS

    Cannon cluster will be paused during this maintenance?: YES
    FASSE cluster will be paused during this maintenance?:YES

    • Slurm upgrade to 25.11.1

      • Audience: All cluster users (Cannon and FASSE)

      • Impact: Jobs will be paused during maintenance

    • In conjunction with SEAS we will modify seas_gpu and seas_compute time limits 

      • Audience: SEAS users

      • Impact:
        seas_gpu: will be set to 2 days maximum
        seas_compute: will be set to 3 days maximum

        Existing pending jobs longer than these limits will be set to 2 day and 3 day run times depending on partition.

    • Job Age Priority Weight Change

      • Audience: Cluster users

      • Impact: We will be adjusting the weight applied to the priority earned by jobs by virtue of their age. Currently job priority is made up of two factors, Fairshare and Job Age. The Job Age factor is currently set such that jobs gain priority over 3 days with a maximum priority equivalent to jobs with Fairshare of 0.5. This keeps low fairshare jobs from languishing at the bottom of the queue. With the current settings though, users with low fairshare can gain significant advantage over users with higher relative fairshare. To remedy this we will be adjusting the Job Age weight to cap out at an equivalent Fairshare of 0.1. This will still allow jobs with 0 fairshare to gain priority and thus not languish while letting fairshare govern a wider range of higher priority jobs.

    • Login node reboots

      • Audience; All login node users

      • Impact: Login nodes will reboot during the maintenance window

    • Open OnDemand (OOD) node reboots

      • Audienc:; All OOD users

      • Impact: OOD nodes will reboot during the maintenance window

    • Netscratch retention will run

      • Audience: All cluster netscratch users

      • Impact: Files older than 90 days will be removed. Please note that retention cleanup can and does run at any time, not just during the maintenance window.

    Thank you,
    FAS Research Computing
    https://docs.rc.fas.harvard.edu/
    https://www.rc.fas.harvard.edu/

1월 2026 ~ 3월 2026

다음

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