|Applies To||Authentication Manager 7.1|
|Issue||AM 7.1 - Solaris Install hanging (error code = 601; message="Failure executing /usr/local/RSASecurity/RSAAuthenticationManager/config/configUtil.sh, return code=1")|
Even though the install is failing on configUtil.sh, no config.out is generated. It also takes over 1/2 hour to generate the hang when it fails which is an longer than usual period of time to reach that portion of the installation. The installation log reveals only:
Install, com.rsa.am.install.actions.product.RSAExecAction, err, ProductException: (error code = 601; message="Failure executing /usr/local/RSASecurity/RSAAuthenticationManager/config/configUtil.sh, return code=1")
In checking the targeted slices selected to install AM 7.1 in the /etc/vfstab, the target slice in this instance was a zdrive that was mounted as a swap partition, i.e:
/dev/zvol/dsk/rpool/swap - - swap - no
This type of swap partition cannot be stat'd by the install program during the installation of AM 7.1. The targeted swap partition and underlying file system for Solaris 10/AM 7.1 installations *must* be a standard ufs file system and a standard tempfs swap partition in order to pass the prerequisite checks done by the product. For more information, reference the man page for vfstab and ufs on your server.
It has been observed that veritas, lvm and Solstice Disk Suite in addition all cause a similar failure, as well as Solaris zones.
|Resolution||While the 601 failure is very generic and does not provide a lot of exact insight into exactly what is wrong, when the the installation fails with this type of error, it can almost always be attributed to an environmental (OS or hardware) issue. Prior to beginning your installation, insure you target a ufs file system. Also, do not mount the ufs file system with any restrictive options in the vfstab (solaris) or fstab (linux).|
|Legacy Article ID||a46875|