Infrastructure News Type: Outage Partial

Affected Infrastructure: anvil.purdue.access-ci.org

Start Date: May 13, 2024, 12:00 p.m.

End Date: May 14, 2024, 12:00 p.m.

The Anvil system will have reduced capacity Monday, May 13 from 8:00am - Tuesday, May 14 at 8:00am EDT for scheduled maintenance. Some compute nodes will be powered off during the maintenance for some power work. How does this maintenance impact you? - This is a standard partial maintenance for Anvil system - OS and Slurm will still be functioning with reduced capacity - User jobs might experience longer waiting time - No user impact is expected once Anvil is returned to service Anvil will return to full production by Tuesday, May 14, 2024 at 8:00am EDT. Please submit a ticket through ACCESS Help Desk at https://support.access-ci.org/open-a-ticket if you have any questions.

Posted: March 20, 2026

Infrastructure News Type: Outage Partial

Affected Infrastructure: bridges2-ocean.psc.access-ci.org

Start Date: May 6, 2024, 2:00 p.m.

End Date: May 6, 2024, 5:00 p.m.

Bridges-2 VMs will be unavailable on Monday, May 6 from 9AM-Noon Eastern Time due to scheduled maintenance.

Posted: March 20, 2026

Infrastructure News Type: Outage Partial

Affected Infrastructure: xdmod.access-ci.org

Start Date: April 29, 2024, 3:00 p.m.

End Date: May 1, 2024, 10:00 p.m.

UPDATE: 5/2/24 The service has been restored and should be fully functional now. There will be a partial outage for ACCESS XDMoD today from approximately 10:00 EDT on 4/29 until 17:00 EDT on 5/01. This will only impact viewing job-level performance data of the Single Job Viewer. Other features of this service will still be fully functional during this time.

Posted: March 20, 2026

Infrastructure News Type: Reconfiguration

Affected Infrastructure: aces.tamu.access-ci.org

Start Date: April 22, 2024, 2:00 p.m.

End Date: April 26, 2024, 11:00 p.m.

During April 22-26, 60 PVCs and 30 H100s will be unavailable while four racks are migrated from PCIe Gen4 fabric hardware to PCIe Gen5 fabric hardware.

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: delta-cpu.ncsa.access-ci.org, delta-gpu.ncsa.access-ci.org

Start Date: April 21, 2024, 6:00 p.m.

End Date: April 21, 2024, 11:00 p.m.

The Delta compute and login nodes require an emergency reboot due to a network instability. Status updates will be provided. -The Delta Project

Posted: March 20, 2026

Infrastructure News Type: Degraded

Affected Infrastructure: delta-storage.ncsa.access-ci.org

Start Date: April 20, 2024, 5:01 p.m.

End Date: April 21, 2024, 2:00 p.m.

We believe the issue with the /scratch file system has been addressed, and will continue to monitor the function and performance of the /scratch file system. We apologize for the inconvenience and recommend checking for failed jobs.

Posted: March 20, 2026

Infrastructure News Type: Reconfiguration

Affected Infrastructure: ookami.sbu.access-ci.org

Start Date: April 15, 2024, 5:00 a.m.

End Date: May 31, 2024, 11:00 p.m.

