Messages & Announcements

  • 2019-02-11:  Anvil: Unplanned downtime resolved
    Category:  System Failure

    The CEPH storage system for Anvil is functioning again and Anvil is available for use. Please check your VM instances to ensure they are operating correctly and contact hcc-support@unl.edu if you have further questions.


  • 2019-02-11:  Anvil: Unplanned downtime due to issue with storage system
    Category:  System Failure

    The CEPH storage system for Anvil is currently experiencing problems. Expect VMs hosted on Anvil to be slow or unresponsive until the problem is resolved.


    The CEPH storage system for Anvil is currently experiencing problems. Expect VMs hosted on Anvil to be slow or unresponsive until the problem is resolved.

  • 2019-02-08:  Crane: JupyterHub maintenance complete
    Category:  General Announcement

    The JupyterHub service maintenance is complete. Please contact us at hcc-support@unl.edu if you have any questions or issues.


  • 2019-02-08:  Crane: JupyterHub maintenance Friday, February 8 @ 4pm
    Category:  Maintenance

    The JupyterHub service will be unavailable starting at 4pm tomorrow, February 8th. This maintenance is to apply configuration changes to the service, and is expected to last no longer than 30 minutes. Running notebooks may be terminated as part of this maintenance. Users are encouraged to stop their notebooks ahead of time gracefully by selecting "Control Panel" then "Stop My Server" in the notebook interface.

    Please contact hcc-support@unl.edu with any questions or issues regarding this maintenance.


  • 2019-02-04:  Crane: system is available for use, /work filesystem checks ongoing
    Category:  General Announcement

    Checks on the storage server's filesystem targets were completed this morning. The results of the scan for one of the filesystem targets requires us to make a full consistency scan of Crane's /work filesystem. This process can be done concurrently while /work is being used by jobs.

    Please check the status of your jobs if they were running at the time of the failure. These jobs may have experienced I/O errors if they were utilizing files that were backed by this storage server's filesystem targets.


Pages