Due to a critical security vulnerability we need to reboot public-facing systems to deploy a mitigation against the vulnerabilit
Known issue with an Unresolved Resolution state is an active problem under investigation; a temporary workaround may be available.
A known issue with a Resolved (workaround) Resolution state is an ongoing problem; a permanent workaround is available which may include using different software or hardware.
A known issue with Resolved Resolution state has been corrected.
| Title | Category |
Resolution |
Description | Posted | Updated |
|---|---|---|---|---|---|
| Job failures on some rolling-rebooted nodes on Owens since April 16, 2018 | Owens |
Resolved |
3:35 PM 4/30/2018 Update: The cause is that NFSv4.1 is not configured correctly after OS on Owens was updated from RHEL 7.3 to 7.4. We re-rebooted the Owens compute nodes... Read more |
8 years 3 weeks ago | 8 years 1 week ago |
| Issue with submitting job array | Batch, Owens |
Resolved |
3:30 PM 5/10/2018 Original Post: User may have been getting the following error message when trying to submit a PBS job using job arrays: qsub: submit error (Maximum number of... Read more |
8 years 18 hours ago | 4 years 5 months ago |
| Rolling reboot of all clusters, starting from 8 AM Tuesday, June 19, 2018 | Batch, Owens, Ruby |
Resolved |
Posted on June 12, 2018, at 4:40 PM: We will have rolling reboots of three clusters (Owens, Ruby, and Oakley) including login and compute nodes, starting from 8 AM Tuesday... Read more |
7 years 11 months ago | 7 years 10 months ago |
| LAMMPS ppn=40 GPU problem on Pitzer | Pitzer, Software |
Resolved |
On Pitzer both LAMMPS 22Aug18 and 5Jun19 gpu jobs with ppn=40 hang immediately after lammps begins execution. A workaround is to use ppn=39. |
7 years 6 months ago | 6 years 3 months ago |
