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

Title Category Resolution Description Posted Updated
Error 'libim_client.so: undefined reference to uuid@' with MVAPICH2 in Conda environment Owens, Pitzer, Software Resolved

Users may encoutner an error like 'libim_client.so: undefined reference to `uuid_unparse@UUID_1.0' while compiling MPI applications with mvapich2 in some Conda enivronments. We found pre-installed... Read more

4 years 8 months ago 2 years 7 months ago
Gaussian g16b01 G4 problem Owens, Pitzer, Software Resolved
(workaround)

Gaussian-4 (G4) theory calculations in Gaussian 16 Rev. B.01 can produce erratic results.  A workaround is to use Gaussian 16 Rev. A.03 or Rev. C.01, e.g.: 

module load gaussian/... Read more          
5 years 9 months ago 2 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          
4 years 7 months ago 2 years 7 months ago
Singularity: reached your pull rate limit Owens, Pitzer, Software Resolved
(workaround)

You might encounter an error while pulling a large Docker image:

ERROR: toomanyrequests: Too Many Requests.

or

You have reached your pull rate limit. You may... Read more          
3 years 5 months ago 2 years 7 months 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          
3 years 4 months ago 2 years 7 months ago
Cannot use mpiexec/mpirun from OpenMPI in an interactive session Owens, Pitzer, Software Resolved
(workaround)

We found mpiexec/mpirun from OpenMPI can not be used in an interactive session (launched by sinteractive) after upgrading Pitzer and... Read more

3 years 8 months ago 2 years 7 months ago
A partial-node MPI job failed to start using Intel MPI mpiexec Owens, Pitzer, Software Resolved
(workaround)

A partial-node MPI job may fail to start using mpiexec from intelmpi/2019.3 and intelmpi/2019.7 with error messages like

[mpiexec@o0439.ten.osc.... Read more          
4 years 3 weeks ago 2 years 7 months ago
MyOSC may not show usage for 28 March 2022 client portal Resolved

MyOSC may not show job usage for 28 March 2022. There is only partial job data for this date at the moment.

Resolution notes:

The job usage for... Read more

2 years 7 months ago 2 years 7 months ago
starccm/15.02.007 with intelmpi after Mar 22, 2022 Resolved
(workaround)

STAR-CCM+ 15.02.007 and 15.02.007-mixed with intelMPI would fail on multiple node jobs after the downtime on Mar 22, 2022. Please use openmpi instead. You can find more... Read more

2 years 8 months ago 2 years 8 months ago
Missing shared library of some mvapich2 modules Owens, Pitzer Resolved

Updates on Feb 25 2022:

This issue is fixed. 

Original Post:

Users may see an issue of missing shared library with some mvapich2 modules... Read more

2 years 9 months ago 2 years 8 months ago

Pages