I'm hoping to get a proper install this week done, but for now, this a stop gap.
To start diagnostic test tools, go to rosalba. (Either sit at it, or ssh -X rosalba).
cd /opt/apps
type "bash", this starts a bash shell
source gds-env.bash
diaggui
--------- Debugging section ------
If that throws up errors, try looking with "diag -i" and see if there's a line that starts with nds. In the case last night, Alex had not setup a diagconf configuration file in the /etc/xinetd.d directory, which setups up the diagconf service under the xinit service. To restart that service (if for example the nds line doesn't show up), go to /etc/init.d/ and type "sudo xinit start" (or restart).
Other problems can include awg and/or tpman not running for a particular model on the front end machine. I.e. diag -i should show 3 results from 192.168.113.85 (c1x02, c1sus, c1mcs) at the moment , for both awg and tp. If not, that means awg and tpman need to be restarted for those.
These can be started manually by going to the front end, to the /opt/rtcds/caltech/c1/target/gds/bin/ directory, and running awgtpman -s sysname (or in the case of IOP files [c1x02, c1x03, etc], awgtpman -s sysname -4. Better is probably to run the start scripts which live /opt/rtcds/caltech/c1/scripts/ which kills and restarts all the process for you.
|