The Ookami team is pleased to announce the addition of two NVIDIA Grace superchips (https://www.nvidia.com/en-us/data-center/grace-cpu-superchip/) to Ookami (CPU only). These new nodes with 144 cores each are now available for your testing and experimental projects. Read more (https://www.stonybrook.edu/commcms/ookami/support/faq/NVIDIA%20Grace%20CPUs.php)

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: bridges2-em.psc.access-ci.org, bridges2-gpu.psc.access-ci.org, bridges2-rm.psc.access-ci.org

Start Date: April 12, 2024, 2:02 p.m.

End Date: April 12, 2024, 6:02 p.m.

Due to a cooling issue in the machine room, Bridges-2 production nodes have been temporarily powered off. We are working on the issue and hope to return the system to full service soon. Please send a ticket to help@psc.edu (mailto:help@psc.edu) if you have any specific concerns.

Posted: March 20, 2026

Infrastructure News Type: Outage Partial

Affected Infrastructure: delta-cpu.ncsa.access-ci.org, delta-gpu.ncsa.access-ci.org

Start Date: March 29, 2024, 10:00 p.m.

End Date: April 1, 2024, 10:00 p.m.

Starting on March 29th the Delta system performed a software update to address a OS security issue. All Delta login, compute and user service nodes have been updated. Testing did not indicate any regression issues. Additionally, some parameters for the Slingshot Cassini network interface cards were tuned to improve performance or stability on April 9th - 10th. In particular, updates to the following packages are highlighted. < nvidia-driver-535.129.03-1.el8.x86_64 > nvidia-driver-535.161.08-1.el8.x86_64 < apptainer-1.2.4-1.el8.x86_64 > apptainer-1.3.0-1.el8.x86_64 < amdgpu-lib-5.7.50700-1652687.el8.x86_64 > amdgpu-lib-6.0.60000-1697589.el8.x86_64 All changes < amdgpu-5.7.50700-1652687.el8.x86_64 < amdgpu-core-5.7.50700-1652687.el8.noarch < amdgpu-dkms-6.2.4.50700-1652687.el8.noarch < amdgpu-dkms-firmware-6.2.4.50700-1652687.el8.noarch < amdgpu-lib-5.7.50700-1652687.el8.x86_64 --- > amdgpu-6.0.60000-1697589.el8.x86_64 > amdgpu-core-6.0.60000-1697589.el8.noarch > amdgpu-dkms-6.3.6.60000-1697589.el8.noarch > amdgpu-dkms-firmware-6.3.6.60000-1697589.el8.noarch > amdgpu-lib-6.0.60000-1697589.el8.x86_64 < apptainer-1.2.4-1.el8.x86_64 --- > apptainer-1.3.0-1.el8.x86_64 < avahi-0.7-20.el8.x86_64 < avahi-glib-0.7-20.el8.x86_64 < avahi-libs-0.7-20.el8.x86_64 --- > avahi-0.7-20.el8_8.4.x86_64 > avahi-glib-0.7-20.el8_8.4.x86_64 > avahi-libs-0.7-20.el8_8.4.x86_64 < bind-export-libs-9.11.36-8.el8_8.2.x86_64 < bind-libs-9.11.36-8.el8_8.2.x86_64 < bind-libs-lite-9.11.36-8.el8_8.2.x86_64 < bind-license-9.11.36-8.el8_8.2.noarch < bind-utils-9.11.36-8.el8_8.2.x86_64 --- > bind-export-libs-9.11.36-8.el8_8.3.x86_64 > bind-libs-9.11.36-8.el8_8.3.x86_64 > bind-libs-lite-9.11.36-8.el8_8.3.x86_64 > bind-license-9.11.36-8.el8_8.3.noarch > bind-utils-9.11.36-8.el8_8.3.x86_64 < c-ares-1.13.0-6.el8_8.3.x86_64 --- > c-ares-1.13.0-6.el8_8.4.x86_64 < cray-cxi-driver-devel-0.9-SSHOT2.2.0_20231129202507_f60db3151cf3.x86_64 < cray-cxi-driver-dkms-0.9-SSHOT2.2.0_20231129202507_f60db3151cf3.noarch < cray-cxi-driver-udev-0.9-SSHOT2.2.0_20231129202507_f60db3151cf3.x86_64 --- > cray-cxi-driver-devel-0.9-SSHOT2.3.0_20240202182511_9ee78d621d75.x86_64 > cray-cxi-driver-dkms-0.9-SSHOT2.3.0_20240202182511_9ee78d621d75.noarch > cray-cxi-driver-udev-0.9-SSHOT2.3.0_20240202182511_9ee78d621d75.x86_64 < cray-kfabric-devel-0.1.0-SSHOT2.2.0_20231129204205_0183e1f44610.x86_64 < cray-kfabric-dkms-0.1.0-SSHOT2.2.0_20231129204205_0183e1f44610.noarch < cray-kfabric-dracut-0.1.0-SSHOT2.2.0_20231129204205_0183e1f44610.x86_64 < cray-kfabric-udev-0.1.0-SSHOT2.2.0_20231129204205_0183e1f44610.x86_64 < cray-libcxi-0.9-SSHOT2.1.1_20231113192204_dd0106ff6e57.x86_64 < cray-libcxi-devel-0.9-SSHOT2.1.1_20231113192204_dd0106ff6e57.x86_64 < cray-libcxi-dracut-0.9-SSHOT2.1.1_20231113192204_dd0106ff6e57.x86_64 < cray-libcxi-retry-handler-0.9-SSHOT2.1.1_20231113192204_dd0106ff6e57.x86_64 < cray-libcxi-utils-0.9-SSHOT2.1.1_20231113192204_dd0106ff6e57.x86_64 --- > cray-kfabric-devel-0.1.0-SSHOT2.3.0_20240202183957_0183e1f44610.x86_64 > cray-kfabric-dkms-0.1.0-SSHOT2.3.0_20240202183957_0183e1f44610.noarch > cray-kfabric-dracut-0.1.0-SSHOT2.3.0_20240202183957_0183e1f44610.x86_64 > cray-kfabric-udev-0.1.0-SSHOT2.3.0_20240202183957_0183e1f44610.x86_64 > cray-libcxi-0.9-SSHOT2.1.2_20240202201124_2ea3fe62c2fe.x86_64 > cray-libcxi-devel-0.9-SSHOT2.1.2_20240202201124_2ea3fe62c2fe.x86_64 > cray-libcxi-dracut-0.9-SSHOT2.1.2_20240202201124_2ea3fe62c2fe.x86_64 > cray-libcxi-retry-handler-0.9-SSHOT2.1.2_20240202201124_2ea3fe62c2fe.x86_64 > cray-libcxi-utils-0.9-SSHOT2.1.2_20240202201124_2ea3fe62c2fe.x86_64 < cuda-drivers-535.129.03-1.x86_64 < cuda-drivers-fabricmanager-535-535.129.03-1.x86_64 --- > cuda-drivers-535.161.08-1.x86_64 > cuda-drivers-fabricmanager-535-535.161.08-1.x86_64 < cuda-toolkit-12-3-config-common-12.3.101-1.noarch < cuda-toolkit-12-config-common-12.3.101-1.noarch < cuda-toolkit-config-common-12.3.101-1.noarch < cups-2.2.6-51.el8_8.2.x86_64 < cups-client-2.2.6-51.el8_8.2.x86_64 < cups-filesystem-2.2.6-51.el8_8.2.noarch --- > cuda-toolkit-12-4-config-common-12.4.99-1.noarch > cuda-toolkit-12-config-common-12.4.99-1.noarch > cuda-toolkit-config-common-12.4.99-1.noarch > cups-2.2.6-51.el8_8.3.x86_64 > cups-client-2.2.6-51.el8_8.3.x86_64 > cups-filesystem-2.2.6-51.el8_8.3.noarch < cups-ipptool-2.2.6-51.el8_8.2.x86_64 < cups-libs-2.2.6-51.el8_8.2.x86_64 < curl-7.61.1-30.el8_8.6.x86_64 --- > cups-ipptool-2.2.6-51.el8_8.3.x86_64 > cups-libs-2.2.6-51.el8_8.3.x86_64 > curl-7.61.1-30.el8_8.9.x86_64 < datacenter-gpu-manager-3.3.1-1.x86_64 --- > datacenter-gpu-manager-3.3.5-1.x86_64 < dkms-3.0.12-1.el8.noarch --- > dkms-3.0.13-1.el8.noarch < emacs-26.1-10.el8_8.2.x86_64 < emacs-common-26.1-10.el8_8.2.x86_64 < emacs-filesystem-26.1-10.el8_8.2.noarch --- > emacs-26.1-10.el8_8.4.x86_64 > emacs-common-26.1-10.el8_8.4.x86_64 > emacs-filesystem-26.1-10.el8_8.4.noarch < fakeroot-1.32.1-1.el8.x86_64 < fakeroot-libs-1.32.1-1.el8.x86_64 --- > fakeroot-1.33-1.el8.x86_64 > fakeroot-libs-1.33-1.el8.x86_64 < fuse-overlayfs-1.11-1.module+el8.8.0+19993+47c8ef84.x86_64 < gds-tools-12-3-1.8.1.2-1.x86_64 --- > gds-tools-12-4-1.9.0.20-1.x86_64 < glibc-2.28-225.el8_8.6.i686 < glibc-2.28-225.el8_8.6.x86_64 < glibc-all-langpacks-2.28-225.el8_8.6.x86_64 < glibc-common-2.28-225.el8_8.6.x86_64 < glibc-devel-2.28-225.el8_8.6.x86_64 < glibc-gconv-extra-2.28-225.el8_8.6.i686 < glibc-gconv-extra-2.28-225.el8_8.6.x86_64 < glibc-headers-2.28-225.el8_8.6.x86_64 --- > glibc-2.28-225.el8_8.9.i686 > glibc-2.28-225.el8_8.9.x86_64 > glibc-all-langpacks-2.28-225.el8_8.9.x86_64 > glibc-common-2.28-225.el8_8.9.x86_64 > glibc-devel-2.28-225.el8_8.9.x86_64 > glibc-gconv-extra-2.28-225.el8_8.9.i686 > glibc-gconv-extra-2.28-225.el8_8.9.x86_64 > glibc-headers-2.28-225.el8_8.9.x86_64 < gmp-6.1.2-10.el8.x86_64 --- > gmp-6.1.2-11.el8_8.1.x86_64 < gnutls-3.6.16-6.el8_7.x86_64 --- > gnutls-3.6.16-7.el8_8.2.x86_64 < gstreamer1-plugins-bad-free-1.16.1-1.el8.x86_64 --- > gstreamer1-plugins-bad-free-1.16.1-2.el8_8.x86_64 < iproute-5.18.0-1.1.el8_8.x86_64 --- > iproute-5.18.0-1.2.el8_8.x86_64 < iwl1000-firmware-39.31.5.1-117.el8_8.1.noarch < iwl100-firmware-39.31.5.1-117.el8_8.1.noarch < iwl105-firmware-18.168.6.1-117.el8_8.1.noarch < iwl135-firmware-18.168.6.1-117.el8_8.1.noarch < iwl2000-firmware-18.168.6.1-117.el8_8.1.noarch < iwl2030-firmware-18.168.6.1-117.el8_8.1.noarch < iwl3160-firmware-25.30.13.0-117.el8_8.1.noarch < iwl5000-firmware-8.83.5.1_1-117.el8_8.1.noarch < iwl5150-firmware-8.24.2.2-117.el8_8.1.noarch < iwl6000-firmware-9.221.4.1-117.el8_8.1.noarch < iwl6000g2a-firmware-18.168.6.1-117.el8_8.1.noarch < iwl6050-firmware-41.28.5.1-117.el8_8.1.noarch < iwl7260-firmware-25.30.13.0-117.el8_8.1.noarch --- > iwl1000-firmware-39.31.5.1-118.el8_8.1.noarch > iwl100-firmware-39.31.5.1-118.el8_8.1.noarch > iwl105-firmware-18.168.6.1-118.el8_8.1.noarch > iwl135-firmware-18.168.6.1-118.el8_8.1.noarch > iwl2000-firmware-18.168.6.1-118.el8_8.1.noarch > iwl2030-firmware-18.168.6.1-118.el8_8.1.noarch > iwl3160-firmware-25.30.13.0-118.el8_8.1.noarch > iwl5000-firmware-8.83.5.1_1-118.el8_8.1.noarch > iwl5150-firmware-8.24.2.2-118.el8_8.1.noarch > iwl6000-firmware-9.221.4.1-118.el8_8.1.noarch > iwl6000g2a-firmware-18.168.6.1-118.el8_8.1.noarch > iwl6050-firmware-41.28.5.1-118.el8_8.1.noarch > iwl7260-firmware-25.30.13.0-118.el8_8.1.noarch < java-1.8.0-openjdk-1.8.0.392.b08-4.el8.x86_64 < java-1.8.0-openjdk-devel-1.8.0.392.b08-4.el8.x86_64 < java-1.8.0-openjdk-headless-1.8.0.392.b08-4.el8.x86_64 --- > java-1.8.0-openjdk-1.8.0.402.b06-2.el8.x86_64 > java-1.8.0-openjdk-devel-1.8.0.402.b06-2.el8.x86_64 > java-1.8.0-openjdk-headless-1.8.0.402.b06-2.el8.x86_64 < kernel-4.18.0-477.27.1.el8_8.x86_64 < kernel-core-4.18.0-477.27.1.el8_8.x86_64 < kernel-core-4.18.0-477.36.1.el8_8.x86_64 < kernel-devel-4.18.0-477.27.1.el8_8.x86_64 < kernel-headers-4.18.0-477.27.1.el8_8.x86_64 < kernel-modules-4.18.0-477.27.1.el8_8.x86_64 < kernel-modules-4.18.0-477.36.1.el8_8.x86_64 < kernel-modules-extra-4.18.0-477.36.1.el8_8.x86_64 --- > kernel-4.18.0-477.51.1.el8_8.x86_64 > kernel-core-4.18.0-477.51.1.el8_8.x86_64 > kernel-devel-4.18.0-477.51.1.el8_8.x86_64 > kernel-headers-4.18.0-477.51.1.el8_8.x86_64 > kernel-modules-4.18.0-477.51.1.el8_8.x86_64 > kernel-modules-extra-4.18.0-477.51.1.el8_8.x86_64 < kernel-tools-4.18.0-477.36.1.el8_8.x86_64 < kernel-tools-libs-4.18.0-477.36.1.el8_8.x86_64 --- > kernel-tools-4.18.0-477.51.1.el8_8.x86_64 > kernel-tools-libs-4.18.0-477.51.1.el8_8.x86_64 < kmod-nvidia-latest-dkms-535.129.03-1.el8.x86_64 --- > kmod-nvidia-latest-dkms-535.161.08-1.el8.x86_64 < libblkid-2.32.1-42.el8_8.x86_64 < libblkid-devel-2.32.1-42.el8_8.x86_64 --- > libblkid-2.32.1-42.el8_8.1.x86_64 > libblkid-devel-2.32.1-42.el8_8.1.x86_64 < libcufile-12-3-1.8.1.2-1.x86_64 < libcufile-devel-12-3-1.8.1.2-1.x86_64 --- > libcufile-12-4-1.9.0.20-1.x86_64 > libcufile-devel-12-4-1.9.0.20-1.x86_64 < libcurl-7.61.1-30.el8_8.6.x86_64 < libcurl-devel-7.61.1-30.el8_8.6.x86_64 --- > libcurl-7.61.1-30.el8_8.9.x86_64 > libcurl-devel-7.61.1-30.el8_8.9.x86_64 < libdrm-amdgpu-2.4.115.50700-1652687.el8.x86_64 < libdrm-amdgpu-common-1.0.0.50700-1652687.el8.noarch < libdrm-amdgpu-devel-2.4.115.50700-1652687.el8.x86_64 --- > libdrm-amdgpu-2.4.116.60000-1697589.el8.x86_64 > libdrm-amdgpu-common-1.0.0.60000-1697589.el8.noarch > libdrm-amdgpu-devel-2.4.116.60000-1697589.el8.x86_64 < libfabric-1.15.2.0-SSHOT2.1.1_20231201144654_1ffeaf21c8dd.el8.x86_64 --- > libfabric-1.15.2.0-SSHOT2.1.2_20240202213349_c1eaa8c31e01.el8.x86_64 < libfabric-devel-1.15.2.0-SSHOT2.1.1_20231201144654_1ffeaf21c8dd.el8.x86_64 < libfastjson-0.99.9-1.el8.x86_64 < libfdisk-2.32.1-42.el8_8.x86_64 --- > libfabric-devel-1.15.2.0-SSHOT2.1.2_20240202213349_c1eaa8c31e01.el8.x86_64 > libfastjson-0.99.9-1.el8_8.1.x86_64 > libfdisk-2.32.1-42.el8_8.1.x86_64 < libmaxminddb-1.2.0-10.el8.x86_64 --- > libmaxminddb-1.2.0-10.el8_8.1.x86_64 < libmount-2.32.1-42.el8_8.x86_64 < libmount-devel-2.32.1-42.el8_8.x86_64 --- > libmount-2.32.1-42.el8_8.1.x86_64 > libmount-devel-2.32.1-42.el8_8.1.x86_64 < libnsl-2.28-225.el8_8.6.x86_64 < libnvidia-nscq-535-535.129.03-1.x86_64 --- > libnsl-2.28-225.el8_8.9.x86_64 > libnvidia-nscq-535-535.161.08-1.x86_64 < libsmartcols-2.32.1-42.el8_8.x86_64 < libsmbclient-4.17.5-4.el8_8.x86_64 --- > libsmartcols-2.32.1-42.el8_8.1.x86_64 > libsmbclient-4.17.5-5.el8_8.x86_64 < libssh-0.9.6-10.el8_8.x86_64 < libssh-config-0.9.6-10.el8_8.noarch --- > libssh-0.9.6-13.el8_8.x86_64 > libssh-config-0.9.6-13.el8_8.noarch < libuuid-2.32.1-42.el8_8.x86_64 < libuuid-devel-2.32.1-42.el8_8.x86_64 --- > libuuid-2.32.1-42.el8_8.1.x86_64 > libuuid-devel-2.32.1-42.el8_8.1.x86_64 > libva-amdgpu-2.16.0.60000-1697589.el8.x86_64 < libwayland-amdgpu-client-1.22.0.50700-1652687.el8.x86_64 < libwayland-amdgpu-server-1.22.0.50700-1652687.el8.x86_64 --- > libwayland-amdgpu-client-1.22.0.60000-1697589.el8.x86_64 > libwayland-amdgpu-server-1.22.0.60000-1697589.el8.x86_64 < libwbclient-4.17.5-4.el8_8.x86_64 --- > libwbclient-4.17.5-5.el8_8.x86_64 < libX11-1.6.8-5.el8.x86_64 < libX11-common-1.6.8-5.el8.noarch < libX11-devel-1.6.8-5.el8.x86_64 < libX11-xcb-1.6.8-5.el8.x86_64 --- > libX11-1.6.8-6.el8_8.x86_64 > libX11-common-1.6.8-6.el8_8.noarch > libX11-devel-1.6.8-6.el8_8.x86_64 > libX11-xcb-1.6.8-6.el8_8.x86_64 < linux-firmware-20230404-117.git2e92a49f.el8_8.noarch --- > linux-firmware-20230404-118.git2e92a49f.el8_8.noarch < llvm-amdgpu-libs-16.0.50700-1652687.el8.x86_64 --- > llvm-amdgpu-libs-17.0.60000-1697589.el8.x86_64 < lustre-client-2.14.0_ddn125-1.el8.x86_64 < lustre-client-devel-2.14.0_ddn125-1.el8.x86_64 < lustre-client-dkms-2.14.0_ddn125-1.el8.noarch --- > lustre-client-2.14.0_ddn136-1.el8.x86_64 > lustre-client-devel-2.14.0_ddn136-1.el8.x86_64 > lustre-client-dkms-2.14.0_ddn136-1.el8.noarch < mesa-amdgpu-dri-drivers-23.2.0.50700-1652687.el8.x86_64 < mesa-amdgpu-filesystem-23.2.0.50700-1652687.el8.x86_64 < mesa-amdgpu-libEGL-23.2.0.50700-1652687.el8.x86_64 < mesa-amdgpu-libgbm-23.2.0.50700-1652687.el8.x86_64 < mesa-amdgpu-libGL-23.2.0.50700-1652687.el8.x86_64 < mesa-amdgpu-libglapi-23.2.0.50700-1652687.el8.x86_64 < mesa-amdgpu-libxatracker-23.2.0.50700-1652687.el8.x86_64 < mesa-amdgpu-vdpau-drivers-23.2.0.50700-1652687.el8.x86_64 --- > mesa-amdgpu-dri-drivers-23.3.0.60000-1697589.el8.x86_64 > mesa-amdgpu-filesystem-23.3.0.60000-1697589.el8.x86_64 > mesa-amdgpu-libEGL-23.3.0.60000-1697589.el8.x86_64 > mesa-amdgpu-libgbm-23.3.0.60000-1697589.el8.x86_64 > mesa-amdgpu-libGL-23.3.0.60000-1697589.el8.x86_64 > mesa-amdgpu-libglapi-23.3.0.60000-1697589.el8.x86_64 > mesa-amdgpu-libxatracker-23.3.0.60000-1697589.el8.x86_64 > mesa-amdgpu-vdpau-drivers-23.3.0.60000-1697589.el8.x86_64 > mesa-filesystem-22.3.0-2.el8.x86_64 < NetworkManager-1.40.16-5.el8_8.x86_64 < NetworkManager-libnm-1.40.16-5.el8_8.x86_64 < NetworkManager-team-1.40.16-5.el8_8.x86_64 < NetworkManager-tui-1.40.16-5.el8_8.x86_64 --- > NetworkManager-1.40.16-9.el8_8.x86_64 > NetworkManager-libnm-1.40.16-9.el8_8.x86_64 > NetworkManager-team-1.40.16-9.el8_8.x86_64 > NetworkManager-tui-1.40.16-9.el8_8.x86_64 < nss-3.90.0-3.el8_8.x86_64 < nss-softokn-3.90.0-3.el8_8.x86_64 < nss-softokn-freebl-3.90.0-3.el8_8.x86_64 < nss-sysinit-3.90.0-3.el8_8.x86_64 < nss-tools-3.90.0-3.el8_8.x86_64 < nss-util-3.90.0-3.el8_8.x86_64 --- > nss-3.90.0-6.el8_8.x86_64 > nss-softokn-3.90.0-6.el8_8.x86_64 > nss-softokn-freebl-3.90.0-6.el8_8.x86_64 > nss-sysinit-3.90.0-6.el8_8.x86_64 > nss-tools-3.90.0-6.el8_8.x86_64 > nss-util-3.90.0-6.el8_8.x86_64 < nvidia-driver-535.129.03-1.el8.x86_64 < nvidia-driver-cuda-535.129.03-1.el8.x86_64 < nvidia-driver-cuda-libs-535.129.03-1.el8.x86_64 < nvidia-driver-devel-535.129.03-1.el8.x86_64 < nvidia-driver-libs-535.129.03-1.el8.x86_64 < nvidia-driver-NvFBCOpenGL-535.129.03-1.el8.x86_64 < nvidia-driver-NVML-535.129.03-1.el8.x86_64 < nvidia-fabric-manager-535.129.03-1.x86_64 < nvidia-fs-2.18.3-1.x86_64 < nvidia-fs-dkms-2.18.3-1.x86_64 < nvidia-gds-12.3.1-1.x86_64 < nvidia-gds-12-3-12.3.1-1.x86_64 < nvidia-kmod-common-535.129.03-1.el8.noarch < nvidia-libXNVCtrl-535.129.03-1.el8.x86_64 < nvidia-libXNVCtrl-devel-535.129.03-1.el8.x86_64 < nvidia-modprobe-535.129.03-1.el8.x86_64 < nvidia-persistenced-535.129.03-1.el8.x86_64 < nvidia-settings-535.129.03-1.el8.x86_64 < nvidia-xconfig-535.129.03-1.el8.x86_64 --- > nvidia-driver-535.161.08-1.el8.x86_64 > nvidia-driver-cuda-535.161.08-1.el8.x86_64 > nvidia-driver-cuda-libs-535.161.08-1.el8.x86_64 > nvidia-driver-devel-535.161.08-1.el8.x86_64 > nvidia-driver-libs-535.161.08-1.el8.x86_64 > nvidia-driver-NvFBCOpenGL-535.161.08-1.el8.x86_64 > nvidia-driver-NVML-535.161.08-1.el8.x86_64 > nvidia-fabric-manager-535.161.08-1.x86_64 > nvidia-fs-2.19.6-1.x86_64 > nvidia-fs-dkms-2.19.6-1.x86_64 > nvidia-gds-12.4.0-1.x86_64 > nvidia-gds-12-4-12.4.0-1.x86_64 > nvidia-kmod-common-535.161.08-1.el8.noarch > nvidia-libXNVCtrl-535.161.08-1.el8.x86_64 > nvidia-libXNVCtrl-devel-535.161.08-1.el8.x86_64 > nvidia-modprobe-535.161.08-1.el8.x86_64 > nvidia-persistenced-535.161.08-1.el8.x86_64 > nvidia-settings-535.161.08-1.el8.x86_64 > nvidia-xconfig-535.161.08-1.el8.x86_64 < openssh-8.0p1-19.el8_8.x86_64 < openssh-clients-8.0p1-19.el8_8.x86_64 < openssh-server-8.0p1-19.el8_8.x86_64 < openssl-1.1.1k-9.el8_7.x86_64 < openssl-devel-1.1.1k-9.el8_7.x86_64 < openssl-libs-1.1.1k-9.el8_7.x86_64 --- > openssh-8.0p1-19.el8_8.2.x86_64 > openssh-clients-8.0p1-19.el8_8.2.x86_64 > openssh-server-8.0p1-19.el8_8.2.x86_64 > openssl-1.1.1k-12.el8_8.x86_64 > openssl-devel-1.1.1k-12.el8_8.x86_64 > openssl-libs-1.1.1k-12.el8_8.x86_64 < pam-1.3.1-25.el8.x86_64 < pam-devel-1.3.1-25.el8.x86_64 --- > pam-1.3.1-26.el8_8.x86_64 > pam-devel-1.3.1-26.el8_8.x86_64 < perf-4.18.0-477.36.1.el8_8.x86_64 --- > perf-4.18.0-477.51.1.el8_8.x86_64 < perl-HTTP-Tiny-0.074-1.el8.noarch --- > perl-HTTP-Tiny-0.074-1.el8_8.2.noarch < platform-python-3.6.8-51.el8_8.2.x86_64 < platform-python-devel-3.6.8-51.el8_8.2.x86_64 < platform-python-pip-9.0.3-22.el8.noarch --- > platform-python-3.6.8-51.el8_8.5.x86_64 > platform-python-devel-3.6.8-51.el8_8.5.x86_64 > platform-python-pip-9.0.3-22.3.el8_8.noarch < python3-bind-9.11.36-8.el8_8.2.noarch --- > python3-bind-9.11.36-8.el8_8.3.noarch < python3-libs-3.6.8-51.el8_8.2.x86_64 --- > python3-libs-3.6.8-51.el8_8.5.x86_64 < python3-perf-4.18.0-477.36.1.el8_8.x86_64 < python3-pip-9.0.3-22.el8.noarch < python3-pip-wheel-9.0.3-22.el8.noarch --- > python3-perf-4.18.0-477.51.1.el8_8.x86_64 > python3-pip-9.0.3-22.3.el8_8.noarch > python3-pip-wheel-9.0.3-22.3.el8_8.noarch < python3-rpm-4.14.3-26.el8.x86_64 --- > python3-rpm-4.14.3-28.el8_8.x86_64 < python3-unbound-1.16.2-5.el8.x86_64 < python3-urllib3-1.24.2-5.el8.noarch --- > python3-unbound-1.16.2-5.el8_8.1.x86_64 > python3-urllib3-1.24.2-5.el8_8.1.noarch < rpm-4.14.3-26.el8.x86_64 < rpm-build-4.14.3-26.el8.x86_64 < rpm-build-libs-4.14.3-26.el8.x86_64 < rpm-libs-4.14.3-26.el8.x86_64 < rpm-plugin-selinux-4.14.3-26.el8.x86_64 < rpm-plugin-systemd-inhibit-4.14.3-26.el8.x86_64 < rpm-sign-4.14.3-26.el8.x86_64 --- > rpm-4.14.3-28.el8_8.x86_64 > rpm-build-4.14.3-28.el8_8.x86_64 > rpm-build-libs-4.14.3-28.el8_8.x86_64 > rpm-libs-4.14.3-28.el8_8.x86_64 > rpm-plugin-selinux-4.14.3-28.el8_8.x86_64 > rpm-plugin-systemd-inhibit-4.14.3-28.el8_8.x86_64 > rpm-sign-4.14.3-28.el8_8.x86_64 < samba-client-libs-4.17.5-4.el8_8.x86_64 < samba-common-4.17.5-4.el8_8.noarch < samba-common-libs-4.17.5-4.el8_8.x86_64 --- > samba-client-libs-4.17.5-5.el8_8.x86_64 > samba-common-4.17.5-5.el8_8.noarch > samba-common-libs-4.17.5-5.el8_8.x86_64 < selinux-policy-3.14.3-117.el8_8.3.noarch < selinux-policy-targeted-3.14.3-117.el8_8.3.noarch --- > selinux-policy-3.14.3-117.el8_8.4.noarch > selinux-policy-targeted-3.14.3-117.el8_8.4.noarch < sl-driver-devel-0.1-SSHOT2.2.0_20231130192126_2c77221b0ab3.x86_64 < sl-driver-dkms-0.1-SSHOT2.2.0_20231130192126_2c77221b0ab3.noarch < slingshot-firmware-cassini-1.5.41-SSHOT2.2.0_20230518023242_fa36f5e4e7f9.noarch --- > sl-driver-devel-0.1-SSHOT2.3.0_20240131000152_2c77221b0ab3.x86_64 > sl-driver-dkms-0.1-SSHOT2.3.0_20240131000152_2c77221b0ab3.noarch > slingshot-firmware-cassini-1.5.49-SSHOT2.2.0_20240117202345_e618b2ae2136.noarch < sqlite-3.26.0-18.el8_8.x86_64 < sqlite-libs-3.26.0-18.el8_8.x86_64 --- > sqlite-3.26.0-18.el8_8.1.x86_64 > sqlite-libs-3.26.0-18.el8_8.1.x86_64 < squashfuse-0.1.104-1.el8.x86_64 < squashfuse-libs-0.1.104-1.el8.x86_64 < sudo-1.8.29-10.el8.x86_64 --- > sudo-1.9.5p2-1.el8_8.x86_64 < tcpdump-4.9.3-3.el8.x86_64 --- > tcpdump-4.9.3-3.el8_8.1.x86_64 < tzdata-2023c-1.el8.noarch < tzdata-java-2023c-1.el8.noarch < unbound-1.16.2-5.el8.x86_64 < unbound-libs-1.16.2-5.el8.x86_64 --- > tzdata-2024a-1.el8.noarch > tzdata-java-2024a-1.el8.noarch > unbound-1.16.2-5.el8_8.1.x86_64 > unbound-libs-1.16.2-5.el8_8.1.x86_64 < util-linux-2.32.1-42.el8_8.x86_64 < util-linux-user-2.32.1-42.el8_8.x86_64 --- > util-linux-2.32.1-42.el8_8.1.x86_64 > util-linux-user-2.32.1-42.el8_8.1.x86_64 < xorg-x11-amdgpu-drv-amdgpu-24.1.0-1652687.el8.x86_64 --- > xorg-x11-amdgpu-drv-amdgpu-24.1.0-1697589.el8.x86_64

Posted: March 20, 2026

Infrastructure News Type: Outage Partial

Affected Infrastructure: tickets.access-ci.org

Start Date: March 20, 2024, 6:16 p.m.

End Date: March 20, 2024, 10:00 p.m.

Problems creating issues and transitions for Jira Service Management, Jira Work Management, and Jira Software. The issue has been resolved and the service is operating normally. More details available here (https://jira-service-management.status.atlassian.com/incidents/mx35ghg6m8qq).

Posted: March 20, 2026

Infrastructure News Type: Outage Partial

Affected Infrastructure: delta-cpu.ncsa.access-ci.org, delta-gpu.ncsa.access-ci.org

Start Date: March 14, 2024, 1:00 p.m.

End Date: March 15, 2024, 10:00 p.m.

The maintenance on the Taiga servers that provide the /projects file system on Delta encountered an issue early last night. Delta staff are working with the vendors to resolve the issue and return the file system to service. Currently, no estimation is available for /projects return to service. We will provide updates as new information becomes available. The Delta system continues to run jobs that do not indicate a need for the /projects file system (see below). The Delta projects (/projects) file system will be unavailable on March 14th from 8AM to 8PM for server-side maintenance. The upgraded software will allow for the enforcement of quotas on the projects file system. We recommend that research teams that are over quota in /projects start to clean up and get back under quota. Two days before the maintenance day, jobs already in the queue will be put on hold that have the projects file system as a slurm Feature or Constraint. Jobs that do not require /projects or /taiga file systems as a Feature will be allowed to run. If your job requires files in /projects then be sure to add the appropriate constraint as shown below. See below for information on how to specify file systems as a job Feature for already submitted jobs. Please send questions to help@ncsa.illinois.edu (mailto:help@ncsa.illinois.edu) and be sure to mention Delta in the subject or message body. --Delta Project Office To indicate that a job uses the /projects file system at job submission add the --constraint option to batch scripts: #SBATCH --constraint="projects" or add it to the command line: $ sbatch --constraint="projects" ... For an already submitted but not yet running job use: $ scontrol update job=JOBID Features="projects" replacing JOBID with the appropriate job id. Please see https://docs.ncsa.illinois.edu/systems/delta/en/latest/user_guide/architecture.html#file-system-dependency-specification-for-jobs

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: bridges2-em.psc.access-ci.org, bridges2-gpu.psc.access-ci.org, bridges2-rm.psc.access-ci.org, bridges2-ocean.psc.access-ci.org

Start Date: March 13, 2024, 8:13 p.m.

End Date: March 13, 2024, 10:30 p.m.

Due to a power outage at the machine room, Bridges-2 is unavailable. Thank you for your patience while we restore full functionality.

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: anvil.purdue.access-ci.org, anvil-gpu.purdue.access-ci.org

Start Date: March 12, 2024, 12:00 p.m.

End Date: March 13, 2024, 12:05 a.m.

Update as of March 12th 2024 8:05pm EDT The maintenance is now concluded and Anvil has been returned to service. Please submit a ticket through ACCESS Help Desk at https://support.access-ci.org/open-a-ticket if you have any questions. Update as of March 12th 2024 5:42pm EDT Engineers are experiencing multiple outages at this time due to power disruption. Due to this, the scheduled Anvil cluster maintenance is being extended until Tuesday, March 12th at 10pm. Please submit a ticket through ACCESS Help Desk at https://support.access-ci.org/open-a-ticket if you have any questions. Original News The Anvil cluster is unavailable beginning Tuesday, March 12th 2024 at 8:00am for a scheduled maintenance. It will return to full production by Tuesday, March 12th at 5pm. During this time, Anvil will have rack and power maintenance performed. Any jobs requesting a walltime which would take them past Tuesday, March 12th, 2024 at 8:00am will not start and will remain in the queue until after the maintenance is completed. Please submit a ticket through ACCESS Help Desk at https://support.access-ci.org/open-a-ticket if you have any questions.

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: bridges2-em.psc.access-ci.org, bridges2-gpu.psc.access-ci.org, bridges2-rm.psc.access-ci.org, bridges2-ocean.psc.access-ci.org

Start Date: March 5, 2024, 7:15 p.m.

End Date: March 5, 2024, 8:44 p.m.

Bridges-2 is currently undergoing maintenance to address some filesystem issues. Our team is working on returning the system to full service.

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: kerberos.access-ci.org

Start Date: March 5, 2024, 7:00 p.m.

End Date: March 5, 2024, 10:00 p.m.

The Master Kerberos KDC will be upgraded to RHEL8. DUring this time users will not be able to create account or change passwords. Authentication should not be affected

Posted: March 20, 2026

Infrastructure News Type: Outage Partial

Affected Infrastructure: tickets.access-ci.org

Start Date: February 28, 2024, 12:00 p.m.

End Date: March 1, 2024, 4:00 p.m.

JIRA Service Management automation rules issue detailed here: - https://jira-service-management.status.atlassian.com/incidents/rrhk1kk4m0kv

Posted: March 20, 2026

Infrastructure News Type: Outage Partial

Affected Infrastructure: anvil.purdue.access-ci.org, anvil-gpu.purdue.access-ci.org

Start Date: February 27, 2024, 1:00 p.m.

End Date: February 27, 2024, 10:00 p.m.

The underlying issue has been isolated and the outage is resolved __________________________________________________________ The Anvil cluster began experiencing issues with Slurm Scheduling this past week. Engineers are currently diagnosing the root cause and are working to identify a fix. Scheduling is still enabled at this time. You may experience periodic SLURM outage where command will be unable to connect to the slurm controller. This can cause jobs to take longer than normal, and in some instanes fail. In addition, Open Ondemand relies on Slurm to run applications. When these issues with slurm occur, the menu in OOD may appear empty or non functional. We will provide another update by 5PM EST today

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: expanse.sdsc.access-ci.org, expanse-gpu.sdsc.access-ci.org, expanse-ps.sdsc.access-ci.org

Start Date: February 12, 2024, 4:00 p.m.

End Date: February 13, 2024, 12:00 a.m.

>>> Update The Expanse maintenance is complete and the reservation has been released and jobs are running. Slurm has been updated to version 23.02.7. Please contact us via the ACCESS ticketing system if you have any questions. >>> Original message We will have a maintenance period on Expanse 8AM-5PM (PT), Feb 12, 2024. During this maintenance, we will be updating the Slurm scheduler. We have a reservation in place to prevent jobs from running during this period. The "squeue" output will show "ReqNodeNotAvail, Reserved for maintenance" for jobs that do not fit in the time period before the maintenance begins. These jobs will run after we release the maintenance reservation.

Posted: March 20, 2026

Infrastructure News Type: Outage Full

Affected Infrastructure: anvil.purdue.access-ci.org, anvil-gpu.purdue.access-ci.org

Start Date: February 7, 2024, 1:00 p.m.

End Date: February 8, 2024, 3:00 a.m.

Maintenance is now complete and Anvil has been returned to service —————-/ Anvil maintenance has been extended. We will provide a other update by 10PM — The Anvil system will be unavailable Wednesday, February 7th, 2024 from 8:00am - 6:00pm EDT for scheduled maintenance. Any Slurm jobs which request a walltime which would take them past Wednesday, February 7th, 2024 at 8:00am EDT will not start and will remain in the queue until after the maintenance is completed. Anvil will return to full production by Wednesday, February 7th, 2024 at 6:00pm EDT. Please submit a ticket through ACCESS Help Desk at https://support.access-ci.org/open-a-ticket if you have any questions.

Posted: March 20, 2026

Infrastructure News Type: Reconfiguration

Affected Infrastructure: aces.tamu.access-ci.org

Start Date: February 5, 2024, 3:00 p.m.

End Date: February 16, 2024, 12:00 a.m.

Beginning at 9am on Monday February 5 to 6pm on Friday February 15, 60 compute nodes, all 30 NVIDIA H100 GPUs, and all Intel PVC GPUs will be unavailable while we redeploy those hardware into four new hardware composability fabrics. The remaining 50 compute nodes on the other four composability fabrics will remain online during this time. All other ACES services such as account access, data transfer, job submission, etc. will remain available during this period.

Posted: March 20, 2026