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 Resolutionsort ascending Description Posted Updated
Podman storage error due to outdated configuration file Software Resolved
(workaround)

If you experience a storage error such as:

 write /var/tmp/storage388772891/1: no space left on device.

you may have an outdated ~/....

Read more
1 year 1 month ago 1 year 1 month ago
Brief interruption of batch services on 4/17 Batch Resolved

On April 17th 2013, at roughly 2PM, we will be rebooting the batch server on the Oakley cluster. Running jobs will not be affected, but there will be a brief disruption in scheduling, as well as...

Read more
13 years 4 months ago 13 years 4 months ago
Rolling reboot of Owens cluster, starting from 9AM June 28, 2017 Owens Resolved

Update posted on July 7, 2017 at 2:00PM:

Rolling reboot of login and compute nodes of Owens cluster is completed. 

... Read more
9 years 2 months ago 9 years 2 months ago
ORCA Bind to CORE Failure Software Resolved
(workaround)

The default CPU binding for ORCA jobs can fail sporadically.  The failure is almost immediate and produces a cryptic error message, e.g.:

...
Read more
3 years 4 months ago 1 year 3 months ago
Temporary Login Node Instability on Ascend and Cardinal Ascend, Cardinal Unresolved

We are currently experiencing temporary instability on the Ascend and Cardinal login nodes, which may result in slow response times or unexpected session disconnects. Our team is actively...

Read more
3 months 1 week ago 1 week 3 days ago

Pages