Access Manager 4.0.1, Access Gateway Appliance failed installation

0 Likes
over 6 years ago
There is a bug in the installation script which can cause some gateways to not install the NetIQ software on the SLES Access Gateway Appliance.

After the SLES installation the script calls on:

ma-config

which is:

case "$1" in
start)
echo "Starting MAGAppliance Configuration Script ......" > /var/log/ma-config.log
/tmp/ma-os-config.sh 2>&1 /dev/null
location_val=`find /tmp/ -name NAM-magappliance*`
location_val=`echo $location_val | cut -d ' ' -f 1`
$location_val/ma_install.sh 2>&1 /dev/null
;;
stop)
echo "Stopping TcpServer " >> /var/log/sbox-config.log
#`perl /root/tcpserver.pl`
;;
*)
echo $"Usage: $0 {start|stop}"
exit 1
esac
exec 1>/dev/null
chkconfig --del ma-config
exit $?


The scripts fails intermittently with:

./ma-config: line 27: /tmp/NAM-magappliance.tar.gz/ma_install.sh: Not a directory


The reason why it fails, it because of the:

find /tmp/ -name NAM-magappliance*


Which produces two results:

/tmp/NAM-magappliance.tar.gz
/tmp/NAM-magappliance-4.0.1-88


The right path is: /tmp/NAM-magappliance-4.0.1-88

the find uses the first result, and in some installations the order is:

/tmp/NAM-magappliance.tar.gz
/tmp/NAM-magappliance-4.0.1-88


or

/tmp/NAM-magappliance-4.0.1-88
/tmp/NAM-magappliance.tar.gz


If the tar.gz is first the installation fails.

The ma-config should be modified to use:

location_val=`find /tmp/ -name NAM-magappliance-*`


Which would find the directory as a single value.

The work around is to correct that value or to run ma_install.sh manually.

 

Labels:

How To-Best Practice
Comment List
Anonymous
Related Discussions
Recommended