受到影响
严重故障 从 7:33 PM 至 3:01 PM, 运行正常 从 3:01 PM 至 6:48 PM
严重故障 从 7:33 PM 至 3:01 PM, 运行正常 从 3:01 PM 至 6:48 PM
严重故障 从 7:33 PM 至 3:01 PM, 运行正常 从 3:01 PM 至 6:48 PM
- 已解决已解决Hardware has been repaired and holyoke login nodes are back online. Thanks for your patience.
- 持续监控中持续监控中
Holylogin chassis repair during maintenance was unsuccessful and replacement parts have been ordered.
holyoke login nodes (holylogin05-08) are down for hardware repair
Only Boston login nodes available (ie, boslogin[05-08])
If you have holylogin hard-coded in your scripts, please update to login.rc.fas.harvard.edu or boslogin.rc.fas.harvard.edu for the time being, which will redirect you to an available login node.
As always, the best method for obtaining a login node is using
login.rc.fas.harvard.eduwhich will pick a node for you.If you require a login node in a specific data center, use
boslogin.rc.fas.harvard.edu(Boston) or (once they are back in service)holylogin.rc.fas.harvard.edu(Holyoke).See also: Command line access with Terminal (login nodes) – FASRC DOCS
- 已解决已解决
This incident was posted by mistake.
holylogin01-04 were replaced by holylogin05-08 some time back.
As always, the best method for obtaining a login node is usinglogin.rc.fas.harvard.eduwhich will pick a node for you.Or if you require a login node in a specific data center, use
boslogin.rc.fas.harvard.edu(Boston) orholylogin.rc.fas.harvard.edu(Holyoke).See also: Command line access with Terminal (login nodes) – FASRC DOCS
- 调查中调查中
Holylogin chassis repair during maintenance was unsuccessful and replacement parts have been ordered.
Audience:
All cluster users
Impact:
All holylogin** servers will be down till further notice
Only Boston login nodes available (ie, boslogin[05-08])
If you have holylogin hard-coded in your scripts, please update to login.rc.fas.harvard.edu or boslogin.rc.fas.harvard.edu for the time being, which will redirect you to an available login node.
Updates to follow as we have them.

