The IMC_LOCK and ITMX SUS and SEI guardain nodes are running the new guardian and cdsutils release candidates. All upgraded nodes have been test driven and appear to be functioning nominally.
The current guardian/cdsutils release candiates are:
The following nodes are running the above versions:
This has been accomplished by creating the following file in the node run directories on h1guardian0:
controls@h1guardian0:~ 0$ cat /etc/guardian/nodes/SUS_ITMX/local-env export PATH=/bin:/usr/bin export LD_LIBRARY_PATH= export PYTHONPATH= . /ligo/apps/linux-x86_64/epics/etc/epics-user-env.sh . /ligo/apps/linux-x86_64/nds2-client/etc/nds2-client-user-env.sh || true . /ligo/apps/linux-x86_64/cdsutils-434/etc/cdsutils-user-env.sh . /ligo/apps/linux-x86_64/guardian-1344/etc/guardian-user-env.sh ifo='ls /ligo/cdscfg/ifo' site='ls /ligo/cdscfg/site' export IFO=${ifo^^*} export NDSSERVER=${ifo}nds0:8088,${ifo}nds1:8088 controls@h1guardian0:nodes 0$ cat /etc/guardian/nodes/SUS_ITMX/run #!/bin/bash set -e exec 2>&1 if [ -e local-env ] ; then . local-env elif [ -e /etc/guardian/local-env ] ; then . /etc/guardian/local-env fi exec chpst -e env guardian $(cat guardian) "$@" controls@h1guardian0:~ 0$
The nodes were then restarted with guardctrl as normal:
controls@h1guardian0:~ 0$ guardctrl restart SUS_ITMX
The local-env files can be removed, and the nodes will be restarted to their pre-upgrade versions (guardian: r1102, cdsutils: r366).
I will proceed with a full system upgrade first thing in the morning.