FAS Research Computing - Histórico de avisos

Todos os sistemas operacionais

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

SLURM Scheduler - Cannon - Operacional

Cannon Compute Cluster (Holyoke) - Operacional

Boston Compute Nodes - Operacional

GPU nodes (Holyoke) - Operacional

seas_compute - Operacional

Operacional

SLURM Scheduler - FASSE - Operacional

FASSE Compute Cluster (Holyoke) - Operacional

Operacional

Kempner Cluster CPU - Operacional

Kempner Cluster GPU - Operacional

Operacional

FASSE login nodes - Operacional

Operacional

Cannon Open OnDemand - Operacional

FASSE Open OnDemand - Operacional

Operacional

Netscratch (Global Scratch) - Operacional

Home Directory Storage - Boston - Operacional

Tape - (Tier 3) - Operacional

Holylabs - Operacional

Isilon Storage Holyoke (Tier 1) - Operacional

Holystore01 (Tier 0) - Operacional

HolyLFS04 (Tier 0) - Operacional

HolyLFS05 (Tier 0) - Operacional

HolyLFS06 (Tier 0) - Operacional

Holyoke Tier 2 NFS (new) - Operacional

Holyoke Specialty Storage - Operacional

holECS - Operacional

Isilon Storage Boston (Tier 1) - Operacional

BosLFS02 (Tier 0) - Operacional

Boston Tier 2 NFS (new) - Operacional

CEPH Storage Boston (Tier 2) - Operacional

Boston Specialty Storage - Operacional

bosECS - Operacional

Samba Cluster - Operacional

Globus Data Transfer - Operacional

Histórico de avisos

out 2024

holyscratch01 OST2b issues
  • Resolvido
    UTC
    Resolvido
    This incident has been resolved.
  • Investigando
    UTC
    Investigando

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

holyscratch01 OST2b issues
  • Resolvido
    UTC
    Resolvido
    This incident has been resolved.
  • Investigando
    UTC
    Investigando

    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
  • Resolvido
    UTC
    Resolvido
    The instability has been resolved.
  • Identificado
    UTC
    Identificado
    We are continuing to work on a fix for this incident.
  • Resolvido
    UTC
    Resolvido
    This incident has been resolved.
  • Investigando
    UTC
    Investigando
    We are currently investigating this incident.
holyscratch01 reboot
  • Resolvido
    UTC
    Resolvido
    This incident has been resolved.
  • Investigando
    UTC
    Investigando

    We are rebooting holyscratch01 to clear a stuck state.

holyscratch01 degraded
  • Resolvido
    UTC
    Resolvido
    OST2b failed over
  • Monitoramento
    UTC
    Monitoramento
    holyscratch01 - OST2b failing over

set 2024

Virtual Machine hypervisor down - Affects FASSE login/OOD
  • Resolvido
    UTC
    Resolvido
    Resolving. The hypervisor and all but one VM, which has separate issue, are operational.
  • Atualizar
    UTC
    Atualizar

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

  • Monitoramento
    UTC
    Monitoramento

    FASSE OOD is back up

    FASSE login nodes are still down

  • Identificado
    UTC
    Identificado

    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
  • Resolvido
    UTC
    Resolvido
    The failover is complete.
  • Identificado
    UTC
    Identificado
    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
  • Resolvido
    UTC
    Resolvido
    holyscratch01 was at times degraded over the weekend. The OST causing the issues was restarted and the filesystem should be back to normal.
holyscratch01 degraded performance
  • Resolvido
    UTC
    Resolvido
    holyscratch01 was found to be in a degraded state around 9:15AM and returned to operation at 9:25AM
holyscratch01 - OST2b stuck
  • Atualizar
    UTC
    Atualizar
    This incident has been resolved.
  • Resolvido
    UTC
    Resolvido
    holyscratch01 and affected nodes are reopened
  • Identificado
    UTC
    Identificado
    holyscratch01 is seeing degraded performance and many nodes are closed off.

ago 2024

holylfs04 down
  • Resolvido
    UTC
    Resolvido
    holylfs04 is back up
  • Investigando
    UTC
    Investigando
    Holylfs04 needs to be rebooted to address performance issues.
Cannon cluster degraded
  • Resolvido
    UTC
    Resolvido
    The power issue has been resolved. All nodes that were drained are now being re-opened.
  • Investigando
    UTC
    Investigando

    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
  • Resolvido
    UTC
    Resolvido
    boslfs02 is back up
  • Investigando
    UTC
    Investigando
    boslfs02 needs to be rebalanced. Access may be inconsistent
Starfish upgrade
  • Concluído
    agosto 27, 2024 em 12:00UTC
    Concluído
    agosto 27, 2024 em 12:00UTC

    Starfish is back up

  • Atualizar
    agosto 26, 2024 em 14:35UTC
    Atualizar
    agosto 26, 2024 em 14:35UTC

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

  • Em curso
    agosto 24, 2024 em 00:00UTC
    Em curso
    agosto 24, 2024 em 00:00UTC
    Maintenance is now in progress
  • Ainda não iniciou
    agosto 24, 2024 em 00:00UTC
    Ainda não iniciou
    agosto 24, 2024 em 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
  • Resolvido
    UTC
    Resolvido
    This incident has been resolved.
  • Monitoramento
    UTC
    Monitoramento

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

ago 2024 para out 2024

Próximo

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