User Tools

Site Tools


operations:agenda2019_05_30

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

This is an old revision of the document!


Chair: Momtaz

Attended:

Apologies:

Absent:

General Issues

  • Please remember to create handover note page during setup.
  • End message, if problem exists, please mention/describe the error.
  • In handover and end messages, include list of missed scans.

Handover Issues

R4896:

Katherine 12m

  • FS crashed. Missed scans 150-2052 - 150-2126 (mas)
  • Alarm scan check reports Mark5 data format problem (indicated by the letter “E” at the end of the line)(mas)
  • FS terminated itself. Restarted @ 0633, first good data @0640. No useful data 0618-0640 (JMc)

Yarragadee 12m

  • Excluded due to technical problem

R1897:

Katherine 12m

  • Proc file does not seem to have been generated properly, this is causing issues noticeable in the test recording (Tiege).
  • Proc issue due to a typo in skedf.ctl (DNNC rather than DBBC). skedf.ctl may not be applied until after a restart of the FS. (JMc)

Yarragadee 12m

  • I encountered the error TPI Overflow. This froze up the pointing check, not letting it progress any further. It was fixed by again restarting and resyncing the DBBC software. Not sure if just a one off quirk, but noting it down just in-case. This was all prior to schedule start so no data is affected. (Tiege)
  • Also, drive information on system monitor for Yg seems to be completely broken. The message box is showing many Monica issues. Have tried restarting both Rxmon and Monica as a whole. This has not fixed it. Telescope appears to be working correctly, I may just need to restart a specific part of Monica that I do not know. (Tiege)
  • Drive info restored after restarting the antmon program [/etc/init.dMonica.antmon stop && /etc/init.dMonica.antmon start as root] (JMc)

OHG119:

Hobart 26m

  • Experiment started one scan late due to drive issues(Lucas).
  • Drives crashed. Diagnostic: persistent missed scan alarms and #antcn# alarms (including cannot allocate memory). Fix appears to be “rem_reboot -r rakbus sys26m”, ping sys26m until it comes back up then resume schedule. This also requires that you “sudo /etc/init.d/sqlmonitor restart”. All on newsmerd (Lucas)
  • Terminated FS @ 0244 to fix GPIB comms issue. Restarted ~0400 (JMc)
  • Schedule was put on halt because of bad wind condition(Jay)

Yarragadee 12m

  • Windstow at Yarragdee (JMc)
  • rfpic not answering. disabled in preob to avoid timeout delays (JMc).

R4897:

Yarragadee 12m

  • ALARM: Automatic wind stow activated, due to heavy rain and wind (Momtaz).
  • 23:38UT False wind stow alarm from log monitor as it first opened log file-“2019.157.23:38:41. ALARM Automatic wind stow activated” this line not found in log file(Warren)

R1898:

Katherine 12m

  • Tsys negative values (~-200 to ~-100)? (Lim).
  • “No space left on device”. Warren deleted some old files on pcfske(Lim).
  • ALARM: error m5 -104 mk5cn: time-out, connection closed. Failed to open terminal from within the pcfs(Lim).
  • Can't open display in pcfske: “Client is not authorized to connect to Servergv” and “Client is not authorized to connect to serverxterm Xt” (Lim).
  • ALARM: error m5 -900 : not while recording or playing(Jay).

Yarragadee 12m

  • Received consistent error error being ignored: error sp -4 unrecognized name (not a function or procedure) after each scan(mas)
/home/www/auscope/opswiki/data/attic/operations/agenda2019_05_30.1560387581.txt.gz · Last modified: 2019/06/13 00:59 by Md. Momtazur Rahman