FAS Research Computing - Kunngjøringshistorikk

BosLFS02 (Tier 0) opplever større avbrudd

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.
Operasjonell

SLURM Scheduler - Cannon - Operasjonell

Cannon Compute Cluster (Holyoke) - Operasjonell

Boston Compute Nodes - Operasjonell

GPU nodes (Holyoke) - Operasjonell

seas_compute - Operasjonell

Operasjonell

SLURM Scheduler - FASSE - Operasjonell

FASSE Compute Cluster (Holyoke) - Operasjonell

Operasjonell

Kempner Cluster CPU - Operasjonell

Kempner Cluster GPU - Operasjonell

Operasjonell

FASSE login nodes - Operasjonell

Operasjonell

Cannon Open OnDemand - Operasjonell

FASSE Open OnDemand - Operasjonell

Større avbrudd

Netscratch (Global Scratch) - Operasjonell

Home Directory Storage - Boston - Operasjonell

Tape - (Tier 3) - Operasjonell

Holylabs - Operasjonell

Isilon Storage Holyoke (Tier 1) - Operasjonell

Holystore01 (Tier 0) - Operasjonell

HolyLFS04 (Tier 0) - Operasjonell

HolyLFS05 (Tier 0) - Operasjonell

HolyLFS06 (Tier 0) - Operasjonell

Holyoke Tier 2 NFS - Operasjonell

Holyoke Specialty Storage - Operasjonell

holECS - Operasjonell

Isilon Storage Boston (Tier 1) - Operasjonell

BosLFS02 (Tier 0) - Større avbrudd

Boston Tier 2 NFS - Operasjonell

CEPH Storage Boston (Tier 2) - Operasjonell

Boston Specialty Storage - Operasjonell

bosECS - Operasjonell

Samba Cluster - Operasjonell

Globus Data Transfer - Operasjonell

Kunngjøringshistorikk

Se nåværende status

okt. 2024

holyscratch01 OST2b issues
LøstNedsatt ytelse4 minutter
  • LøstUTC
    This incident has been resolved.
  • UndersøkerUTC

    OST2b (one of the bricks that make up holyscratch01) has wedged again. We are in the process of troubleshooting.

holyscratch01 OST2b issues
LøstNedsatt ytelse5 minutter
  • LøstUTC
    This incident has been resolved.
  • UndersøkerUTC

    OST2b on holyscratch01 (one of the bricks that makes up holyscratch01) is hung up. We are failing it over the rectify scratch performance issues.

holyscratch01 Instability
LøstDelvis avbrudd2 timer 8 minutter
  • LøstUTC
    The instability has been resolved.
  • IdentifisertUTC
    We are continuing to work on a fix for this incident.
  • LøstUTC
    This incident has been resolved.
  • UndersøkerUTC
    We are currently investigating this incident.
OKT10
holyscratch01 reboot
LøstVedlikehold9 minutter
  • LøstUTC
    This incident has been resolved.
  • UndersøkerUTC

    We are rebooting holyscratch01 to clear a stuck state.

holyscratch01 degraded
Løstett minutt
  • LøstUTC
    OST2b failed over
  • OvervåkerUTC
    holyscratch01 - OST2b failing over

sep. 2024

