Stokes login node maintenance, Mon.26.June 8a-5p

Details

Written by R. Paul Wiegand R. Paul Wiegand

Published: 19 June 2017 19 June 2017

• maintenance

The ARCC team will need to perform some maintenance on our login node for Stokes. We've schedule next Monday, June 26 from 8a-5p to perform this work. During this time, you will not be able to log into Stokes or to scp files to/from Stokes; however, all jobs will continue and no compute nodes will be taken down as a part of this maintenance. We appreciate your patience, Paul.

End of ARCC Spring 2017 Maintenance Cycle

Details

Written by R. Paul Wiegand R. Paul Wiegand

Published: 08 May 2017 08 May 2017

• downtime
• maintenance

Stokes and Newton have returned to operation two days early! Please remember that we have two such maintenance downtimes per year, one in late Fall and one in late Spring.

The work performed during this downtime should not affect users. These were regular maintenance efforts that must be performed when the system is offline, but there were no changes to user, software, or hardware configurations. Fortunately, we were able to complete these early this cycle. Among the tasks performed were:

• Replacement of a redundant component within our Lustre file system;
• Regularization of the configuration management tools to make Newton more consistent with Stokes;
• Some improvements to hardware monitoring tools;
• Wide-scale performance testing.

The ARCC staff appreciates your patience and thank you for your use of the resources! If you have any questions or concerns, please contact us!

Paul Wiegand & Glenn Martin

Spring Maintenance cycle downtime, May.3-May.10

Details

Written by R. Paul Wiegand R. Paul Wiegand

Published: 30 March 2017 30 March 2017

Stokes and Newton will be taken down per our bi-annual routine maintenance cycle during early May. Specifically, the clusters will be unavailable from the morning of Wednesday, May 3 through the morning of Thursday, May 11.

Changes made during downtime will be minimal and should not affect users. We will provide more detail in the change log when we bring the system back online.

Recall that we now routinely bring the system down twice a year, once in late Fall and once in late Spring. We will keep the users notified in advance of such downtimes, but we recommend you build such expectations into your workflow. Though we anticipate no data loss during this time, it's never a bad idea to backup your materials. So we suggest you use this opportunity to copy salient data and code off of Stokes prior to the downtime.