FAS Research Computing - Meddelelseshistorik

BosLFS02 (Tier 0) Oplever større udfald

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

SLURM Scheduler - Cannon - Operationel

Cannon Compute Cluster (Holyoke) - Operationel

Boston Compute Nodes - Operationel

GPU nodes (Holyoke) - Operationel

seas_compute - Operationel

Operationel

SLURM Scheduler - FASSE - Operationel

FASSE Compute Cluster (Holyoke) - Operationel

Operationel

Kempner Cluster CPU - Operationel

Kempner Cluster GPU - Operationel

Operationel

FASSE login nodes - Operationel

Operationel

Cannon Open OnDemand - Operationel

FASSE Open OnDemand - Operationel

Stort udfald

Netscratch (Global Scratch) - Operationel

Home Directory Storage - Boston - Operationel

Tape - (Tier 3) - Operationel

Holylabs - Operationel

Isilon Storage Holyoke (Tier 1) - Operationel

Holystore01 (Tier 0) - Operationel

HolyLFS04 (Tier 0) - Operationel

HolyLFS05 (Tier 0) - Operationel

HolyLFS06 (Tier 0) - Operationel

Holyoke Tier 2 NFS - Operationel

Holyoke Specialty Storage - Operationel

holECS - Operationel

Isilon Storage Boston (Tier 1) - Operationel

BosLFS02 (Tier 0) - Stort udfald

Boston Tier 2 NFS - Operationel

CEPH Storage Boston (Tier 2) - Operationel

Boston Specialty Storage - Operationel

bosECS - Operationel

Samba Cluster - Operationel

Globus Data Transfer - Operationel

Meddelelseshistorik

Se nuværende status

okt. 2024

holyscratch01 OST2b issues
LøstBegrænset drift4 minutter
  • LøstUTC
    This incident has been resolved.
  • UndersøgerUTC

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

holyscratch01 OST2b issues
LøstBegrænset drift5 minutter
  • LøstUTC
    This incident has been resolved.
  • UndersøgerUTC

    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østDelvist udfald2 timer 8 minutter
  • LøstUTC
    The instability has been resolved.
  • IdentificeretUTC
    We are continuing to work on a fix for this incident.
  • LøstUTC
    This incident has been resolved.
  • UndersøgerUTC
    We are currently investigating this incident.
OKT10
holyscratch01 reboot
LøstVedligeholdelse9 minutter
  • LøstUTC
    This incident has been resolved.
  • UndersøgerUTC

    We are rebooting holyscratch01 to clear a stuck state.

holyscratch01 degraded
Løst1 minut
  • LøstUTC
    OST2b failed over
  • OvervågerUTC
    holyscratch01 - OST2b failing over

sep. 2024

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

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

  • OvervågerUTC

    FASSE OOD is back up

    FASSE login nodes are still down

  • IdentificeretUTC

    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østBegrænset drift6 minutter
  • LøstUTC
    The failover is complete.
  • IdentificeretUTC
    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
  • OpdateringUTC
    This incident has been resolved.
  • LøstUTC
    holyscratch01 and affected nodes are reopened
  • IdentificeretUTC
    holyscratch01 is seeing degraded performance and many nodes are closed off.

aug. 2024

holylfs04 down
LøstDelvist udfald23 minutter
  • LøstUTC
    holylfs04 is back up
  • UndersøgerUTC
    Holylfs04 needs to be rebooted to address performance issues.
Cannon cluster degraded
LøstBegrænset drift4 timer 57 minutter
  • LøstUTC
    The power issue has been resolved. All nodes that were drained are now being re-opened.
  • UndersøgerUTC

    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østBegrænset drift8 minutter
  • LøstUTC
    boslfs02 is back up
  • UndersøgerUTC
    boslfs02 needs to be rebalanced. Access may be inconsistent
AUG24
Starfish upgrade
GennemførtVedligeholdelse84 timer
  • Gennemførtaugust 27, 2024 kl. 12:00UTC

    Starfish is back up

  • Opdateringaugust 26, 2024 kl. 14:35UTC

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

  • Igangværendeaugust 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østBegrænset drift11 minutter
  • LøstUTC
    This incident has been resolved.
  • OvervågerUTC

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

Forrige

aug. 2024 til okt. 2024

Næste

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