ARSC system downtime for pacman (all)

Menu to filter items by type

Contents for pacman

News Items

20 Jun 2013 Emergency Downtime

Start Time: 06/20/2013 -- 09:00
  End Time: 06/20/2013 -- 14:00
    Reason: The Pacman system vendor, Penguin Computing, has 
            issued a kernel update needing to be deployed on the 
            Pacman system as soon as possible to correct instability 
            issues affecting the pacman 4 core nodes.
            A reservation has been made on the system to keep jobs 
            queued with walltimes extending beyond Thursday at 9am.  
            User jobs running past Thursday at 9am will be killed 
            at that time. 

18 May 2013 Scheduled Downtime

Start Time: 05/18/2013 -- 12:00
  End Time: 05/30/2013 -- 12:00
    Reason: University FAST power outage and OS upgrade to
            RHEL 6.4. Default modules will be updated.
            *** Recompiling of user code required. ***
            If users wish to recompile your pacman code in 
            the RHEL 6.4 environment prior to the May 18th 
            scheduled downtime, please log onto pacman14.arsc.edu 
            and recompile using the software available via 
            modules and /usr/local/pkg.  If users would like to 
            submit batch jobs in the RHEL 6.4 environment prior 
            to the scheduled downtime, please contact the ARSC Help Desk.

            *** Update on May 24, 2013 ***
            The OS upgrade is taking longer than first anticipated.
            Therefore, the pacman.arsc.edu scheduled downtime has 
            been extended through May 30th.
            Files on $CENTER and $ARCHIVE are accessible via logins
            to fish.arsc.edu.
            Files on $HOME are available via the linux workstations
            on /pachome/$HOME.  The names of the linux workstations are
            available on 
            http://www.arsc.edu/arsc/resources/linuxws/index.xml

20 Apr 2013 Scheduled Downtime

Start Time: 04/20/2013 -- 11:00
  End Time: 04/20/2013 -- 12:35
    Reason: Due to a network outage, many 4 core nodes were rebooted.