Dear DICC Users, We are currently experiencing another major service disruption due to an unknown internal service problem. We are currently in the process of investigating so we will be having an unscheduled emergency maintenance. We will be updating again once the service is stabilized and accessible again. We are Read more…
Dear DICC Users, We were facing HPC service disruption due to major failure on one of the internal core services around 6.45pm. The HPC service has recovered around 9.15pm and is now accessible. All running jobs failed due to broken connection with the Lustre Storage system. Users will need to resubmit Read more…
Dear DICC users, We are experiencing unexpected service disruption since 3.43am on 22 July 2021. We are working on this issue to restore the service as soon as possible. We apologize for the inconvenience caused. Thank you. UPDATE: The HPC service has resumed around 4.00pm today. Please do take notes Read more…
Dear DICC Users, We are experiencing unexpected disruption to our service since 10 Jun 2021, 2.50pm. We are working on the matter to resolve the issue. We apologize for the inconvenience caused. Update: The service has recovered around 8.45 pm on 10 Jun 2021.
Dear DICC Users, There was a major power outage in our HPC data center since 19 May 2021, around 10am. The power outage is currently causing all DICC servers to power off and all DICC services are affected. All the DICC services will not be accessible during the power outage. We will be updating again once the power issue Read more…
Dear DICC users, We are experiencing a major power outage in our HPC data center since 4th April, around 7.20 am. The power outage has caused most of the servers in DICC to power off and affected all DICC services. We have recovered most of the operation of our services around 9.45 am, 5th April. For Read more…
Dear all HPC Users, There was an incident where one of the CPU compute nodes in the HPC pool, cpu06 crashed due to high CPU load caused by some processes stuck in the machine indefinitely. This incident has caused all the jobs running in cpu06 to fail as the worker daemon was not Read more…