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 - 运行正常

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 (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 - 运行正常

历史记录

5月 2026

Cannon cluster down
  • 已解决
    UTC
    已解决

    Slurm crashed on 4:30p on Friday due to a user running a large sacct query against the Slurm database. This caused the database host to run out of memory and crash the scheduler. To prevent this from reoccurring we are reducing the time range that users are permitted to query at one time to 7 days. Thus if you need to cover a month you would need to query in four 7 day increments.

    We do ask users to be judicious in their querying of the Slurm. Only ask for those fields that you require. Please also ensure any AI agents you have running limit their queries appropriately.

  • 已确认问题
    UTC
    已确认问题

    To temporarily stabilize the situation, we have reduced the maximum query time for sacct and other Slurm commands to be 1 day. We have filed a ticket with SchedMD to further analyze the issue.

    The cluster is back up and the scheduler is accepting new jobs.

    We will continue to monitor for emergencies over the weekend, and resume in-depth troubleshooting on Monday.

  • 调查中
    UTC
    调查中

    The Slurm scheduler is experiencing an error which is impacting jobs. The Cannon cluster will be inaccessible while we troubleshoot.

    We are currently investigating this incident.

Account approvals down
  • 已解决
    UTC
    已解决

    This incident has been resolved. Login is again available for approvals/onboarding.

  • 调查中
    UTC
    调查中

    Account approvals through Portal are not available at this time.

    We are currently investigating this incident.

FASRC VPN (Cambridge) is back up
  • 已解决
    UTC
    已解决
    FASRC VPN (Cambridge) is back up. This incident was automatically resolved by Instatus monitoring.
  • 调查中
    UTC
    调查中
    FASRC VPN (Cambridge) is down at the moment. This incident was automatically created by Instatus monitoring.
FASRC VPN (Cambridge) is back up
  • 已解决
    UTC
    已解决
    FASRC VPN (Cambridge) is back up. This incident was automatically resolved by Instatus monitoring.
  • 调查中
    UTC
    调查中
    FASRC VPN (Cambridge) is down at the moment. This incident was automatically created by Instatus monitoring.
FASRC VPN (Cambridge) is back up
  • 已解决
    UTC
    已解决
    FASRC VPN (Cambridge) is back up. This incident was automatically resolved by Instatus monitoring.
  • 调查中
    UTC
    调查中
    FASRC VPN (Cambridge) is down at the moment. This incident was automatically created by Instatus monitoring.

4月 2026

OpenOnDemand maintenance
  • 已完成
    四月 30, 2026 在 下午 2:00UTC
    已完成
    四月 30, 2026 在 下午 2:00UTC
    Maintenance has completed successfully
  • 进行中
    四月 30, 2026 在 下午 12:00UTC
    进行中
    四月 30, 2026 在 下午 12:00UTC
    Maintenance is now in progress
  • 已计划
    四月 30, 2026 在 下午 12:00UTC
    已计划
    四月 30, 2026 在 下午 12:00UTC

    At 8am on Thursday April 30th we will be upgrading from Open OnDemand version 4.0.7 to 4.1.4 on both the Cannon and FASSE clusters.

    This is not expected to impact running jobs.

    This upgrade adds the Jobs->Project Manager menu item and fixes an issue that affected access to the Clusters->Shell Access menu item when using Firefox.

login.rc.fas.harvard.edu is responding normally
  • 已解决
    UTC
    已解决
    \[login.rc.fas.harvard.edu\](http://login.rc.fas.harvard.edu) is responding normally. This incident was automatically resolved.
  • 调查中
    UTC
    调查中
    login.rc.fas.harvard.edu is not responding normally. This incident was automatically created.
Login and OOD node access restricted due to serious security issue - No ETA
  • 已解决
    UTC
    已解决

    The cluster has been rebooted and all nodes, including login and OOD, have been patched.

    The scheduler is re-opened and jobs which were preempted/requeued have priority for re-scheduling.

    Some non-standard, lab-owned nodes may still require patching. The owners of these machines may be contacted about this.

    Thank you for your patience. This is a global issue and is being addressed at centers everywhere.

  • 更新
    UTC
    更新

    To mitigate this exploit we will need to restart -all nodes- on the cluster.

    This will begin at 1PM and run until all nodes have restarted (no ETA).

    This will mean any un-finished jobs will be terminated. There is no way to avoid this.

    We will then be validating the fix before re-opening the login. OOD nodes, and scheduler.

    Next steps and updates will be posted here.

  • 更新
    UTC
    更新

    We are developing a plan of attack to mitigate this exploit. Please know that this is a very serious issue and so we are treating it as such. Thank you for your understanding.

    We are currently awaiting further information from the Redhat/Fedora/Rocky community but building a plan in the meantime with the information we have. More details to follow as we can share them.

    If you need to access storage (except scratch and home directories), Globus is still online and available. But again, login nodes and OOD are not available.

  • 已确认问题
    UTC
    已确认问题

    Due to a serious in-the-wild exploit which can compromise Fedora-based Linux distributions including Rocky, which is used on the cluster, we need to restrict access. All login and OOD nodes are shut down until a fix can be put in place. Jobs running on the cluster will continue running.

    No ETA, There is not fix at this time. We will update our status page in the morning once we have more information or a fix to roll out.

    This is a serious exploit and we do not take this measure lightly. Please follow this status page for updates and eventual resolution.

holylfs06 down
  • 已解决
    UTC
    已解决

    Holylfs06 is accessible again.

    This incident has been resolved.

  • 已确认问题
    UTC
    已确认问题
    Holylfs06 storage is down. We are investigating. More details as they are known.
Website security maintenance (www.rc and docs.rc) 4-28-26 1pm
  • 已完成
    四月 28, 2026 在 下午 5:16UTC
    已完成
    四月 28, 2026 在 下午 5:16UTC

    Website maintenance has completed successfully.

  • 进行中
    四月 28, 2026 在 下午 5:00UTC
    进行中
    四月 28, 2026 在 下午 5:00UTC
    Maintenance is now in progress
  • 已计划
    四月 28, 2026 在 下午 5:00UTC
    已计划
    四月 28, 2026 在 下午 5:00UTC

    Security updates are required for www.rc.fas.harvard.edu and docs.rc.fas.harvard.edu
    This work will take place today between 1pm and 2pm
    Both sites will be down for very short periods during the updates.

3月 2026

Scheduler is degraded
  • 已解决
    UTC
    已解决

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

  • 调查中
    UTC
    调查中

    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
  • 已解决
    UTC
    已解决

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

  • 调查中
    UTC
    调查中

    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
  • 已解决
    UTC
    已解决
    This incident has been resolved.
  • 调查中
    UTC
    调查中
    We are currently investigating this incident.
Network issues - Cluster degraded
  • 已解决
    UTC
    已解决

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

  • 持续监控中
    UTC
    持续监控中

    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.

  • 已确认问题
    UTC
    已确认问题

    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.

  • 调查中
    UTC
    调查中

    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.
  • 已解决
    UTC
    已解决

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

  • 已确认问题
    UTC
    已确认问题

    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.

3月 2026 至 5月 2026

下一页

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