User Tools

Site Tools


handover:aust72

This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
handover:aust72 [2014/12/17 09:02]
Warren Hankey
handover:aust72 [2014/12/17 22:07] (current)
cjordan
Line 1: Line 1:
 ====== AUST72 ====== ====== AUST72 ======
  
-Hobart 12m:+**Hobart 12m:**
  
-Disk VSN: HOB+1009/​16000/​1024+  * Disk VSN: HOB+1009/​16000/​1024 
 +  * Data volume at beginning: 5.4 TB
  
-Data volume at beginning5.4 GB+10:06UT - Had to switch to old version of e-RemoteCtrl as new version could not maintain ssh connection (Imogen)
  
-Katherine 12m:+**Katherine 12m:**
  
-Disk VSN: HOB+0075/​8000/​1024+  * Disk VSN: HOB+0075/​8000/​1024 
 +  * Data volume at beginning: 0 GB
  
 07:23UT - DBBC strangely restarted itself. ​ Logged back in, reconfigured and the problem is fixed for now (Imogen) 07:23UT - DBBC strangely restarted itself. ​ Logged back in, reconfigured and the problem is fixed for now (Imogen)
Line 17: Line 19:
 08:17UT - still trying to fix mark 5/DBBC/GPIB problem but nothing is responding due to poor internet connection. There was a power glitch and UPS connected to the DBBC and Mark 5 has died.  Martin is taking the DBBC, GPIB counters and Mark 5 off the UPS and connecting them to the mains, so if there is another power glitch, the DBBC, Mark 5 and GPIB counters will still be able to be restarted remotely. (Imogen) 08:17UT - still trying to fix mark 5/DBBC/GPIB problem but nothing is responding due to poor internet connection. There was a power glitch and UPS connected to the DBBC and Mark 5 has died.  Martin is taking the DBBC, GPIB counters and Mark 5 off the UPS and connecting them to the mains, so if there is another power glitch, the DBBC, Mark 5 and GPIB counters will still be able to be restarted remotely. (Imogen)
  
-Data volume at beginning0 GB+09:14 - Martin restarted UPS's. Mark 5 clock is still not synced, trying to fix the problem (Imogen)
  
-Yarragadee 12m:+09:35UT - ALARM: error st -999 systemclock connection error. Fixed with commands “antenna=operate” and “antenna=open”. ​ Mark5 was stuck with its record mode on (FHG_on), so ended the process and did another fmset. ​ This fixed the problem. (Imogen)
  
-Disk VSNHOB+0128/​32000/​1024+09:55UT - DBBC lost connection again - it seemed to restart, possibly another power glitch? ​ halted schedule while DBBC reconfigured. ​ Restarted schedule 09:59UT. (Imogen)
  
-Data volume at beginning: 0 GB+10:10UT - Alarm kept sounding for Mark5 apparently not being in sync, halted schedule, ran fmset, restarted schedule (Imogen) 
 + 
 +22:06UT - Volume of data recorded is 3.835 TB, which is about 900 GB behind schedule (Chris) 
 + 
 +**Yarragadee 12m:** 
 + 
 +  * Disk VSN: HOB+0128/​32000/​1024 
 +  * Data volume at beginning: 0 GB
  
 {{tag>}} {{tag>}}
/home/www/auscope/opswiki/data/attic/handover/aust72.1418806935.txt.gz · Last modified: 2014/12/17 09:02 by Warren Hankey