Changes between Version 24 and Version 25 of HetProcedures/RA/TCS
- Timestamp:
- May 12, 2023 5:57:17 PM (12 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HetProcedures/RA/TCS
v24 v25 45 45 46 46 2. Second, restart the HPF TCS relay: 47 * run {{{tcsrelay}}} command in gnome terminal where you have run "ssh -X hpf@hpf". (Be sure you have closed any rasession windows first).48 * confirm that you are in the correct windows. You should see messages like in the picturebelow. (if window is not the right one use 'Ctrl-a n' or 'Ctrl-a p' to find it)47 * open a new terminal, log in to hpf (e.g., {{{ssh hpf@hpf}}} and run {{{tcsrelay}}} 48 * confirm that you are seeing the correct screen - you should see messages like the text and screenshot below. (if window is not the right one use 'Ctrl-a n' or 'Ctrl-a p' to find it) 49 49 50 ''2023-05-11 20:21:54.181838 : Relayed 22160000 messages''50 ''2023-05-11 20:21:54.181838 : Relayed 22160000 messages'' 51 51 52 [[Image(hpf_tcs_relay.jpg, 300px)]] 53 52 [[Image(hpf_tcs_relay.jpg, 300px)]] 54 53 55 54 * CTRL-C the script running there (this is a script, not a TIMS client). You will need to CTRL-C twice (It took 3x for me once -SJ) to actually kill it. 56 55 * Restart the script (up arrow or {{{./bashwrapperfor_HETTCSRebroadcast.sh}}}) 56 * After that you can detach from this screen with ctrl-A D 57 57 58 3. Restart the TIMS HET Client . Two options:58 3. Restart the TIMS HET Client once more to be safe. Two options: 59 59 * During OPS, use the OPS web page to click "TCS Client Restart" 60 60 * OR, on in the "Scripts" screen session, run: {{{tims het shutdown}}}, and then in the HPF HET Client screen session, run: {{{timshet}}}