NAOJ GW Elog Logbook 3.2
Displaying report 1-1 of 1.
EleonoraCapocasa - 00:40, Saturday 18 July 2020 (2122)
Guardian deployed on TAMA DGS
Yamamoto-san, Aso-san, Yuhang, Eleonora
Thanks to Aso-san's help Guardian PC is now connected to the TAMA DGS network. We used a USB-> ethernet adaptor since the system was not recognizing the ethernet port.
Aso-san solved also a problem caused by the fact that space on the disk was completely occupied by log files generated by an error.
Then Yamamoto-san could remotely access the PC and set up the guardian. Below a memo of his work:
##################
1. Copy following applications from KAGRA to NAOJ k1grd0
- /kagra/apps/etc
- /kagra/apps/guardain
- /kagra/apps/epics
- /kagra/apps/pyepics
- /kagra/apps/cdsutils
- /kagra/apps/pcaspy
2. Set hostname info. in /etc/hosts on desktop1, standalone and k1grd0 in order to fix the too slow ssh connection.
192.168.11.110 desktop
192.168.11.100 standalone
192.168.11.103 k1grd0
3. Mount “standalone:/opt/rtcds” on k1grd0 by editing /etc/fstab
4. guardian service is relaunched after guardlog service is launched.
$ systemctl stop guardian
$ systemctl restart guardlog
$ systemctl start guardian
5. Operation checks
- guardctrl [create/start/stop/destroy] $(node_name) ### => Okey
- guardmedm $(node_name) ### => Okey. MEDM screen could be launched.
- guardlog $(node_name) ### => Okey. It is also available from MEDM screen.
##################
Today, we have some progress about guardian deployment in TAMA. Thanks to the help from Yamat. The detailed information can be found in the #filter_cavity channel of gokagra in Slack. Here, I put a summary of my activity today.
1. Yamat helped us check simulink file and found no problem.
2. Yamat suggested to run caget K1:FDS-FC_GR_TRA to check potential issue on client workstation of desktop1 and k1grd0. Running it on desktop1, I got -27.7212 for K1:FDS-FC_GR_TRA. But running it on k1grd0, I got channel connect timed out for K1:FDS-FC_GR_TRA.
3. Yamat suggested to check environment values in guardian computer. To do that, I used 'env > tama_filter_cavity_k1grd0_env_out.txt' to save the environment variable of k1grd0 workstation. Then I used 'scp tama_filter_cavity_k1grd0_env_out.txt controls@192.168.11.110:/home/controls/Desktop' to copy environment variables from k1grd0 workstation to desktop1 workstation. To share with Yamat on Slack, I firstly uploaded the txt file to dropbox and then share link with him. (Note that I didn't just take screenshot because the environment variable information is large.)
4. After Yamat checking env output, he found that a variable called 'EPICS_CA_ADDR_LIST' seems to have a wrong IP address. He suggested to change this from '/home/controls/.bashrc or /kagra/apps/etc/client-user-env.sh.' and reboot k1grd0.
5. I found the channel 'EPICS_CA_ADDR_LIST' is in /kagra/apps/etc/epics-user-env.sh. So I did the modification and reboot k1grd0. But the problem is not solved.
6. I found after modifying from /kagra/apps/etc/epics-user-env.sh, the env output in k1grd0 is still as before and didn't change. Maybe this is why the problem is not solved. Now I am waiting for the answer from Yamat.