2019.6.12
A network failure happened as follows and it had been recovered.
1. summary
Network failure between campus network and login0 occurred.
2. period
June 11 2019 around 14:10 - 17:00
3. detail
From around June 11 2019 14:10, a trouble that login node(login0) was not accessible from the internet happened.
It had been recovered by restarting login0 at 18:49.
2018.12.25
A storage failure occurred and now temporarily recovered.
１．Summary
2018.8.1
Failure occurred as follows and restoration work in progress.
1. Outline of Failure
Failure occurred in 72 computation nodes starting with r8 due to failure of one of the cooling racks around 2018/08/01 12:45.
2. Cause
investigating
3. Future measures
To be determined
Jobs that may be affected by failures are as follows.
2018.6.25
An fault occurred and now temporarily recovered.
Impossible to access a part of /gs/hs0. It has temporarily recovered, but there is the possibility of performance decline.
From 13:39 to 13:54, on Jun. 25
2018.6.18
An fault occurred and now temporarily recovered.
1. Summary
Impossible to access a part of /gs/hs0. It has temporarily recovered, but there is the possibility of performance decline.
2. Period
From 21:42 to 21:57, on Jun. 15
3. Details
2018.6.4
An fault occurred and now temporarily recovered.
1. Summary
Impossible to access a part of /gs/hs0. It has temporarily recovered, but there is the possibility of performance decline.
2. Period
From 01:52 to 02:06, on Jun. 4
3. Details
2018.5.25
An fault occurred and now temporarily recovered.
1. Summary
Impossible to access a part of /gs/hs0. It has temporarily recovered, but there is the possibility of performance decline.
2. Period
From 19:18 to 19:36, on May 24
3. Details
2018.2.27
Sorry for delaying to notice. As described below, the failure occurred and recovered.
1. Outline of failure
2/18 15:50 144 nodes under Rack 1,2 stopped due to power supply instability in Tokyo and Kanagawa.
2. Cause
Power supply instability from power company.
Jobs that may be affected by failures are as follows.
2018.2.27
Sorry for delaying to notice.
1. Outline of failure
Water leakage occurred inside the cooling rack #1 on Jan. 26.
That caused a failure in 19 nodes, and it affected all the 72 jobs in the rack.
Although it does not break down only by water leakage, it hits cooling fan, and it bounced, so compute node also affected.
Disassembly and visual inspection of cooling rack#1 have identified water leakage points, and we have completed the treatment against water leakage.
2018.2.13
The following event has occur. We have done the corrective action.