Probably caused by a DMF dependency. DMF was being upgraded at the time.
The persistent filesystem has been remounted on the protocol nodes, Windows drives and datasets are available. The Nix head node has been fixed, and all Nix clients have been restarted and tested. It seems Slurm jobs were unaffected as the filesystem remained available on the compute nodes.
It has been reinstated and is now available on the login nodes. Compute and protocol nodes being checked. Nix will need restarting
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6020 services available
Integrations with