my.osc.edu outbound email outage
There is an issue with my.osc.edu sending outbound emails, including the 'Forgot Password' emails.
There is ongoing work to resolve this issue as soon as possible.
Contact OSC Help if there are any questions.
Login Problems
Client Portal: Intermittent Outages
We are experiencing infrastructure issue on the servers that host the Client Portal (my.osc.edu).
Outages are intermittent.
We apologize for the inconvenience.
Please contact OSCHelp@osc.edu with any questions.
All HPC systems are available
8/24/16 3:57PM: All HPC systems are availalbe including:
- Oakley cluster for general access
- Ruby cluster for restricted access
- Owens cluster for early users
- Home directory and scratch file systems
- OnDemand and other web portals
- Project file system (/fs/project)
All jobs held before downtime have been released by the batch scheduler. If your jobs are still held or you have any questions, please contact oschelp@osc.edu
Some issues remain after downtime
15 July 2016, 5:00PM update: some additional issues we are facing
- We are experiencing periodic hangs of the GPFS client file system software used with the new storage environment. We have an open support case with the vendor, but no solution at this time. This may affect access to the /fs/project, and /fs/scratch file systems. Reports of transfer failures to these file systems through scp.osc.edu, and sftp.osc.edu have been reported.
-
Symlinks transfered from /nfs/gpfs to /fs/project are lost(fixed)
June 7th downtime to finish at 6:30PM
Update: Downtime completed at 6:30PM, June 7th.
The June 7th downtime is now slated to be completed at 6:30PM. Previous estimate was 5PM.
All systems and services will continue to be unavailable until that time.
Thank you for your cooperation.
Oakley Login Node Issues
Currently users connecting via SSH to Oakley may recieve "connection refused" or "connection failed" errors if they were not logged in before this occurred. Glenn is currently functioning normally, and users may also attempt to connect to one of the Oakley nodes specifically, by pointing their SSH client to either "oakley01.osc.edu" or "oakley02.osc.edu". This has had some success in our testing. More updates will be forthcoming.
