История на известията

Работи

Сериозно прекъсване

Работи

Вижте текущия статус

окт 2026

As per email communications with affected groups, the cutover from boslfs02 to /n/lab_storage is ongoing from October 27-October 29. All storage folders are set to read-only and all running jobs have been stopped.
Once the cutover process is complete, affected users will receive an email confirming their new storage is ready for use.
октомври 28, 2026 в 15:10UTC

Решеноктомври 26, 2026 в 14:33UTC
boslogin07 has been rebooted and is responsive. This incident has been resolved.
Разследва сеоктомври 26, 2026 в 14:15UTC
boslogin07 is experiencing long delays on login we will reboot the system at 10:30

Решеноктомври 27, 2026 в 20:10UTC
This incident has been resolved.
Наблюдавамеоктомври 26, 2026 в 14:38UTC
holystore01 is back up.
Draining nodes are being addressed and will be put back into service at the earliest.
Разследва сеоктомври 26, 2026 в 14:05UTC
holystore01 is We are currently experiencing performance issues that have impacted some compute nodes, causing them to drain, investigating this incident.

ОКТ24

Globus scheduled maintenance

ЗавършенПоддръжка1 час

Завършеноктомври 24, 2026 в 15:30UTC
Maintenance has completed successfully
В ходоктомври 24, 2026 в 14:30UTC
Maintenance is now in progress
Планиранаоктомври 19, 2026 в 15:30UTC
Globus services will be unavailable for a period between 9:30am and 10:30am U.S. Central time on Saturday, October 24, 2026 due to planned maintenance (https://www.globus.org/blog/2026-10-24-maintenance) that includes database upgrades.
Please refer to the posted link for additional information on how services and in-progress work will be impacted during this window.

Решеноктомври 23, 2026 в 18:37UTC
This incident has been resolved.
Разследва сеоктомври 23, 2026 в 13:22UTC
holylfs06 is in a very degraded or stuck state.
Expect degraded to no access until the system is back up.

сеп 2026

Решеноктомври 05, 2026 в 20:07UTC
The vendor has replaced the necessary hardware components, and FASRC engineers have installed updates and confirmed working status. No data was affected.
All h-nfs11-p shares should be accessible again once more.
If you notice any irregularities, please reach out at rchelp@rc.fas.harvard.edu
Актуализацияоктомври 02, 2026 в 18:40UTC
The vendor has dispatched parts. The vendor has indicated that this may not get fixed until Monday, but the storage team is pressing them to accelerate that timeline. We will update here when we know more.
Thanks for your understanding.
Актуализацияоктомври 01, 2026 в 15:03UTC
After lengthy troubleshooting, h-nfs11-p is still down. The vendor is scheduling a datacenter visit for on-site repairs. We will update as we know more.
Идентифицирансептември 30, 2026 в 19:15UTC
Our engineers are diagnosing the root cause of the failure and are working with the vendor to troubleshoot further
We are continuing to work on a fix for this incident.
Разследва сесептември 29, 2026 в 19:33UTC
h-nfs11-p is currently down. The following shares are inaccessible on FASSE
- ncf_cnl01
- ncf_cnl02
- ncf_cnl03
- ncf_cnl04
- ncf_gspdata
- ncf_mri_l3
- cnl05
- cnl06
- eldaief
- ncf_apps
- jcamprodon_lab_l3
We are investigating this incident.

Решенсептември 28, 2026 в 15:29UTC
Openauth/radius is now operational. This update was created by an automated monitoring service.
Разследва сесептември 28, 2026 в 14:59UTC
Authentication issues with openauth/radius. This incident was created by an automated monitoring service.

Решенсептември 28, 2026 в 7:03UTC
FASRC VPN (Boston) is back up. This incident was automatically resolved by Instatus monitoring.
Разследва сесептември 28, 2026 в 6:44UTC
FASRC VPN (Boston) is down at the moment. This incident was automatically created by Instatus monitoring.

Решенсептември 28, 2026 в 6:36UTC
FASRC VPN (Cambridge) is back up. This incident was automatically resolved by Instatus monitoring.
Разследва сесептември 28, 2026 в 6:27UTC
FASRC VPN (Cambridge) is down at the moment. This incident was automatically created by Instatus monitoring.

Решенсептември 28, 2026 в 6:16UTC
FASRC VPN (Cambridge) is back up. This incident was automatically resolved by Instatus monitoring.
Разследва сесептември 28, 2026 в 6:06UTC
FASRC VPN (Cambridge) is down at the moment. This incident was automatically created by Instatus monitoring.

авг 2026

Решенавгуст 25, 2026 в 16:38UTC
docs.rc.fas.harvard.edu is back up. This incident was resolved automatically.
Разследва сеавгуст 25, 2026 в 15:58UTC
docs.rc.fas.harvard.edu is down at the moment. This incident was created automatically.

Решенавгуст 25, 2026 в 16:37UTC
www.rc.fas.harvard.edu is back up. This incident was resolved automatically.
Разследва сеавгуст 25, 2026 в 15:57UTC
www.rc.fas.harvard.edu is down at the moment. This incident was created automatically.

Решенавгуст 25, 2026 в 17:58UTC
This incident has been resolved. All hosts are back up and online. Thanks for your patience.
Please note that the rolling OS updates are still in progress, but will not affect OOD access.
Идентифициранавгуст 25, 2026 в 15:28UTC
This likely affects other virtual machines including, but possibly not limited to,
cannon ood
cbscentral*
ssbccentral*
mczapps
mczbase
msprl
smms
epslic1
hptc-cal
mailman
minecat
r10k-builds02
ncfservice*
Разследва сеавгуст 25, 2026 в 15:14UTC
We are currently investigating this issue. Details to follow.

АВГ24

Rolling OS Upgrades August 24th - 27th 2026

ЗавършенПоддръжка79 часа 6 минути

Завършенавгуст 27, 2026 в 20:06UTC
OS upgrade work is mostly completed.
There are a few remaining nodes in the cluster that did not successfully receive the upgrade.
If you see nodes that are 'DOWN' for the following reasons, they are all nodes that need manual intervention for OS upgrade. FASRC staff are aware of them and will upgrade these nodes over the next week.
- "wrong kernel"
- "Not responding"
- "unexpected reboot"
- "gres/gpu count lower than configured"
- "/n/sw not mounted"
We appreciate your continued patience.
Актуализацияавгуст 26, 2026 в 20:01UTC
Today's work is complete. The final round, Cannon Part 3, takes place tomorrow.

August 26th: Cannon Part 2
arguelles_delgado
conroy
davies
doshi-velez
dsouza
edwards
geophysics
giribet
gpu_test
hernquist
huce_cascadeimasc
janson
kempner_h200
kempner_rtx
murphy
ni_lab
olveczky
ortegahernandez
pehlevan
seas_compute
shakhnovich
shared
unrestricted
xlin
yin
zon
Актуализацияавгуст 25, 2026 в 19:37UTC
Today's work is complete for Cannon Part 1 and will resume tomorrow for Cannon Part 2
August 25th: Cannon Part 1
holylogin
arguelles_delgado
blackhole
davies_gpu
davies
desai
eddy
holy-cow
holy-smokes
huce_bigmem
huce_cascade
huttenhower
jacobsen2
janson_bigmem
janson_cascade
janson
ke
lukin
nguyen
olveczky_gpu
remoteviz
seas_compute
shared
sompolinsky_gpu
tambe
vishwanath
whipple
xlin
xlin_ice
zhuang_gpu
zhuang
Актуализацияавгуст 24, 2026 в 19:07UTC
Today's portion of the upgrades are completed. Tomorrow's list (Cannon part 1) can be found in this maintenance event.
August 24th:
FASSE
boslogin
private login nodes
В ходавгуст 24, 2026 в 13:00UTC
Maintenance is now in progress
Планиранаавгуст 03, 2026 в 19:35UTC
FASRC will be doing OS upgrades to the latest version of Rocky 8.10 from August 24-27th. These rolling upgrades will improve cluster security and install the latest Cuda 13.2 driver.
Upgrades will happen in stages with each stage occurring between 8a-5p each day. During that period the nodes being upgraded will be unavailable. No jobs will be canceled but jobs will stay pending if all nodes in the partition are down.
Note that during this week the cluster will be in a partially upgraded state, thus jobs that span multiple nodes may become unstable due to mismatching libraries. Users concerned about this should wait until August 28th to restart runs.
Users should plan their work accordingly.
The upgrade schedule with impacted partitions is as follows:
August 24th:
FASSE
boslogin
private login nodes
August 25th: Cannon Part 1
holylogin
arguelles_delgado
blackhole
davies_gpu
davies
desai
eddy
holy-cow
holy-smokes
huce_bigmem
huce_cascade
huttenhower
jacobsen2
janson_bigmem
janson_cascade
janson
ke
lukin
nguyen
olveczky_gpu
remoteviz
seas_compute
shared
sompolinsky_gpu
tambe
vishwanath
whipple
xlin
xlin_ice
zhuang_gpu
zhuang
August 26th: Cannon Part 2
arguelles_delgado
conroy
davies
doshi-velez
dsouza
edwards
geophysics
giribet
gpu_test
hernquist
huce_cascadeimasc
janson
kempner_h200
kempner_rtx
murphy
ni_lab
olveczky
ortegahernandez
pehlevan
seas_compute
shakhnovich
shared
unrestricted
xlin
yin
zon
August 27th: Cannon Part 3
arguelles_delgado_gpu_a100
arguelles_delgado_gpu_mixed
arguelles_delgado_h100
bigmem_intermediate
bigmem
blackhole_gpu
dvorkin
eddy
enos
gershman
gpu
gpu_h200
hejazi
hernquist_ice
hoekstra
hsph_gpu
hsph
huce_ice
iaifi_gpu
intermediate
itc_cluster
itc_gpu
janson_sapphire
joonholee
jshapiro
kempner_h100
kempner_h200
kempner
kempner_interactive
kovac
kozinsky_gpu
kozinsky
murphy_ice
mweber_compute
mweber_gpu
olveczky_sapphire
ortegahernandez_ice
rivas
sapphire
seas_compute
seas_gpu
seas_gpu_perf
siag_gpu
siag_combo
siag
sur
test
yao_alphatns
yao_gpu
yao
zhuang

Актуализацияавгуст 18, 2026 в 19:09UTC
A number of jobs appear to have terminated during the upgrade for some reason. Those jobs will re-queue or, if not, will need to be re-submitted,
We apologize for the inconvenience.
Решенавгуст 18, 2026 в 18:57UTC
The update has been applied and the scheduler is returned to service. Jobs are unpaused.
Разследва сеавгуст 18, 2026 в 15:15UTC
We have been manually dealing with a Slurm memory leak bug behind the scenes and now have an official fix in the form of a Slurm upgrade (26.05.3). It is necessary to get this update in place as soon as possible.
At 2pm today we will pause the cluster. Jobs will be paused, not terminated, and the scheduler will be unavailable for querying or submitting new jobs until the update is completed. Once complete, jobs will resume.

Technical information about the bug:
https://support.schedmd.com/show_bug.cgi?id=25685

авг 2026 до окт 2026

FAS Research Computing - История на известията

История на известията

окт 2026

сеп 2026

авг 2026

The upgrade schedule with impacted partitions is as follows: