From time to time there might be problems with the batch farm. Machines hang, ore do not see a directory anymore.
To test which machines are affected, this script can be used. It will connect via ssh to each machine and execute the following command:
command='if [ -x '$EXECUTABLE' ] ; then echo -n executable found; \
if [ -d '$DIRECTORY' ] ; then echo -n " data dir found"; if [ -d $LIBDIR ]; \
then echo -n $HOSTNAME "">> hosts.sh; echo " library dir found"; \
else echo " ko"; echo HOSTNAME >> hosts_problem.sh; fi; else echo " ko"; \
echo $HOSTNAME >> hosts_problem.sh; fi; \
else echo $HOSTNAME >> hosts_problem.sh; fi'
The script takes four parameters:
- Name of the batchqueu to use,
- name of an executable (including location),
- name of a directory with datafiles,
- name of a directory with libraries used by the executable.
If you never have connected via ssh to the batch machines, you will have to type "yes" a couple of times.
The result will be two files named hosts.sh and hosts_problem.sh containing one definition of a environmentvariable containing all hostnames, that are found to be ok (hosts.sh) and those which are unable to se one of the required directories (hosts_problem.sh).
If you had to type your password for an machine and it shows up in hosts_problem.sh, this means that the machine does not see your homedirectory. Otherwise it does not accept ssh connections at the moment.
Sending this report to the DVEE department experts, will help them to find out which machines are corrupted and need a reboot.
- 20 Jul 2004