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 01:04] 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. |