User Tools
operations:starting_monitoring_9.10.5
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.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
operations:starting_monitoring_9.10.5 [2016/02/25 00:15] Jamie McCallum [FS time is out by minutes, hours, months or years!] |
operations:starting_monitoring_9.10.5 [2016/11/24 21:11] Bryn Emptage [Antenna control and monitoring] |
||
|---|---|---|---|
| Line 38: | Line 38: | ||
| 2012.297.03:58:54.01?ERROR st -5 Error return from antenna, see Mbus error. | 2012.297.03:58:54.01?ERROR st -5 Error return from antenna, see Mbus error. | ||
| </code> and you'll need to re-establish the connection by typing: <code>antenna=open (this re-opens the connection) | </code> and you'll need to re-establish the connection by typing: <code>antenna=open (this re-opens the connection) | ||
| - | antenna=status (if the connection has re-established, you will see several lines of status messages)</code> | + | antenna=status (if the connection has re-established, you will see several lines of status messages)</code> If it still doesn't work, from a terminal <code>ping syshb</code>. If syshb is not "pingable" it might be a communication issue, contact the on call person and tell them. |
| - We occasionally get an alarm from the mark5 like this: <code>2012.312.18:08:21.42?ERROR m5 -900 Probably no such disk | - We occasionally get an alarm from the mark5 like this: <code>2012.312.18:08:21.42?ERROR m5 -900 Probably no such disk | ||
| 2012.312.18:08:21.42?ERROR m5 -904 MARK5 return code 4: error encountered (during attempt to execute) | 2012.312.18:08:21.42?ERROR m5 -904 MARK5 return code 4: error encountered (during attempt to execute) | ||
| Line 123: | Line 123: | ||
| </code> | </code> | ||
| - | ==== "rfpic" problem ==== | + | ==== "rfpic" or rfpcn problem ==== |
| If you receive a persistent "//rfpcn: error opening, rfpic probably not running, see above for error//" report, or notice that the recording is notably behind the summary file and the becklog grows, you might want to restart Rxmon. | If you receive a persistent "//rfpcn: error opening, rfpic probably not running, see above for error//" report, or notice that the recording is notably behind the summary file and the becklog grows, you might want to restart Rxmon. | ||
| Line 284: | Line 284: | ||
| The time or date in the field system log output is very wrong, but all the time settings appear OK, that is; the FS time in fmset is correct, the pcfs[hb][ke][yg] date command reports the correct time etc. | The time or date in the field system log output is very wrong, but all the time settings appear OK, that is; the FS time in fmset is correct, the pcfs[hb][ke][yg] date command reports the correct time etc. | ||
| - | The problem is the field system actually uses the hardware BIOS time from the pcfs[hb][ke][yg] computer, not the operating system time. If all the times appear OK but the field system is still incorrect then you will need to fix the hardware BIOS time setting. To read the hardware time; <code>hwclock -r</code> The system time comes from a local GPS receiver which runs an NTP server. Check that the pcfs[hb][ke][yg] system time is indeed correct, the offset from the first server in the list should be less than 10 ms; <code>ntpd -nq</code> | + | The problem is the field system actually uses the hardware BIOS time from the pcfs[hb][ke][yg] computer, not the operating system time. If all the times appear OK but the field system is still incorrect then you will need to fix the hardware BIOS time setting. To read the hardware time, (and the difference from the system time), as root user; <code>hwclock -r</code> The system time comes from a local GPS receiver which runs an NTP server. Check that the pcfs[hb][ke][yg] system time is indeed correct; <code>ntpd -nq</code> |
| - | Then write the current system time to the hardware clock. <code>hwclock -w</code> | + | The offset from the first server in the list should be less than 10 ms. |
| + | Then write the current system time to the hardware clock, as root user; <code>hwclock -w</code> | ||
| + | That the hardware clock has gone wrong probably indicates a fault, such as a bad BIOS battery on the motherboard that needs replacing. | ||
/home/www/auscope/opswiki/data/pages/operations/starting_monitoring_9.10.5.txt · Last modified: 2017/06/23 03:24 by Arwin Kahlon
Page Tools
