activepastactivepastactivepastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastactivepastactivepastactivepastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpastexpiredpast

ARSC system downtime for fish (past)

Menu to filter items by type

Type Downtime News
Machine All Systems linuxws pacman bigdipper fish lsi
Downtime All Future Current Past

Contents for fish

News Items

06 Oct 2014 Unscheduled Downtime

Last Updated: Mon, 06 Oct 2014 -
Machines: linuxws pacman fish
Start Time: 10/06/2014 -- 11:20
  End Time: 10/06/2014 -- 12:00
    Reason: $CENTER Infiniband switch lost power due to a loose power cable.  The
            switch was powered back on after power was restored.  Users with jobs 
            running on both fish and pacman during the time of the power outage
            will be notified.

17 Sep 2014 Unscheduled Downtime

Last Updated: Wed, 17 Sep 2014 -
Machines: fish
Start Time: 09/17/2014 -- 04:30
  End Time: 09/17/2014 -- 09:55
    Reason: Management node lost communication with the system.  System reboot 
            required.  Users with lost jobs were notified.

28 Aug 2014 UnScheduled Downtime

Last Updated: Fri, 29 Aug 2014 -
Machines: fish
Start Time: 08/28/2014 -- 14:43
  End Time: 08/28/2014 -- 17:35
    Reason: Storage controller rebooted unexpectedly. As a result, the fish.arsc.edu
            system needed to be rebooted in order to restore normal system operations.
            All user jobs running at the time were killed.  A case has been opened with
            the vendor to identify the cause and prevent the issue from reoccurring in
            the future.


Back to Top