SWT2_CPB: 

• GGUS-Ticket-ID: #1003078 - SWT2_CPB transfer failures as source with File Not Found error

  • Received replacement PERC to install in storage where we took the PERC from for faster repair. 

  • Replaced the problematic drive in this storage to rebuild.

  • We are currently running diagnostic tests on both storage servers involved, rebuilt, and are performing other tests after repairs to check for any additional issues. 

  • Storage server has been stable since PERC replacement. 

• GGUS-Ticket-ID: #1003053 - IGTF CRLs & fetch-crl SHA1 signature validation (SWT2_CPB)

  • We requested this XRootD Proxy server be removed from our DNS round robin two weeks ago, but they were able to remove it yesterday.  

  • This reduces the number of XRootD Proxy servers we have active down to three, and allows us to check this server more thoroughly and rebuild. 

  • The last transfer error we experienced due to this was yesterday, since this DTN was just removed then. 

• We experienced some brief transfer errors throughout the past two weeks as we worked toward upgrading the network of the XRootD Proxy server racks. 

• We rebuilt the last ME4084 storage server to EL9. It was temporarily out of service with no real data (not in production). 

• We changed the “Monitored” parameter for our test cluster to “True” in CRIC. 

  • Service Protocol: SWT2_CPB_SE_TEST-XROOTD-xrdb.local/XROOTD

  • Service Protocol: SWT2_CPB_SE_TEST-XROOTD-gridftp.swt2.uta.edu/XROOTD

  • Service Protocol: SWT2_CPB_SE_TEST-WEBDAV-gridftp.swt2.uta.edu/WEBDAV

• We experienced some issues with jobs due to the high number of single core jobs on 7/4. 

  • We believe this is due to our Slurm max job limit, and slightly increased this to from 12000 to 13000 to see if the issue resolves. We may gradually increase this over time to fix if needed. 

• CVE-2026-55200 does not apply to us, so no action taken. We have a different libssh2 version. 

OU:

• Back up from scheduled maintenance, but at reduced capacity, until OSCER has had time to re-image all nodes.
• New SE, OU_OSCER_ATLAS_SE_1 should be up now, so assuming that works, we will need to migrate from the old and out of date SE to this new one as fast as possible, because of new stricter OU IT security rules.