Updated on Oct 29, 2018 1:52:20 PM
Lonestar5 maintenance is still in progress. We have finished the larger systems and network updates and are currently submitting acceptance jobs with the HPC group. We will provide further updates as we get closer to production status. Thank you for your patience.
Updated on Oct 20, 2018 8:07:41 PM
The Lonestar5 maintenance is continuing for longer than anticipated. System administrators are still working to bring up and customize the upgraded operating system, networks, and file systems. With the substantial progress made so far we have forgone our option to revert. Please be on the lookout for new announcements as we approach production status. We appreciate your patience in this substantial undertaking.
Updated on Oct 8, 2018 9:26:09 AM
This is a reminder to the already posted and atypically long maintenance window booked for the dates: Sunday, October 14 through Saturday, October 20, 2018. The full announcement is here: https://portal.tacc.utexas.edu/user-news/-/news/103097.
Jobs that queue up before the maintenance that can't complete (reported by the scheduler with the following state: ReqNodeNotAvail, UnavailableNodes:nid00[XXX-XXX]) will be removed from the queues at the start of the maintenance.
Updated on Oct 1, 2018 9:28:03 AM
This is a reminder to the already posted and unusually long maintenance window booked for the dates: Sunday, October 14 through Saturday, October 20, 2018. The full announcement is here: https://portal.tacc.utexas.edu/user-news/-/news/103097.
The most common question question received so far is which glibc version will exist after the update: GNU libc 2.22
-Thanks for your continued use of TACC Systems.
We will be taking an exceptionally long, one time only maintenance period on Lonestar5 from Sunday, October 14 through Saturday, October 20, 2018. Many of you have likely noticed “old” components in the software stack for Lonestar; unfortunately at this point our only option to update involves essentially reinstalling parts of the core OS from scratch – and the unique nature of the Cray makes this exceptionally time-consuming.
Please communicate, by submitting a ticket, any major concerns and we'll attempt to find alternative accommodations on other systems if necessary. Once again, we apologize for this multi-day disruption, and we hope (and have spent the last year working with Cray to ensure) that this is an extraordinary one-time event.
Thanks for your continued use of TACC Systems.