User Tools
operations:backup_control
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 | ||
|
operations:backup_control [2014/10/22 03:51] David Horsley [Usage] |
operations:backup_control [2014/11/22 02:31] (current) David Horsley [Quirks] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Backup control system ====== | ====== Backup control system ====== | ||
| - | Occasionally, especially for Yg, eRc can refuse to connect or frequently drop out. The VNC session can also suffer some problems, is quite heavy on the network, and doesn't allow copy-paste. As an alternative, there is a text based backup control setup installed on the field system PCs. | + | Occasionally, especially for Yg, eRc can refuse to connect or frequently drop out. The VNC session can also suffer some problems, has quite a heavy network load, and doesn't allow copy-paste. The field system ships with a suite of tools to allow it to be access from a terminal, so as an alternative to eRc and VNC, a 'tmux' layout has been created to present these tools in a convenient manner. As this is purely text based and amenable to compression over ssh, it is very light on network usage. |
| ====== Usage ====== | ====== Usage ====== | ||
| Line 10: | Line 10: | ||
| This will present you with a a terminal window similar with a similar layout to e-RemoteCtrl. | This will present you with a a terminal window similar with a similar layout to e-RemoteCtrl. | ||
| - | To get the alarm system working, you need to stream the log files to ops2, or the PC with the log monitor. This can be done with ssh and tail, but there is a shell script on ops2 which does this for you. **To transfer the current log file** from pcfsyg to ops2 run: | + | To get the alarm system working, you need to stream the log files to ops2, or the PC with the log monitor. This can be done with ssh and tail, but there is a shell script on ops2 which does this for you. |
| - | <note important> | + | <note> |
| - | **To transfer the current log file** | + | **To stream the current log file** |
| - | On ops2 run (eg.) | + | On ops2 run |
| * ''~/stream_log yg'' | * ''~/stream_log yg'' | ||
| + | |||
| + | **You will need to rerun this when the log file changes.** | ||
| </note> | </note> | ||
| - | You can then point the log monitor to the file indicated by the script. **Note: you will need to rerun this when the log file changes** | + | You can then point the log monitor to the file indicated by the script. |
| By default, the cursor should be in the ''oprin'' pane at the bottom of the window. If it isn't, you can change active panes by pressing "Ctrl+b" then an arrow key. The ''oprin'' window is the same program that runs in the VNC, so tab-completion and up-arrows should work as expected. | By default, the cursor should be in the ''oprin'' pane at the bottom of the window. If it isn't, you can change active panes by pressing "Ctrl+b" then an arrow key. The ''oprin'' window is the same program that runs in the VNC, so tab-completion and up-arrows should work as expected. | ||
| ====== Quirks ====== | ====== Quirks ====== | ||
| - | As the script is very simple, there are a few quirks. Importantly, the log in the central pane will not update when the fs log is changes. You can either kill the session and restart it (see below), or highlight the central pane using Ctrl+b and the arrow keys, Ctrl+c to kill the tail, the running the tail program again by pressing up and enter. | + | As the script is very simple, there are a few quirks. Importantly, the log in the central pane will not update when the fs log is changes. |
| - | The control setup runs in a tmux session, so it is persistent across window closes and disconnects. This means simply closing and reopening it will not reset the setup. | + | You may also find the session in funny states if someone opens it in a small window, or if fs has been terminated. The control setup runs in a tmux session, so it is persistent across window closes and disconnects. This means simply closing and reopening it will not reset the setup. |
| - | Instead reset the session with | + | |
| - | <note important> | + | The easiest way to fix these is to kill the session and restart it. |
| + | |||
| + | <note> | ||
| ** To reset the session:** | ** To reset the session:** | ||
| * press Ctrl+b and type '':kill-session'' | * press Ctrl+b and type '':kill-session'' | ||
| Line 34: | Line 37: | ||
| </note> | </note> | ||
| - | You may also find the session in funny states if someone opens it in a small window, or if fs has been terminated. | + | |
/home/www/auscope/opswiki/data/attic/operations/backup_control.1413949861.txt.gz · Last modified: 2014/10/22 03:51 by David Horsley
Page Tools
