User Tools

Site Tools


operations:agenda2017_11_23

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
operations:agenda2017_11_23 [2017/11/23 02:47]
Arwin Kahlon
operations:agenda2017_11_23 [2017/11/23 03:01] (current)
Arwin Kahlon
Line 27: Line 27:
   * aov018: Eremote control not connected, in such cases start the experiment using the VNC to relevant pcfs computer. To get alarms you'll need to open a terminal on ops8 and type example ''​./​stream_log hb'',​ repeat for any other stations needed (dont close the terminal). In the log monitor select file '/​tmp/​hb.log'​ or equivalent station, as usual run '​cloff'​ before reading the file in the log monitor.   * aov018: Eremote control not connected, in such cases start the experiment using the VNC to relevant pcfs computer. To get alarms you'll need to open a terminal on ops8 and type example ''​./​stream_log hb'',​ repeat for any other stations needed (dont close the terminal). In the log monitor select file '/​tmp/​hb.log'​ or equivalent station, as usual run '​cloff'​ before reading the file in the log monitor.
   * r1819: YG error m5 -104 mk5cn: time-out, connection closed. antenna=operate and antenna=open fixed it.    * r1819: YG error m5 -104 mk5cn: time-out, connection closed. antenna=operate and antenna=open fixed it. 
-  * Most likely a network issue or bad drives in the module? Monitor mk5 get_stats and make sure there are no other apparent issues. ''​checkmk5''​ can only be called once the recording has stopped.+               Most likely a network issue or bad drives in the module? Monitor mk5 get_stats and make sure there are no other apparent issues. ''​checkmk5''​ can only be called once the recording has stopped.
   * r1819: Ke drives issues, needed a power reset on site : “Turned the main switch off for 20 secs then back on. The emergency reset light was blinking and after the turn off/on the light stopped blinking.” He mentioned there were some power surges earlier on in the night, and suggested that the power may have gone off and on multiple times during the evening. ​   * r1819: Ke drives issues, needed a power reset on site : “Turned the main switch off for 20 secs then back on. The emergency reset light was blinking and after the turn off/on the light stopped blinking.” He mentioned there were some power surges earlier on in the night, and suggested that the power may have gone off and on multiple times during the evening. ​
   * r4819: Ke had issues with drives and erc having the wrong time : Needed to run '​hwclock -w' again to change hardware clock, then disable fscking on reboot by editing '/​etc/​fstab'​ as root and changing the last number on the line /dev/md0 to 0 (instead of 1), then rebooting the pcfske. Now ERC and fs have the correct time.   * r4819: Ke had issues with drives and erc having the wrong time : Needed to run '​hwclock -w' again to change hardware clock, then disable fscking on reboot by editing '/​etc/​fstab'​ as root and changing the last number on the line /dev/md0 to 0 (instead of 1), then rebooting the pcfske. Now ERC and fs have the correct time.
/home/www/auscope/opswiki/data/pages/operations/agenda2017_11_23.txt · Last modified: 2017/11/23 03:01 by Arwin Kahlon