Information

2023/5/8-9
On May 8, the storage space usage of the Toyosu virtualization platform at Toyosu reached 100% and some servers were shut down.
As a result, various services were unavailable.

We have confirmed that most of the services have been restored as of now (May 9, 10:00),

but if you find any services that are experiencing problems, please contact the Information System Section.

[List of failed services]（5/9 10:15 update）

S*gsot
Linux server（yli）
Wireless LAN(SRAS/eduroam)
SIT STATION
AMI
Certificate issuing machine（PAPYRUS MATE）
Gakunin
Wing-net（at Toyosu）
DHCP（partially）
DNS（partially）

Office support system（Office portal）
Office system menue
Debt system（ including source system）
Print server（for office）
Application for card issue

Apr. 10-11, 2023
There was an intermittent problem with the wireless LAN at the Omiya Campus.
Countermeasures to load access points are being taken sequentially.

There is a problem with MoSICA for iOS in which the correct one-time passwords are not output

(This seems to occur on devices with a specific version of iOS or later).

This problem will be resolved by updating MoSICA.

If the one-time password still does not pass, please refer to the attached file and update MoSICA.

※If you are currently using iOS 11 or earlier, you may not be able to use the service after updating. Please be aware of this.

01/25/2023 16:30~
Microsoft365 is experiencing disability.

01/25/2023 23:31
The system has been restored.

We experienced an Azure outage during the winter break.
The system has now been restored.
We apologize for any inconvenience this may have caused to ScombZ.

Date of Occurrence:

Approximately 12/30/2022 to 10:30am on 01/01/2023
Scope of impact: Uploading and downloading of attached files such as educational materials and assignments in ScombZ LMS

Cause:

File access errors due to storage mount failure caused by Azure failure or maintenance. The error was caused by a storage mount failure due to an Azure failure or maintenance. Normally, the storage is automatically mounted after a failure, but for some reason it was not remounted. However, for some reason, it was not remounted.

Recovery method:

Remount on the CITS side and restart the service.
Translated with www.DeepL.com/Translator (free version)