Maintenance

Rolling reboots on owens and pitzer starting 18 Aug 2021

We will have rolling reboots of Owens and Pitzer cluster, including login and compute nodes, starting from 9am on August 18, 2021. The rolling reboot is for urgent security updates.

The rolling reboots won't affect any running jobs, but users may experience longer queue wait time than usual on the cluster. User will also expect about a 10 minute outage of login nodes during the reboot of login nodes. If there are interactive jobs started from a login node and that login node is rebooted, then the job will be killed.

Jupyter security issue Aug. 13, 2021

Please do not run any Jupyter applications at OSC until further notice due to a security vulnerability.

OSC will update JupyterLab and Jupyter Notebook applications to rectify this as soon as possible.

List of versions changed:

  • 0.35: removed because there is no official patch release.
  • 1.2: upgraded to 1.2.21
  • 2.1: replaced with 2.2.10 because there is no official patch release.
  • 3.0: upgraded to 3.0.17

References for more information:

Rolling reboot of all clusters, starting from Wednesday morning, April 19, 2017

1:40PM 4/27/2017 Update: Rolling reboots are completed. 

3:10PM 4/18/2017 Update: Rolling reboots on Owens have started to address GPFS errors occured late Friday. 

Rolling reboot of Owens, Oakley, and Ruby clusters is scheduled to start from Wednesday morning, April 19, 2017. Highlights of the rolling reboot activities:

Lustre is still offline. HPC systems back up

Day One of the scheduled downtime has been completed, and HPC operations have resumed. As planned, Lustre work will extend into Day Two. Jobs using /fs/lustre or $PFSDIR cannot run until this work is completed, but all other jobs can run.

UPDATE: Performance problems with Lustre have prevented us from bringing up the filesystem. We are working on a resolution.

UPDATE: Lustre returned to service the afternoon of July 12th, 2014.