User Tools

Site Tools


operations:agenda2018_05_17

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
Next revision Both sides next revision
operations:agenda2018_05_17 [2018/05/17 01:35]
Noor Md Said
operations:agenda2018_05_17 [2018/05/17 01:37]
Noor Md Said
Line 1: Line 1:
 __CRDS95__ __CRDS95__
  
-Katherine 12m+__Katherine 12m__
  
 •Patrick need to swapped out the module due to bad disk, received an alarm error (m5-104 mk5cn: time-out, connection closed), tried to restart the mk5 in between scans but didn’t fix the error. The error is due to a faulty disk in the module (shows up in get_stats procedure), which causing writes to disk to be slower than usual. Have asked Mick to swap to a good module in the morning. ​ •Patrick need to swapped out the module due to bad disk, received an alarm error (m5-104 mk5cn: time-out, connection closed), tried to restart the mk5 in between scans but didn’t fix the error. The error is due to a faulty disk in the module (shows up in get_stats procedure), which causing writes to disk to be slower than usual. Have asked Mick to swap to a good module in the morning. ​
Line 12: Line 12:
 __R1841__ __R1841__
  
-Yarragadee 12m+__Yarragadee 12m__
  
 •Katie received “ALARM: error m5-104 mk5cn: time-out, connection close” continuously. Had called Mick and he said only 1 light was on for the drives. Looks like mk5 crashes and had to reboot it. •Katie received “ALARM: error m5-104 mk5cn: time-out, connection close” continuously. Had called Mick and he said only 1 light was on for the drives. Looks like mk5 crashes and had to reboot it.
Line 21: Line 21:
 __AUA043__ __AUA043__
  
-Hobart 26m+__Hobart 26m__
  
 •Lucas noticed that the disk position has been drifting very quickly, 360 GBs in 4.5 hours, aka 80GB/​hour. ​ •Lucas noticed that the disk position has been drifting very quickly, 360 GBs in 4.5 hours, aka 80GB/​hour. ​
Line 28: Line 28:
  
  
-Katherine 12m+__Katherine 12m__ 
 •Lucas noticed that the disk position has been drifting, 25 GBs in 4.5 hours, aka5.5GB/​hour (Lucas). •Lucas noticed that the disk position has been drifting, 25 GBs in 4.5 hours, aka5.5GB/​hour (Lucas).
  
Line 34: Line 35:
  
  
-Yarragadee 12m+__Yarragadee 12m__
  
 •Lucas received constant onsource slewing errors, and it seems like Yarragadee is late to source quite often. The disk position has been drifting very quickly, 100 GBs in 4.5 hours, aka 22GB/hour. •Lucas received constant onsource slewing errors, and it seems like Yarragadee is late to source quite often. The disk position has been drifting very quickly, 100 GBs in 4.5 hours, aka 22GB/hour.
Line 41: Line 42:
 __R4841__ __R4841__
  
-Katherine 12m+__Katherine 12m__
  
 •Warren noticed large delay and reconfigure DBBC •Warren noticed large delay and reconfigure DBBC
Line 50: Line 51:
 __R1842__ __R1842__
  
-Katherine 12m+__Katherine 12m__
  
 •Jamie halted the schedule to restart DBBC. Clkoff had been slipping and passed the threshold. Several data were affected by delay jumps. ​ •Jamie halted the schedule to restart DBBC. Clkoff had been slipping and passed the threshold. Several data were affected by delay jumps. ​
  
  
/home/www/auscope/opswiki/data/pages/operations/agenda2018_05_17.txt · Last modified: 2018/05/17 03:22 by Noor Md Said