User Tools

Site Tools


handover:r1784

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
handover:r1784 [2017/03/21 05:34]
Jesse Swan
handover:r1784 [2017/03/21 08:39] (current)
Jesse Swan
Line 20: Line 20:
    * The original power outage flattened the CMOS battery, requiring the hwclock procedure to correct it (JMc).    * The original power outage flattened the CMOS battery, requiring the hwclock procedure to correct it (JMc).
    * After rebooting, the machine apparently stayed off the network for about an hour. It was firstthought that this was due to the fsck check of the drives, but was actually a network problem. The symptoms were a lack of access via ping, ssh or VNC when attempting to connect from either the campus machines (ops8) or Mt. Pleasant. pings and ssh connections from mk5ke were fine though. Problem finally resolved with a reboot of pcfske, after logging in through mk5ke (JMc)    * After rebooting, the machine apparently stayed off the network for about an hour. It was firstthought that this was due to the fsck check of the drives, but was actually a network problem. The symptoms were a lack of access via ping, ssh or VNC when attempting to connect from either the campus machines (ops8) or Mt. Pleasant. pings and ssh connections from mk5ke were fine though. Problem finally resolved with a reboot of pcfske, after logging in through mk5ke (JMc)
 +
  
  
Line 29: Line 30:
  
    * 1700UT Experiment started OK (Tiege)    * 1700UT Experiment started OK (Tiege)
 +   * 0700UT Alarm cannot connect to pcfs, check vnc. Fs still running but with error along the lines of “wrong length written, file probably too large can't write to disk.” Fixed as per wiki by 07:08UT
  
  
/home/www/auscope/opswiki/data/pages/handover/r1784.txt · Last modified: 2017/03/21 08:39 by Jesse Swan