Known issues

Unresolved known issues

Known issue with an Unresolved Resolution state is an active problem under investigation; a temporary workaround may be available.

Resolved known issues

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.

Known Issues

Titlesort ascending Category Resolution Description Posted Updated
Downtime Update: All Major Services Online Resolved

Friday, Sept 25th 12PM Noon:

  • Oakley is back online and has resumed running jobs.  
  • Ruby... Read more
10 years 4 months ago 10 years 4 months ago
DOWNTIME EXTENDED UNTIL MORNING OF 12/13/17 Resolved

We have extended the 12/12/2017 downtime until 7AM on 12/13/17 to complete filesystem maintenance that has taken longer than expected.

8 years 1 month ago 8 years 1 month ago
Docker container runtime error on desktop due to DBUS session Software Resolved
(workaround)

When running a container using the podman or docker command on a desktop system, you may encounter an error like the following:

Error: OCI... Read more          
6 months 1 week ago 6 months 1 week ago
Dec 27, 2016: Issues with /fs/project filesystem Resolved

Dec 27, 2016 3:46PM Update: Both project and scratch file systems (/fs/project and /fs/scratch ) are back to normal now.  Some users' jobs may be... Read more

9 years 1 month ago 9 years 1 month ago
Data on /fs/scratch is not accessible filesystem Resolved

Updated on 10:30 AM July 3rd, 2019:

Data on /fs/scratch is accessible now. We are working with the vendor to find the root cause and apologize for any inconvenience.  ... Read more

6 years 7 months ago 6 years 7 months ago
cuda-gdb segmentation fault on startup Owens, Pitzer, Software Resolved

The CUDA debugger, cuda-gdb, can raise a segmentation fault immediately upon execution.  A workaround before executing cuda-gdb is to unload the xalt module, e.g.: 

module unload... Read more          
5 years 9 months ago 3 years 10 months ago
Critical change about using $PFSDIR directory at OSC Batch Resolved

Starting from Thursday, Feb 2nd, the $PFSDIR directory on scratch (/fs/scratch) won’t be created by job prologue. For example, if you simply use the command cd $PFSDIR,... Read more

9 years 1 week ago 8 years 12 months ago
cp2k/2023.2 can produce huge output containing MKL messages Ascend, Cardinal, Pitzer, Software Resolved
(workaround)

On all clusters the cp2k executables from module cp2k/2023.2 can produce huge output files due to many many repeating errors from MKL, e.g.:

... Read more          
6 months 3 days ago 4 months 1 week ago
CP2K 6.1 would fail on Pitzer Cascade Lakes (48-core) node: Pitzer Resolved
(workaround)

CP2K 6.1 would fail with the following error when running on Pitzer Cascade Lakes (48-core) node:

Program received signal SIGFPE: Floating-point exception - erroneous arithmetic... Read more          
4 years 7 months ago 9 months 11 hours ago
CP2K 6.1 Floating-point exception on Pitzer Cascade Lakes (48-core) node Owens, Pitzer Resolved
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.

Backtrace for this error:

Thid could be a bug in libxsmm 1.9.0 which is released on Mar 15... Read more

1 year 3 months ago 1 year 3 months ago

Pages