Virtual Machine hypervisor down - Affects FASSE login/OOD
LøstStørre avbrudd18 timer 19 minutter
  • LøstUTC
    Resolving. The hypervisor and all but one VM, which has separate issue, are operational.
  • OppdateringUTC

    FASSE Open OnDemand and FASSE login services should be operational now.

  • OvervåkerUTC

    FASSE OOD is back up

    FASSE login nodes are still down

  • IdentifisertUTC

    One of the hypervisors managing virtual machines is down. We are working to bring it back up. This does affect FASSE login and FASSE OOD nodes as well as may degrade OpenAuth (two-factor).

    Affected hosts are:
    HOST -- STATUS

    dataverse-backup UNKNOWN

    demo2-l3-fs UNKNOWN

    enos-vote-l3-fs UNKNOWN

    fasselogin01 UNKNOWN

    fasselogin02 UNKNOWN

    frontier-squid02 UNKNOWN

    frontier-squid03 UNKNOWN

    frontier-squid04 UNKNOWN

    goel-adm24-l3-fs UNKNOWN

    goel-blind-l3-fs UNKNOWN

    goel-l3-fs UNKNOWN

    h-dev-fasseooda-01 UNKNOWN

    h-dev-fasseooda-lb01 UNKNOWN

    h-dev-fasseoodb-lb11 UNKNOWN

    h-fasseooda-01 UNKNOWN

    h-fasseooda-lb02 UNKNOWN

    h-fasseoodb-lb11 UNKNOWN

    h-fasseoodb-lb12 UNKNOWN

    h-fasseoodc-lb21 UNKNOWN

    h-fasseoodc-lb22 UNKNOWN

    h-qa-fasseooda-01 UNKNOWN

    h-qa-fasseooda-lb02 UNKNOWN

    holy-es-master01 UNKNOWN

    holy-es-master02 UNKNOWN

    holy-es-master03 UNKNOWN

    holynagios UNKNOWN

    kreindlerl3-fs UNKNOWN

    martin-su-l3-fs UNKNOWN

    mcconnell-l3-fs UNKNOWN

    openauth02 jtriley UNKNOWN

    shleifer-dsl3-fs UNKNOWN

    stock-solar-l3-fs UNKNOWN

    stopsack-l3-fs UNKNOWN

    xcat UNKNOWN

holyscratch01
LøstNedsatt ytelse6 minutter
  • LøstUTC
    The failover is complete.
  • IdentifisertUTC
    The object storage target OST2b on holyscratch01 is again causing degraded performance. We are failing it over to the backup. We're aware that this issue is a concern, but please know that an entire new scratch filesystem is forthcoming. Thanks for your understanding.
holyscratch01 issues overnight
Løst
  • holyscratch01 was at times degraded over the weekend. The OST causing the issues was restarted and the filesystem should be back to normal.
    UTC
holyscratch01 degraded performance
Løst
  • holyscratch01 was found to be in a degraded state around 9:15AM and returned to operation at 9:25AM
    UTC
holyscratch01 - OST2b stuck
Løst4 timer 20 minutter
  • OppdateringUTC
    This incident has been resolved.
  • LøstUTC
    holyscratch01 and affected nodes are reopened
  • IdentifisertUTC
    holyscratch01 is seeing degraded performance and many nodes are closed off.

aug. 2024

holylfs04 down
LøstDelvis avbrudd23 minutter
  • LøstUTC
    holylfs04 is back up
  • UndersøkerUTC
    Holylfs04 needs to be rebooted to address performance issues.
Cannon cluster degraded
LøstNedsatt ytelse4 timer 57 minutter
  • LøstUTC
    The power issue has been resolved. All nodes that were drained are now being re-opened.
  • UndersøkerUTC

    Due to temporary power availability issues in MGHPCC, half the nodes in 8A have been set to drain. This affects all partitions. Jobs will take longer to schedule but will not be terminated.

    We will reopen these nodes once the power issue has been resolved at the datacenter. No ETA at this time

boslfs02 degraded
LøstNedsatt ytelse8 minutter
  • LøstUTC
    boslfs02 is back up
  • UndersøkerUTC
    boslfs02 needs to be rebalanced. Access may be inconsistent
AUG24
Starfish upgrade
FullførtVedlikehold84 timer
  • Fullførtaugust 27, 2024 kl. 12:00UTC

    Starfish is back up

  • Oppdateringaugust 26, 2024 kl. 14:35UTC

    Starfish maintenance is still ongoing, no ETA at this time.

  • Pågåraugust 24, 2024 kl. 00:00UTC
    Maintenance is now in progress
  • Planlagtaugust 24, 2024 kl. 00:00UTC

    The Starfish Zones Dashboard will be undergoing a few upgrades and maintenance this weekend from Friday, August 23rd at 8AM until Monday, August 26th at 8AM. The dashboard will not be accessible during this time. Further details will be provided, if needed. Please email rchelp@rc.fas.harvard.edu if you have any questions or concerns.

Rebalancing boslfs02
LøstNedsatt ytelse11 minutter
  • LøstUTC
    This incident has been resolved.
  • OvervåkerUTC

    We are working on rebalancing boslfs02, there may be a short period of degraded performance

Forrige

aug. 2024 til okt. 2024

Neste

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