Special Weapons!

If you're in a Unix environment and hate having to check SystemOut.logs in multiple locations-  Did you know you can get around that with a little scripting and taking advantage of ssh.   The way it works it you use a private key to allow your script to authenticate and run a script on the node.   This way you can just run a script to tail or grep for what you want to see and hit all the servers from a single machine. 

 

I had to write this as part of a monitoring subsystem for another customer.   Though this would be handy for almost anything repetitive in a multinode environment.   So here is the snippet.

 

 userHost=( user@host05 user2@host01 )

 exitCode=0

# Location of the News SysOut logs.
newsSysOutDir=/local/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/clusterLC_server1

# Name of the monitor script
mon_script=SO_Mon.sh
 

# Test SSH access
for var in "${userHost[@]}"
do
  echo "Directory listing for $var"
  ssh -oBatchMode=yes -n $var "ls -l $newsSysOutDir"

    if [ $? != 0 ]; then
     exitCode= $?   
     echo "SSH access is not configured"
        ssh-keygen -t rsa
     cat ~/.ssh/id_rsa.pub | ssh $var "chmod g-w ~/; mkdir -p .ssh; chmod 700 .ssh; cat - >> .ssh/authorized_keys2"
     
     echo "Configured SSH private key for $var.  You will need to try again"   
    fi

done
if [ $exitCode != 0 ]; then
    exit $exitCode
fi

 

 

 

 

# Upload the monitor scripts
if [ -z $isScheduledRun];then

echo "Uploading the monitor script"

for var in "${userHost[@]}"
do
 scp $runDir/$mon_script $var:$newsSysOutDir/$mon_script
 if [ $? != 0 ]; then
   echo "Upload of monitor script failed"
   exit 1
 fi

done   
fi

 

 

 # Run the SystemOut.log monitor
for var in "${userHost[@]}"
do
  # This is configured to work with sendEmail
  ssh -oBatchMode=yes -n $var "$newsSysOutDir/$mon_script sendEmail wtfmail02.lotus.com michael_lee@us.ibm.com $newsSysOutDir "
done
echo "Kicked off the monitors"

 

 

# You can obviously run something here now to clean up the script .