FAS Research Computing - Lịch sử thông báo

The affected partitions are back up within acceptable operating percentages.

Modules should be available again across Cannon and FASSE. If you have an open session, please log out and log in again to use modules.

This incident has been resolved.

This incident has been resolved.

We have brought the server back online in a "workaround" state and will be continuing to investigate the root cause. Access should be normal.

This incident has been resolved.

Firmware updates have resolved this issue.

The proscribed driver update did not fix this issue.

We are working with Nvidia to find a fix. As a stop-gap nodes which get stuck/flagged will be marked in Slurm for reboot and rebooted once empty of jobs.

If a A100 GPU host your lab owns is stuck in a bad state, please let us know and we will mark and reboot it.

A100s are open but still experiencing some instability. Infrequently, you may hit the issue we noted earlier.

We are continuing to work on a solution.

This incident has been resolved.

This incident has been resolved.

A solution to the Slurm scheduler issue has been found and implemented. The scheduler is now operating normally.

Thank you for your patience and understanding.

PLEASE SEE EMERGENCY MAINTENANCE NOTICE BELOW
Emergency maintenance Tuesday June 20th 7am-11am. Running jobs will be paused.

We are still working on finding the root cause of the scheduler slowness and timeouts. We are working with SchedMD and have sent diagnostic information for analysis.

At this time the scheduler is up but may become unresponsive to your commands at times. You can wait and retry them.

Jobs, once launched, should run as expected.

OOD/VDI are working, but job submission may also be affected.

If you receive salloc: error: Job submit/allocate failed: Invalid account or account/partition combination specified, waiting a moment and re-submitting your job again should result in a successful submission.

Addendum: It was determined that the issue is cyclical and you will have the best luck during odd hours (e.g. - after 1pm, before 2pm) and less success interfacing with the scheduler during even hours (e.g. - after 2pm, before 3pm).

We regret the impact this is having on your work. Updates will follow as we have them.

We are still working on finding the root cause of the slowness and are working with the vendor to troubleshoot.

At this time the scheduler is up but may become responsive to your commands at times. Jobs, once launched, should run as expected.

Slurm is still being overwhelmed with large numbers of requests. VDI timeouts/502 errors, interactive job connections, job submissions, are all impacted.

We are in contact with the Slurm developers to find a better resolution.

We have implemented updates and the scheduler appears stable and responsive.
We will continue to monitor and update this incident.

This incident has been resolved. FASSE and Cannon OOD are both available.

Cannon and FASSE OOD are not fully operational due to slurm being slow. With slurm slow, the apps wait too long to be launched and it can throw 502 errors

Cannon OOD is operational.

FASSE OOD is still experiencing issues and showing errors for new connections. Existing connections are working.
WIP

Login to fasselogin is working. Additional login nodes are not in the rotation and will be added back once they are healthy again. But normal login is working.